The pricing transparency divide.

What changed

For most of CIAM's history, pricing model was a finance question: vendors either published per-MAU pricing (because the metric was simple and the target buyer was self-serve) or required sales contact (because the metric was complex and the target buyer was enterprise procurement). The choice mostly reflected market segment rather than vendor philosophy.

In 2025 this stopped being neutral. Pricing transparency became a buyer- trust signal in its own right, one that a meaningful tier of new entrants weaponized against incumbents whose pricing-by-conversation models started to read as evasive rather than enterprise-appropriate.

The shift was driven by three things at once: AI-era cost predictability pressure (CFOs got tired of quarterly true-ups across SaaS contracts), generational change in procurement (the buyers running CIAM evaluations in 2025 grew up with Stripe-style published pricing as the default), and the explicit positioning of new-entrant CIAM vendors that made pricing transparency part of their product story rather than a finance footnote.

The transparent tier

A discrete group of CIAM vendors made pricing transparency a positioning choice in 2025. They share a common pattern: per-MAU list pricing published prominently on a pricing page; explicit overage rules; visible free-tier limits that match what enterprise buyers would request anyway; deprecation timelines for legacy plans surfaced before the renewal cycle.

WorkOS is the cleanest reference implementation. Usage-based per-event pricing with public dollar amounts and explicit scaling math. A buyer running back-of-envelope math gets to the same number procurement will quote. The implicit message, we don't price you on what you'll pay; we price you on what you'll use, is the strongest single argument the transparent tier has.

Stytch, Clerk, Kinde, FusionAuth, Frontegg, Descope sit in the same shape with variations: per-MAU instead of per-event in some cases, free tiers calibrated for prototype work, enterprise plans starting at public dollar amounts rather than "contact sales."

The dev-first OSS layer (Keycloak, Ory, Logto, Zitadel, Authentik) is implicitly transparent, self-hosted has no negotiated pricing, but the hosted variants of these projects (Ory Cloud, Logto Cloud, Zitadel Cloud) have generally adopted the transparent-tier conventions.

The quote-only tier

The legacy enterprise CIAM tier still defaults to "contact sales" for serious deployments. This is not unreasonable on its face, enterprise contracts genuinely involve customization, volume commitments, and multi-year terms that don't fit a public price list. The question is whether the underlying simple cases are also gated behind sales contact.

For most of the quote-only tier, the answer in 2025 was yes. Even a boring "what does your platform cost for 100,000 MAU with standard features" question routed to a sales engineer rather than a pricing page. By the second half of 2025, this routing started costing deals. Not because the eventual quoted price was bad, sometimes it was competitive, but because the signal of needing a conversation to answer the basic-math question read as defensive.

Auth0's enterprise tier sits in this category. The lower-tier plans (self-serve startup pricing) are transparent; the enterprise plans above them are quote-only. For an Auth0-leaning buyer this is fine; for a price-comparing buyer, it complicates the evaluation.

ForgeRock sits more deeply in the quote-only model, even basic sizing questions require enterprise contact. The post-merger uncertainty amplified the procurement friction here.

LoginRadius scores 1/5 on the pricing transparency axis in this index, the lowest score. Most paid tiers are quote-only, free tier limits are stated but the path from free tier to enterprise is opaque. This is the editorial concern that informed the LoginRadius profile's overall critical posture.

Why this isn't just a finance preference

The temptation is to treat pricing transparency as a buyer-preference question, some buyers like published prices, some don't, vendors should serve both. The 2025 evidence pushed back against that framing.

The transparent tier's pricing model was an editorial expression of how the vendor expects to relate to customers: we publish what we charge; you can budget against it; we will not surprise you at renewal. The quote-only tier's pricing model was, in some cases, exactly the inverse , the price depends on what we learn about your willingness to pay, which means we will charge you what we can. Buyers reading this distinction in 2025 increasingly took the implicit message as data about how the rest of the vendor relationship would go.

The pattern was strongest in startup-led B2B SaaS buyers, weakest in heavy regulated enterprise where multi-year procurement is the default shape regardless. But the directional pressure was consistent across segments.

The 2026 procurement consequence

If you are evaluating CIAM in 2026, treat pricing transparency as a procurement signal even when it isn't your primary axis:

1. Can you do back-of-envelope math from public information? If yes, the vendor is signaling predictable pricing through renewal.
2. What's the path from the free tier to the smallest paid tier? If the free tier ends at "contact sales" rather than a published dollar amount, expect that pattern to continue at every subsequent step.
3. Are overage rules published? Overages are where opaque pricing produces the largest procurement surprises. The transparent tier publishes them; the quote-only tier negotiates them.
4. Is there a published deprecation policy for legacy plans? This is the longest-tail signal. Vendors that explicitly publish how they handle plan changes telegraph their long-run customer-relationship philosophy.

These four questions correlate strongly with one underlying property: how the vendor expects to behave in year three of a contract, not year one. The 2025 data suggests buyers started weighting that signal much more heavily than they had in any prior year.