Running Ory on a 30M users platform
summary
Fandom migrates its authentication to Ory Kratos for 30M users, runs Kratos in shadow mode alongside the legacy system to compare every authentication result, and imports 35 million accounts by writing a direct-database importer rather than slow REST calls. Identity synchronization uses an identity mapper facade and bidirectional hooks; a custom hashing algorithm is added so imported passwords validate. The migration completes with performance parity, incremental fixes, and a final cutover without user-data loss.
AI-written summary · about
chapters (12)
- 0:00Introduction and speaker
- 1:23What is Fandom platform
- 4:16Authentication system overview
- 8:12Why choose Ory Kratos
- 10:19Migration challenges
- 11:00Shadow mode deployment
- 12:27User import process
- 13:54Custom hashing for legacy users
- 14:35Data consistency between systems
- 15:57Synchronization via hooks
- 16:38Username and identity checks
- 17:19Extending Kratos webhooks
related talks
23mRe-Engineering: Ory Kratos and Ory Keto in production
25mAnaconda Unified authentication with Ory 
16mHow to move your RBAC into Ory 
19mDavids Slingshot: Leveraging Ory
24mBuilding a community management infrastructure with Ory open source software
25mImplementing the Ory stack at Padis
18mOry Cloud Identity for App Developers, Amorevino Firebase Example
15mKeynote: Future Directions for the New ID Stack