idpcost.com
Memo
To: IT / Security buyer evaluating Okta Workforce Identity
From
idpcost.com
Re
Okta Workforce Identity end-to-end cost analysis
Source
https://www.okta.com/pricing/

Okta Workforce Identity

live verifiedOkta · Per-user tiered bundles. $1,500/yr annual minimum across all tiers.

Okta restructured pricing in 2025-26: the older à-la-carte model ($2 SSO + $3 MFA + $4 Lifecycle) no longer exists. New starter at $6/user/mo includes SSO + MFA + basic provisioning. The $1,500/yr minimum effectively prices Okta out of teams below ~21 seats.

1.Year-1 TCO breakdown

Representative buyer: 200 employees, 30 SaaS apps, full SAML + MFA + lifecycle automation, 90-day audit retention.

Licensing (200 seats)200 seats × $14/mo (Core Essentials) × 12 = $33,600/yr
SAML taxSSO is included from Starter ($6); the step to Core Essentials ($14) buys lifecycle provisioning and workflows, not SAML itself
Audit retentionOkta's System Log is fixed at 90 days on every tier. There is no paid retention extension to buy — Okta's own guidance is to export via the UI or API, or stream events to a third-party SIEM. Longer retention is a cost you carry, not an Okta line item
MFAIncluded in all paid tiers
Year-1 TCO$33,600/yr licensing at Core Essentials (200 × $14 × 12). Price tier movement separately — Essentials at $17 is $40,800/yr for the same 200 seats — and add your own log pipeline if you need more than 90 days of retention

2.The hidden cost category for this IdP

Hidden cost

The $1,500/yr annual minimum is the structural cost trap. Below 21 seats (~$1,500 ÷ $72/seat-year at Core Essentials) the annual minimum dominates and per-user math becomes meaningless. The tier jumps are the second trap — moving from Core Essentials ($14) to Essentials ($17) is a 21% per-seat increase, often triggered by needing a single feature (e.g. workflows). The third is log retention, and it is the one buyers model wrongly: Okta caps the System Log at 90 days and does not sell an extension, so a multi-year compliance retention requirement arrives as an engineering project on your side rather than as a line on the Okta quote.

3.Migration cost out of Okta Workforce Identity

The Okta-specific complication is Workflows. Many companies use Okta's Workflows engine for custom joiner-mover-leaver automation, and that logic does not port — it has to be rebuilt in the target IdP's automation framework, which is usually the largest single line in an Okta exit. The standards-based parts (SAML app reconfiguration, SCIM connectors, MFA re-enrolment, System Log export) behave like any other migration. Work your own number from the driver table on the migration-cost page rather than a category average; the spread between a 30-app deployment with no custom Workflows and one with fifty of them is larger than the spread between IdPs.

4.The negotiation lever

Tier upgrade timing. Okta sales pressures upgrades to Professional/Enterprise via 'roadmap calls' that surface compliance or governance features. The lever: bundle any upgrade into the renewal rather than taking it mid-term, ask for the multi-year commit discount in writing before you agree to the tier, and push back where the feature driving the upgrade is not actually required by your audit scope. Okta publishes no discount schedule, so treat any percentage a rep quotes as a starting position and make them put it against a named tier and term.

5.Vendor tier reference

TierPer-user (USD/mo)Features
Starter$6
Core Essentials$14
Essentials$17
Professional / EnterpriseQuoteQuote-only — adds advanced lifecycle, governance, identity threat protection