Explore the new Zitadel management Console, configure Google SSO through the CLI, and inspect your local authentication setup in one complete workflow.
• Fabienne Bühler
Reading time • 5 min
Zitadel Nextgen no longer uses events as the source of truth. Learn why we moved to relational storage while keeping wide events for auditing, security, and integrations.
Six ways an AI agent's identity gets exploited, and the controls that close each one.
AI agents didn't reinvent identity. AAA still decides everything. What changed: scoped delegation and per-agent audit are no longer optional
Agents make it faster to build your own auth, but they don't make it safer. Someone still has to secure, audit, and maintain code no one on the team actually wrote.
We’re building the next iteration of Zitadel in the open. Explore our community roadmap and see how we’re rethinking identity—from getting started in under a minute to enterprise scale and AI-native identity.
AI agents don't need to break in to cause damage. When an agent is handed broad credentials for a narrow task, the identity layer can't tell the difference, and that's a structural problem with how access control was built.
Authentication that starts locally in about a minute, then moves login flows, user schemas, and identity configuration closer to the application workflow, where developers and coding agents can inspect, review, and change them.
ZITADEL joined HSG and Gobugfree at HackingLab Day 2026 to bridge the gap between academic theory and real-world security. From the ethics of hacking and AI vulnerabilities to high-stakes CTF challenges, we explored the evolving threat landscape. Read our highlights on why transparency, proactive incident response, and creative thinking are the keys to a resilient future.
No more naming inconsistencies. Explore ZITADEL’s comprehensive terminology update designed to reduce cognitive load and streamline your integration process without breaking existing APIs.
