How we built a single design system for 20+ teams

At AeroPort, we have 20+ teams and a lot of microfrontends. Without a shared design system, this quickly turns into a classic IT horror story: buttons drift, spacing takes on a life of its own, and the user suddenly “moves” into a different product just by opening a neighboring module.

We built a design system + UI Kit so all services speak to the user in the same visual language. The key here is not just the components, but also governance: rules for how the system evolves, standards for code review, and solid component documentation.

The result: teams ship features faster, and the interface stays consistent — without any “surprises” where modules meet. Against the backdrop of the trend toward scalable frontends and AI-accelerated development, this is no longer a “nice to have,” but the baseline.