We removed Redis

Authentik, an open-source identity provider, transitioned from using Redis to relying solely on PostgreSQL in its 2025.10 release to simplify its architecture, reduce dependencies, and enhance stability. Initially, Redis was chosen for its speed in handling frequently accessed data, but the decision to move away was influenced by broader industry trends, licensing changes, and the complexity of maintaining high availability setups with Redis. The migration began in 2024.6 by replacing Redis locks with PostgreSQL advisory locks and was completed in 2025.10, despite some performance trade-offs in areas like Remote Access Control and WebSocket communication. With everything now stored in PostgreSQL, except media files, authentik has improved user session performance and gained better insight into background tasks. The shift aims to provide a more reliable and straightforward self-hosting experience for its community, aligning with authentik’s goal to focus on simplicity and reliability.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.