Pricing is always tricky. One pricing never fits all use case. So we have worked hard to offer pricing options like usage based pricing/ dev based pricing in addition to user based pricing.
Was curious to apply your use case and see if our pricing model maximises ROI.
Disclaimer: I am co-founder at a retool alternative platform for building internal tools and enterprise apps.
Re:Form to DB
by antonybello on Saturday February 24, 2024 @11:36AM
(#39492834)
Hi! Last year, Retool introduced differentiated pricing for end users (viewers) and standard users (editors) to make these kinds of use cases much more palatable[0]. We also rolled out support for building customer-facing apps through letting you whitelabel and ship apps to people outside your organization [1].
Would be more than happy to talk through your use case; feel free to reach out at antony[at]retool[dot]com.
[0] https://retool.com/pricing [1] https://retool.com/products/portals
I want to create customer accounts, apply settings (e.g. I delimit the data their account can access, basically adding WHERE clauses on a per-account basis), and they can access white-label read-only dashboards with their own user/pass.
Retool seemed 100% insistent on being an internal-only tool with a high cost per user.