Streamlining Our Terminology for a Sharper Developer Experience
We’ve just made a major step toward simplifying ZITADEL and making it more intuitive. You spoke, we listened, and as promised, our top priority this year is to make complex multi-tenancy simple, secure, and scalable. And simplicity starts with clarity.
For too long, we’ve struggled with naming inconsistencies across our products—a headache we know many of you have shared. Terms used in our APIs didn't always match the UI, or the documentation used yet another variation. This lack of uniformity introduced unnecessary friction, wasted time, and complicated integration.
Today, we can announce a comprehensive terminology update that standardizes key concepts across the board. We've tackled these inconsistencies head-on to ensure that the terms you see in one place are the same terms you see everywhere else. The result is a simpler, more streamlined development environment.
Where You'll See the Difference
We’ve already rolled out these changes in several critical areas to immediately improve your experience:
- Documentation: All core concepts and guides now use the new, standardized terminology, making it easier than ever to learn and find what you need.
- Management Console UI: The user interface for managing your resources is updated to reflect the consistent naming conventions.
- Customer Portal UI & Login UI: These interfaces are also harmonized, creating a unified experience from the moment you log in.
A Stable Path Forward for APIs
We recognize that our APIs are the backbone of your applications. While we were committed to fixing the inconsistency, we were equally committed to avoiding painful breaking changes.
Therefore, for our existing APIs, we have not changed endpoints or response messages. Instead, we have integrated the new, streamlined terminology by adding clear comments and annotations within the API specifications and documentation. This ensures stability for your current integrations while providing immediate clarity on the preferred, future-proof terminology.
This is more than just a surface-level change; it's a fundamental commitment to reducing cognitive load and accelerating your development cycles. Expect more initiatives this year focused on making our platform the easiest and most enjoyable to build on. We believe this new consistency will immediately translate into a sharper, faster, and more enjoyable development journey.
View the Full Mapping
For a granular look at every term we’ve updated—including the "Before" and "After" mapping—please refer to the official tracking issue on GitHub: 👉 GitHub Issue: Inconsistent Naming
Happy coding!