Skip to content
Shutdown / EoL

Akamai Identity Cloud announces end-of-life, full shutdown December 31, 2027

Akamai formally announced End-of-Life plans for Identity Cloud on October 31, 2024, with feature freeze in effect since end of 2024 and complete shutdown set for December 31, 2027. Existing Janrain-lineage customers should be in active migration.

Akamai Identity CloudAuth0MojoAuthSAP Customer Data Cloud

What happened

Akamai announced the End-of-Life of Identity Cloud, the B2C CIAM product Akamai acquired from Janrain in 2019, on October 31, 2024. The timeline:

  • March 7, 2024, End of Sale; no new customer onboardings accepted.
  • October 31, 2024, Formal End-of-Life announcement.
  • End of 2024, Feature freeze in effect; no new development on the platform.
  • December 31, 2027, Complete shutdown; service ends.

Why it matters

Akamai Identity Cloud (formerly Janrain) was one of the longest-tenured B2C CIAM platforms, with deep heritage in social registration, consumer profile management, and consent orchestration. Its customer base skewed toward enterprise media, retail, and consumer brands, many of which had used the product for a decade or more. The shutdown forces a migration window for a population of customers that hadn't planned to evaluate alternatives.

Three years between announcement and shutdown is generous on paper, but realistic migration projects at the scale of Janrain's enterprise base run 12–18 months from decision to cutover. Customers who haven't started the conversation by mid-2026 will be making rushed choices in late 2026 and early 2027.

Deepak's take

The CIAM market has bifurcated: developer-first platforms (Auth0, Stytch, Clerk, MojoAuth) on one side, enterprise heritage platforms (Akamai, ForgeRock, IBM, Oracle) on the other. The heritage side is consolidating fast, ForgeRock merged into Ping under Thoma Bravo in 2023, Akamai now sunsetting, IBM rebranding its identity portfolio. The signal is that traditional B2C CIAM at the heritage tier is being abandoned by its acquirers in favor of either modernization or product-line consolidation.

For Akamai customers, the migration question isn't just "which CIAM" but "which kind of CIAM." Modern developer-first platforms have caught up on enterprise capabilities while retaining DX and pricing advantages. SAP Customer Data Cloud (formerly Gigya) remains the heritage-tier option for the largest B2C enterprise deployments. MojoAuth is the cost-aware modern option for B2C teams with enterprise auth requirements (SAML, advanced MFA).

What to do

If you're an Akamai Identity Cloud customer:

  1. Inventory now. Capture the customizations: registration flows, consent rules, social provider configuration, custom email templates. These often have undocumented business logic.
  2. Define your destination. Use the vendor selector tool and the build vs buy guide to narrow the shortlist.
  3. Plan a JIT migration. Don't bulk-migrate password hashes; verify on next login and re-hash with the new platform. See the migrating-from-Cognito guide for the JIT pattern (the approach generalizes).
  4. Budget for the federation rebind. Social provider bindings (Google, Apple, Facebook) need to be re-established on the new platform. Plan for the user-facing UX of "sign in with Google again."

For more on data residency and sovereignty considerations during the move, see the data residency guide.

Sources

Curated 2026-05-08.