Summary
- Okta's documents define the monthly active user seven different ways in six addresses: with and without a tenant, with and without an employee exclusion, and once by an authentication-method list that omits the enterprise connections the same contract prices as a separate column.
- The ladder is not a rate card. All ten B2C Essentials bands divide to $0.07 per MAU per month, a figure printed nowhere, and the published rule for usage between tiers bills a whole new band rather than an increment.
- The count is the auditable part: a named report, twelve months of history, three breakdowns, a CSV export and a Management API endpoint. What none of the ten documents reviewed here prints is a per-MAU overage rate.
Every identity bill carries a quantity: the number of people who authenticated, or were authorised, in a month. The documents that produce that quantity are public. Read them in sequence and the arithmetic is the easy part. The noun is not.
One noun, seven sentences
Start at the address that prints the price. Okta's own pricing page defines the unit: "A Monthly Active User is a unique user that authenticates with or is authorized by the Okta service within a given month." (Okta plans and pricing) Note what the sentence does. It widens the qualifying event to authorisation, which is not authentication. It names no tenant and excludes no employee. And "a given month" is never pinned to the calendar or to a billing cycle.
The markdown companion to the Auth0 price page carries a second version: "Any non-internal (non-employee) user that authenticated during a given month for a given tenant." (Auth0 pricing companion) Three things change in one line. The event narrows to authentication. The population narrows to non-employees. And tenant scope appears for the first time.
The Auth0 billing policy carries a third, and this one is a list: "An active user is a user that has authenticated with a username/password combination, a Passwordless ... connection, or any social provider during a given calendar month." (Auth0 billing policy) Enterprise connections are absent from that list. They are not absent from the price list. The order form defines "External Enterprise defined as usage with Enterprise connection types and External Users defined as usage with Social, Database, Passwordless and Custom connection types. Does not include Employee users." (Enterprise Self-Service Order Form Terms) A customer reading only the billing policy would conclude that a workforce signing in through SAML is not counted. A customer reading only the order form would conclude that those users are the entire first column.
The contract then defines the same quantity twice. "A MAU shall be calculated as a User with a successful authentication event with the Auth0 Platform, provided that if a unique User authenticates with the Auth0 Platform more than one (1) time in a calendar month that will only be calculated as one (1) MAU." Further along, a second term appears: "Active User coverage (quantity) is defined as a non employee user that has authenticated at least once within a calendar month." (Enterprise Self-Service Order Form Terms) One is MAU, the other coverage, and "Unique User" is defined in neither sentence.
A support article moves the counted object again: "A user is considered to be active in a given month if they have generated a log of user activity with their user_id." (Tooling for auditing Auth0 MAU) That makes the unit a profile key rather than a person, and the same article supplies the reason it matters: each tenant creates its own profile with its own identifier.
The seventh sentence is the only one that answers a behavioural question, and it sits in a blog post: "In the world of Auth0, an MAU is defined as a user who has performed a login (or a token refresh) within a calendar month." (Auth0 MAU explained) Token refresh is not on the billing policy's list of qualifying events.
The questions with one published answer
The question a customer actually asks — does a person who signs in once cost the same as a person who signs in daily? — has exactly one answer across the ten addresses reviewed here, and it is the blog's: "A user who logs in once and stays active for five minutes counts the same as a user who logs in every single day of the month: they both count as one MAU (per tenant)."
Whether one human can be three counted users has one answer too, in the same post: a unique user in three tenants counts as three MAUs. The only mechanism the post offers against a single human being counted twice is account linking, described there as the way to stop a person who uses different identities from occupying two counts. (Auth0 MAU explained)
Organization membership gets no answer at all. Auth0's documentation states that a user can be a member of several organizations inside one tenant. (Auth0 Organizations overview) No reviewed sentence says whether that changes the count. Nor does any reviewed sentence settle whether one person who authenticates through an enterprise connection and, in the same tenant, through a social connection occupies one count or two — and the order form separates exactly those two by connection type, which is where the question carries money.
Machine-to-machine has the same shape. The documentation names the output of the client-credentials flow an access token and explains that the application authenticates instead of a user. (Client Credentials Flow) The price table sells Machine-to-Machine Authentication in allowances of 1,000 on Free and Essentials and 5,000 on Professional and Enterprise. (Auth0 pricing) No reviewed sentence equates one access token with one billable token, and none says whether a refresh bills on that line.
What the contract does when the count goes over
Two documents answer the overage question, and neither answers it with a rate. The order form: "In the event Customer exceeds the purchased quantity of MAUs, Okta will require Customer to upgrade their service level tier in line with the Customer’s usage." (Enterprise Self-Service Order Form Terms) The pricing companion: "Pricing is available only at the listed MAU tiers. If your usage falls between tiers, you are billed at the next tier up." (Auth0 pricing companion)
The increment, in other words, is a band. Sit at 10,000 users, add one, and the rule does not multiply. It moves you to the next row.
The ladder that prints no rate
Here is what those rows divide to, using the monthly figures in the pricing companion. Ten B2C Essentials bands, ten divisions, one answer. $35 for 500 users is $0.07 per MAU. $70 for 1,000 is $0.07. $175 for 2,500, $350 for 5,000, $525 for 7,500, $700 for 10,000, $1,400 for 20,000, $2,100 for 30,000, $2,800 for 40,000 and $3,500 for 50,000 all land on the same $0.07. (Auth0 pricing companion)
That division is mine, not the page's. It changes how the word tier reads: on Essentials the ladder is a flat rate arranged in ten rows, and what a customer buys by climbing it is a higher declared ceiling, not a lower price per person.
Professional is not flat, and its first two rows are the tell. $240 for 500 users is $0.48 each; $240 for 1,000 users is $0.24 each — the same printed price buys twice the quantity. Then $545 for 2,500 is $0.218, $1,000 for 5,000 is $0.20, and from 7,500 through 20,000 every row sits at $0.16.
Put the published next-tier-up rule on top of that and the arithmetic becomes visible on one ladder and vanishes on the other. At 10,001 B2C Professional users the rule bills the 20,000 band, so $1,600 becomes $3,200 for one extra user in that month. At 10,001 B2C Essentials users the same rule moves $700 to $1,400 — an increment of exactly 10,000 × $0.07, which is arithmetically indistinguishable from a per-user charge. Both figures are printed band prices and the jump across bands is the document's own rule; the comparison is mine.
Two more divisions are worth holding. Yearly billing is 11× the monthly price, printed as equivalent to one month free — 8.33 percent off twelve payments — so at the 10,000 Essentials band one MAU-year costs $0.77. And in the same table set, 500 counted users in one month costs $35, $240, $150 or $800 depending on the row: the largest is 22.86 times the smallest. The B2B column is not a discount on the B2C column and must not be read as one, because the order form separates the two by connection type.
Where the metre is legible
The surprise is on the other side of the question. The part of this that is fully documented is neither the noun nor the price. It is the count.
Auth0 support names the artefact. Go to Reports, then Usage, then Subscription Usage, "where the Active Users Report can be found". It "includes the count of Monthly Active Users for the past 12 months of the subscription", can show "the Active Users, Active Users by Tenant, or Total Users by Tenant", and "can be downloaded in CSV Format". (Report of Monthly Active Users)
A second article adds a machine path and a rule a customer can apply to their own logs: admins can use the Quota Utilization reports in the Support Center or the get_active_users endpoint of the Management API, and "Auth0 MAU usage calculation also includes, for instance, Refresh Token as a log of user activity, so the successful exchange of Refresh Token for Access Token is a successful authentication event." (Tooling for auditing Auth0 MAU)
Two frictions belong beside that, in the same documents. The report's third breakdown, Total Users by Tenant, is a stored-profile count and not an MAU. And the auditing article states both that for MAU "logins are not counted" and that admins should query tenant logs for successful login events.
So a customer can reconcile. Export the report, pull the tenant logs, apply the user-identifier rule, compare the total against the invoice line. What the same ten documents withhold is a printed price for the unit just reconciled. The count is checkable. The rate is not printed. And the population it covers is described seven ways.
The documents that were not readable
In the ten addresses reviewed here, the largest stop is Okta's own customer-identity pricing. The page prints a required base product at "$3,000 per month, billed annually" and says add-on pricing is "based on usage, such as your total Monthly Active Users per year" (Okta plans and pricing) — an annual phrasing laid against a definition written inside "a given month", with no sentence joining the two. It prints no MAU band table and no per-MAU rate for that product. Part of that is a reading limit rather than an absence: the page runs a client-side calculator, and the calculator's output cells were not read here.
Three further stops. Professional and Enterprise Workforce pricing is quote-only, so no seat price above Starter at $6, Core Essentials at $14 and Essentials at $17 is public, and the page's own floor is a "$1,500 annual contract minimum" rather than a seat count. (Okta plans and pricing) The order form was read as a PDF excerpt: its SKU prices and any audit obligation are not visible. And the Auth0 comparison column that carries the allowances is headed "External Active Users" while the plan cards above it say "monthly active users"; no sentence in the inspected text equates the two labels. (Auth0 pricing)
One boundary deserves naming, because it is where an argument would otherwise be easy. Workforce Identity is priced per user per month with a $1,500 annual floor; Customer Identity requires a $3,000 monthly base. Those are two product families, 24 times apart on my arithmetic, and nothing reviewed here establishes that the Auth0 entry rows and the $3,000 base product price the same thing.
What the documents add up to
Okta has not published a vague price. It has published a precise quantity of disagreement: seven sentences for one noun across six addresses, a ladder that divides to a rate the vendor never printed, and a metering path a customer genuinely can walk. The reconciliation is real — report, logs, user identifier, invoice. What that reconciliation cannot produce is the second line of a forecast, because the noun has seven published edges and the price of one more unit is a row rather than a rate. Okta is tracked in BTW's entity directory.
Member Briefing
Read the full trend briefing
Members read the full briefing with the source notes behind every finding.
Strategic Circle
A daily briefing in your language, built from changes we have verified.
Join for USD 20/monthCancel anytime.
Members also get the full research library, a daily briefing on the networks they follow and the private forum.






