Authentication costs depend on the provider's billing definitions and the features your SaaS needs. Registered accounts, active users, retained users, organisations, messages, and enterprise connections are not interchangeable units.
Before scaling, build a worksheet that uses the current plan terms and your actual product model. A free-tier headline cannot tell you the cost of a B2B application with many small customer teams.
Read billing definitions before entering volumes
Record the provider, plan, quote date, billing unit, included allowance, overage rule, required add-ons, and contract assumptions. Check how development and production environments are treated and whether your required roles, session controls, logs, and support are available on the selected plan.
For example, consult the current Clerk pricing page and its linked definitions rather than copying an old comparison table. This article deliberately gives no lasting price promise because plans and billing rules can change.
Model a fictional agency SaaS
Suppose a product serves agencies with several client workspaces. Its registered-user count may be modest while the number of active organisations, enterprise identity connections, and invitation messages grows differently.
Create three illustrative scenarios: a small pilot with a few teams, a wider rollout with many low-activity teams, and a concentrated customer with stronger access and support requirements. Use your own expected counts and label them assumptions. Calculate the bill under the provider's current definitions rather than substituting total registrations for every unit.
Add messaging and related services where they are separately charged. Consider the operating effort of support, account recovery, permission debugging, and provider changes. A lower service bill can be offset by more engineering work, while a higher plan may include capabilities you genuinely need.
Compare migration cost alongside recurring cost
Ask how stable user identifiers, organisation memberships, roles, and linked accounts would be exported or mapped if the provider changed. Password and session migration capabilities require current provider-specific review; do not assume every account can move through a simple database export.
Keep application resource ownership distinct from provider display fields. That can make future mapping clearer, although it does not eliminate migration work. Estimate coexistence, user communication, testing, and support disruption as part of the comparison.
The tradeoff is predictable spending versus feature flexibility. A plan that fits today's pilot may constrain tomorrow's enterprise requirement. Avoid paying for hypothetical needs indefinitely, but record the trigger that would force an upgrade or architectural review.
The StackFlight product account describes a shipped SaaS using third-party authentication. It does not publish a provider bill or establish your application's future cost.
Questions about authentication spending
Should founders compare cost per registered user?
Only when that matches the provider's billing definition. Use the actual units and model organisations and add-ons separately where required.
Is self-hosting automatically cheaper?
No. Include engineering, updates, incident response, account recovery, and operating risk before comparing total cost.
What should a scaling review contain?
Bring dated plan terms, three usage scenarios, required features, observed activity, and migration assumptions to a SaaS architecture discussion.