Pricing behavior — Authentication & Identity
•
Pricing
Pricing for OneLogin
How pricing changes as you scale: upgrade triggers, cost cliffs, and plan structure (not a live price list).
Sources linked — see verification below.
Freshness & verification
Pricing behavior (not a price list)
These points describe when users typically pay more and what usage patterns trigger upgrades.
Actions that trigger upgrades
- Need stronger conditional access and advanced policy controls
- Need governance workflows like access reviews and lifecycle automation
- Need enterprise support and higher assurance security posture
- Need to standardize identity across multiple business units and apps
- Need tighter ecosystem alignment with a primary vendor (Microsoft, etc.)
What gets expensive first
- The operational cost is policy ownership and rollout discipline, not just licensing
- App-by-app onboarding often requires testing and attribute mapping
- Migrations require staged cutovers to avoid widespread login failures
- Identity incidents are outages; monitoring and runbooks are mandatory
- Workforce IAM tooling doesn’t replace CIAM product needs
Plans and variants (structural only)
Grouped by type to show structure, not to rank or recommend SKUs.
Plans
- Base - Per-user licensing - Workforce SSO and baseline controls (see pricing page)
- Security - Add-ons - MFA and advanced security controls (see pricing page)
- Governance - Add-ons - Reviews/lifecycle workflows where applicable (see pricing page)
Next step: constraints + what breaks first
Pricing tells you the cost cliffs; constraints tell you what forces a redesign.
Open the full decision brief →Sources & verification
Pricing and behavioral information comes from public documentation and structured research. When information is incomplete or volatile, we prefer to say so rather than guess.