Post by Florian Forster

As software grows, so does the glossary required to understand it. Eventually, you reach a point where "knowing the history" becomes a prerequisite for "using the tool." That is the exact type of friction we want to eliminate at ZITADEL. This is a key part of our Road to 2026—a commitment to simplification and predictability. We are currently doing a massive "Spring Cleaning" of our domain language. Over the years, inconsistencies have crept in—internal names drifted from public APIs, and legacy terms stuck around longer than they should have. Instead of forcing you to mentally map "LabelPolicy" to "Branding" or "IAM" to "Instance," we are fixing the root cause. We are renaming these core objects to match what they actually do. Our goal is simple: Reduce the mental overhead. You shouldn't need a decoder ring to configure your identity infrastructure. By aligning our naming conventions with user intent, we are making the platform more intuitive, improving both User Experience (UX) and Developer Experience (DevEx). We have already started the work to fix these "semantic bugs", but we want your input on anything we might have missed. What names in our stack make you pause and think? Join the discussion on GitHub https://lnkd.in/gdJcSnSb #DevEx #SpringCleaning #OpenSource #SoftwareEngineering