Skip to content

Blog

Auth0 pricing, and why it is not workforce SSO

Auth0 pricing explained: the free plan, what paid plans cost as monthly active users grow, and what to buy instead if you wanted SSO for staff.

· 9 min read

Auth0 pricing starts with a free plan for up to 25,000 monthly active users. Paid plans start at $35 a month for consumer apps (B2C Essentials) and $150 a month for business apps (B2B Essentials), at the smallest tier of 500 users, and rise with the number of people who log in each month. Enterprise is priced on request.

Those are the prices on Auth0's pricing page as we read it on 27 October 2026. The important thing about them is who they are for. Auth0 prices logins for your product's users, not for your staff. If you were looking for single sign-on for your team's work tools, Auth0 is the wrong product, and this post says what to look at instead.

Auth0's plans and prices

PlanPrice, smallest tierNotes
Free$0Up to 25,000 monthly active users; 1 enterprise connection
B2C Essentials$35 a monthFor consumer apps
B2C Professional$240 a monthFor consumer apps
B2B Essentials$150 a month, or $1,650 a year3 enterprise SSO connections
B2B Professional$800 a month, or $8,800 a year5 enterprise SSO connections
EnterpriseContact salesCustom user and SSO tiers

The paid prices shown are for the lowest tier of monthly active users: 500 for the Essentials plans, and 1,000 for the Professional plans, whose price is the same at both. Paying yearly costs eleven times the monthly price, which the page sells as one month free.

How the price grows with your users

The unit to notice is the monthly active user: a person who logs in to your product in a given month. An employee count has nothing to do with it. The page has a slider for it, and the monthly prices at a few of its steps were these:

Monthly active usersB2C EssentialsB2C ProfessionalB2B EssentialsB2B Professional
1,000$70$240$300$800
5,000$350$1,000$1,300$1,500
10,000$700$1,600$2,100$2,400

At 30,000 active users, every paid plan except B2C Essentials says "contact us"; B2C Essentials keeps a list price up to 50,000.

Here is what that means in practice. Say you sell software to other businesses and 2,000 of their people log in each month. That lands in the 2,500 tier, where B2B Essentials is $700 a month, or $7,700 a year paid yearly. Double the active users and the bill nearly doubles. That is fine for a product, whose revenue grows with its users. It is a strange way to pay for logins for 20 colleagues.

Two worked examples

A small B2B product. You have 800 active users across a few dozen customer companies, and two of those customers want their staff to log in through their own identity provider. The free plan covers the user count but only one enterprise connection, so the second customer pushes you to B2B Essentials. At the 1,000-user tier that is $300 a month, or $3,300 a year paid yearly, with three enterprise connections included. A third and fourth SSO customer still fit. A fifth pushes you to add-ons or to B2B Professional, at $800 a month.

A consumer app. You have 10,000 people logging in each month with email or Google, and nobody asks for SAML. B2C Essentials at that tier is $700 a month, or $7,700 a year. You do not need the B2B plans at all, unless a business customer turns up asking for SSO, and then the upgrade is the subject of the next sections.

Both bills are for the product, and both scale with its success. Neither tells you anything about what single sign-on for your own staff would cost.

What the free plan includes

The free plan is genuinely usable for a small product. The page lists up to 25,000 monthly active users, no credit card to sign up, one custom domain (which needs a card for verification), unlimited social connections such as "Sign in with Google", passwordless login and five organizations, Auth0's way of modeling your business customers. It also includes one enterprise connection, self-service SSO and SCIM, which the page marks as new.

What it leaves out is support and history. Free has community support only and, per the page's comparison table, one day of log retention. The paid plans add standard support, longer logs and more tenants, which is what you will want once real customers depend on the login.

Customer identity vs workforce identity

Identity products split into two markets, and mixing them up is the most common way to end up on the wrong pricing page.

Customer identity (often shortened to CIAM) is login for your product's users: the sign-up page, "Sign in with Google" on your app, password resets, MFA for your customers. It is priced by monthly active users, because a product can have thousands or millions of them. Auth0 is a customer identity product. So is Microsoft Entra External ID, which Microsoft's Entra pricing page lists as pay-as-you-go and free for the first 50,000 monthly active users.

Workforce identity is login for your staff, into the tools your company uses: Slack, GitHub, Figma, Google Workspace. It is priced per employee, every month, whether they log in or not. Okta Workforce Identity, Microsoft Entra ID, JumpCloud and Google Workspace are workforce identity products. What an identity provider is explains the job they share.

The technology overlaps. Both kinds speak OpenID Connect and SAML (SAML vs OIDC explains the difference). What differs is who logs in, where, and what you are billed for.

Auth0 vs Okta

Okta sells both. Auth0's site carries Okta's copyright, and Okta's own pricing page lists Workforce Identity suites, with separate tabs for workforce and customer identity and a link for anyone "looking for Auth0 pricing".

So the difference between Auth0 and Okta is mostly the difference between the two markets above. Auth0 is the developer-facing product you build into your own app, priced by active users. Okta Workforce Identity is what an IT admin uses to sign staff in to SaaS tools, priced per user with a $1,500 yearly minimum and annual billing on every suite, per that page. If you are a company of 20 people looking for single sign-on into your work tools, Auth0's pricing page will not tell you what you need to know.

Can Auth0 sign in your employees?

Not in the sense people usually mean. Auth0 is built and priced to put a login in front of software you own. Signing your staff in to Slack, GitHub or Figma is a different job: a workforce identity provider keeps the employee list, assigns each tool to the right people, and takes the tools away when someone leaves. Auth0's plans are not sold on that basis, and its billing unit, the active user of your product, says as much.

The tell is in the page itself: when we read it, the words "workforce" and "employee" did not appear on Auth0's pricing page at all. If your search started with "SSO for our team", the products in the next sections are the ones to compare.

When Auth0 is the right tool

Auth0 makes sense when you are building software and your own users need to log in to it. If you want sign-up, login, social login and MFA without building and securing them yourself, that is its core job.

It also makes sense when you sell to businesses and your customers ask to log in to your product with their company SSO. That is what Auth0 calls enterprise connections, and it sits on the B2B plans. Finally, Auth0 issues machine-to-machine tokens, so your own services and API clients can authenticate without a person logging in.

In the enterprise-connections case, notice the irony. Your customers are asking you for SAML SSO, and the tool you would use to give it to them puts that feature on a higher plan. If you add it to your own Enterprise plan in turn, you are passing the SSO tax down the line.

The SSO tax on Auth0 itself

Auth0's own pricing has a version of the SSO tax, aimed at software companies. An enterprise connection is what lets one of your customers log in to your product through their own identity provider, over SAML or similar. Auth0's free plan includes one. Its B2C plans do not: the page says to upgrade to B2B "to continue using EC, Self-Service SSO, and SCIM". B2B Essentials includes three enterprise connections, B2B Professional five, with more as add-ons or on Enterprise.

So a software company that wants to offer SSO to its business customers is pushed to B2B pricing, which starts at more than four times the B2C entry price. Many pass that on by putting SSO on their own top plan. That is how the tax travels down the chain to the small companies at the end of it, and why enterprise SSO so often means "the expensive plan". If you are building a product, consider not doing that: buyers notice, and they resent it.

If you wanted staff SSO

If you landed here looking for single sign-on for your team, start with what you already pay for. Google Workspace and Microsoft 365 can both act as identity providers for many tools, at no extra charge; Google Workspace SSO shows the set-up on Google's side.

If you need more than that, a workforce identity provider such as Okta, JumpCloud or Microsoft Entra ID is the next step. Okta pricing and JumpCloud pricing break down what they cost a small team.

You may not need an identity provider at all, if what you actually need is to add and remove people across your tools. SSO for small business covers that decision. Whichever you pick, remember the second bill: each tool has to support SSO, usually on its Business or Enterprise plan.

Where SmashSSO fits

SmashSSO is not customer identity and not SSO. It is for the people who work at your company: it reads them from Google Workspace, finds who has access to which tool, and invites, changes and removes them from one place, through a tool's member API where you have added a token and through an agent in your own Chrome otherwise.

That includes your Auth0 dashboard itself. Auth0 tenant admins are just another tool's member list to keep in step when someone joins or leaves. It costs a flat fee from $199 a month billed annually (pricing).

FAQ

How much does Auth0 cost?
On Auth0's pricing page on 27 October 2026, B2C Essentials started at $35 a month and B2B Essentials at $150 a month for 500 monthly active users, with Professional plans from $240 and $800. Prices rise with monthly active users, and paying yearly costs eleven times the monthly price.
Is Auth0 free?
There is a free plan for up to 25,000 monthly active users, with no credit card needed to sign up. It includes social logins, one enterprise connection and five organizations, with community support only.
Can Auth0 do SSO for employees?
Auth0 is built and priced for logins to software you own, counted in monthly active users. For staff signing in to tools like Slack or GitHub, a workforce identity provider such as Google Workspace, Microsoft Entra ID, Okta or JumpCloud is the right kind of product.
What is the difference between Auth0 and Okta?
Both belong to Okta. Auth0 is customer identity, the login inside your own product, priced by monthly active users. Okta Workforce Identity signs your staff in to work tools, priced per user with annual billing and a $1,500 yearly minimum.

Keep reading

Stop paying for a login button.

Sign in with Google Workspace, connect your tools, and see who has access to what in minutes.

Sign up with Google