Client Portal Pricing Model

Hi @victoria,

Thanks for the response! It's good to know about the public apps on the business plan.

Are you planning on adding any capability for non-public information - i.e. where a customer would need to first log in to an external app? My customers should only be able to access their own orders and the order information cannot be public.

Thanks again!

1 Like

Hi @hunter!

Glad to hear it.

Public apps aren't really meant to be a secure access point (public apps), so they don't support any of the same authentication methods that you get when users log in through Retool. We don't track any user information on public apps, so that limits what we can do. If you were to embed the normal /app/ version in a page, it would prompt the users to log in if they weren't already authenticated and work normally otherwise!

Had there been any progress on this?

Retool could work great as a customer portal - with limited functionality, but at a cheaper price.

1 Like

Hi @richelliott! For now, building upon the public app functionality to support auth + public users isn't on any upcoming roadmaps, but I've passed this feedback along to the team. Thank you for taking the time to share your plus one here, it absolutely helps us know what to prioritize in future plans. :slightly_smiling_face:

Hi @richelliott - Retool PM here. We're exploring this use case and would love to chat more about your use case. I'll reach out direct now but for any others feel free to email me at



I sent this to you in an email as well.

I along with the other people on this post, am very interested in a client portal pricing model, the other company I have looked at is JetAdmin, which I'm sure you are familiar with. Their external pricing model is very attractive, however, I think ReTool might have some advantages to JetAdmin and I have finally started to learn how to work my way around ReTool. What are the chances that ReTool could adopt a similar plan to JetAdmin?

Here is a link for your reference.

1 Like

Hi Jamie and other "retoolers"

It's great that this issue has been raised. For our company is a real deal breaker and has us on the cusp of deciding to creating lots of mini apps with Django or some other quick development web framework that don't add critical business value.

If you consider a use case where a company's customers log into a Retool app a few times a month, enter some information, read a graph and log out, Retool would be awesome but there is no way that the benefit outweighs the cost per user (> USD 50 / month with decent security features). That amount is reasonable for internal users (though certainly on the expensive side of the spectrum of business SaaS).

For a B2B company with 30 employees, 200 customers and 2 users per customer, the bill goes through the roof with over USD 21k a month! And that same company's Google Workspace Enterprise Plus (which includes AppSheet) bill is only USD 675. It makes retool 16x more expensive.

The alternative is to build separate apps (one Retool app for internal use and a custom one for external users) that are tightly coupled on the data storage... The CFO might be happy but the engineers will be very sad :joy:



@glarrain-cdd Thanks for the follow up thoughts here. Would love to learn more about your use case and see if what we're building will work for you. Want to shoot me an email at

We're looking for a solution here as well. We need a build a client support portal based on the products they purchased. For the products they own, there would be various download options and user manuals along with support plan renews and upgrades. I know we can do most of this we Retool except for the costly user authentication.

1 Like

Hi folks! I'm the PM working on Retool for external use cases (like client-facing portals). Please shoot me a note at - would love to learn more about how you're thinking about leveraging Retool!


Singed up to post about this. I just discovered this issue too... very disappointing for us.

We want to build both a supplier management portal and a customer management portal. $10/m for Suppliers does make sense, but to add hundreds of customers .. will make Retool far and away our biggest SaaS spend.


Also signing up for this post - Retool looks great with lots of functionality but I need to build a cost-effective client portal and from I can see, the pricing model won't support this.

My use case requires data to be behind a log in for order submissions, analytics and tracking but also requires public access to elements of the data.

I'm looking to deep link limited edit forms to a QR code which should be publicly accessible or behind a password/pin with no log in required. As I'm building for a client, I need the back end only accessible to me, so the app must consist of a client admin portal, a client-customer admin portal and the public facing element.

Ideally the database would be shared with a WordPress site, so MySQL.

I would then be looking to use Retool for building solutions for other clients.

Right now, Glide App seems to be the best solution, but it can't have MySQL as the data source.

So I'll be keeping a close eye on Retool - hopefully in the future it will become more competitive for my use case(s).

This is what I was thinking too, one internal app and one external but that's a lot of work as a workaround, even for so for a solo dev!

Thank y'all for all your feedback! Keep it coming :slight_smile: We're working on a new way to build and share public apps, which should hopefully help with the price per user issue. Coming soon™️!

Anyone with a Retool account counts as a user pricing-wise, editor or otherwise. On the Business Plan, you do get the public apps feature, which lets you build apps that are publicly available to anyone with the URL. Whoever uses that link won't need a Retool account, so you won't be charged for them. Since the app is public though, you wouldn't want it to have any user-specific information or dangerous functionality (I.E. deleting rows in a database).

Currently, public apps are meant for simple apps with no authentication or security. In portal-like use case where there's a notion of authentication, public apps won't be your best option since they don't collect any sort of user info. feel free to shoot Antony, the PM working on externally facing Retool apps (like client-facing portals), a note at if you'd like to share more about your use cases.

I must be the odd ball here.... I would think everyone would want a much cleaner, productive, and more personal customer facing portal than using Retool. Retool is a amazing for internal tools. Hands down the best service there is. But for customer facing? Hire offshore.

Here is your cost effective stack:

That is probably a good model. First build (prototype) it in Retool to nail down the database, functionality, workflow and business logic and then pass it off to someone to recreate in Vue for a royalty free, aesthetic, performant and scalable product.

If they can retool can find a way to integrate in 3 or 4 basic patterns and have a pricing model that include clients rather than users they might pull it off. The crux of the seems that they only want to only support one type of authentication which will never been successful.. You may as well write your own if you going to have to jump through retools proposed authentication model.

Update here: we just launched Retool Embed, which lets you securely embed Retool apps into your existing portal or web app. You can use your existing auth to give users access to embedded Retool apps, and Retool provides security and auditing for external users out-of-the-box (docs here).

Because we're talking about external-facing Retool apps embedded into your product, the pricing model needs to make sense upfront and at scale. Because business models vary (or some companies don't monetize users at all), we've worked with our early customers to align on what works.

Would welcome any feedback on the Embed product - please don't hesitate to share it at!


Hi all, we just made some significant changes to our pricing! Instead of charging the same price for any user at your company, we will now charge different rates for standard users (people who build apps in Retool) and a significantly lower amount for end users (people who only view or use Retool apps). See the details on our pricing page.

I'd love to understand if this helps unblock your use cases, or if there's more work to be done. Please shoot me a note at if so!