ZITADEL

We just shipped user schemas for the next Zitadel. 🚀 Most identity providers hand you a fixed user object and expect your app to adapt. We flipped that: your user model is now a JSON Schema file in your repo. Edit it, add fields, add whole new schemas for machines and agents. Preview the change with `plan`, publish it with `apply`, straight from your repo. Full write-up: https://lnkd.in/e4jC-gGi

We're building the next iteration of Zitadel in the open, and sharing every step: previews, the open source repo, the roadmap, and what's next. If you want to follow along, join the waitlist. We'll keep you posted as it happens. Subscribe: https://lnkd.in/eea9uWeZ

We published where the next iteration of Zitadel is headed: five phases, from local-first setup in under a minute to AI agents as first-class identities. Not a theoretical roadmap, each phase ships as something you can actually install and use. Read it: https://lnkd.in/e3AZB49e

We open sourced the repo for the next iteration of Zitadel: [zitadel/nextgen](https://lnkd.in/eZYBH26C) CLI, runtime, framework adapters, all public now, from here on. It's separate from `zitadel/zitadel` for now, our build and release pipeline changed enough that sharing CI/CD right now would slow us down. Once that settles, we'll merge it back into one repo. Go star it, open an issue, tell us what's wrong. We're building this in the open specifically so it reflects what you need, not what we guessed. ⭐

The recording from our community event is up: a live demo of the next iteration of Zitadel (one command, a working login flow with passkeys, under a minute), the vision behind it, and a Q&A with genuinely valuable feedback from the community. Watch it: https://lnkd.in/eTkF4zjR

I'm in the middle of ZITADEL integration. It's going well so far. The local environment is set up with Docker. Everything looks good. I'm preparing my .NET Core backend webhook to handle registration events from Zitadel. I want to make sure that when a user signs up or logs in through Zitadel, the backend can process those events correctly and maintain the user data in sync. Other users' profile changes also should go smoothly with the same approach. All auth sign-ups and sign-ins will be handled by Zitadel, so I can focus on the core business logic and user experience without worrying about the complexities of authentication and security. Moreover, I can use this in my other future projects as well. #LIFOCode #SoftwareEngineering #Modernization #Authentication #Zitadel

Think Like a Hacker: Highlights from HackingLab Day 2026 We had an incredible time sponsoring HackingLab Day 2026 at the START Global Campus in St. Gallen! In collaboration with the Universität St.Gallen (HSG) and GObugfree AG, we dove deep into the future of cybersecurity. The capture the flag was a highlight of the day. Check out our full recap! https://lnkd.in/eD3WfPXb Thanks to Christoph Bühler Guido Salvaneschi Nadine Anderson for the well organized event 👏 #CyberSecurity #STARTGlobal #ZITADEL #AI #EthicalHacking #InfoSec #HSG

Complexity shouldn't be the status quo. We’ve heard your feedback on naming inconsistencies in ZITADEL. Today, we’re taking a major step toward a more intuitive developer experience with a platform-wide terminology alignment. Standardized docs. Unified UI. Zero breaking changes. Read the full announcement and see the mapping on our blog: 👉 https://lnkd.in/eduvzZGx #DeveloperExperience #IAM #OpenSource

Are you ready to think like a hacker? We're sponsoring a HackingLab Day on March 27th at the START Global Campus in St. Gallen. It's a hands-on day with a practical introduction to ethical hacking. Explore the legal framework, learn the tools and techniques security teams use in the real world, and put your skills to the test in a capture-the-flag challenge. 🚩 Register now: https://lnkd.in/exijJMfG

Integrating Linux fleets with modern identity providers has historically required maintaining LDAP bridges or complex SSSD configurations. Ubuntu's latest update to AuthD changes this architectural requirement by introducing a generic OIDC broker. You can now authenticate Ubuntu environments directly against an OIDC provider like ZITADEL. This removes the need to maintain legacy directory services purely for OS-level access control. By treating the OS login as a standard OIDC client, we reduce the attack surface, remove protocol translation layers, and simplify the provisioning pipeline. https://lnkd.in/e-Dm_m85 #Linux #OIDC #DevOps