IAM modernisation · 2022 – present

MyEvoSys

One product ecosystem, one IAM architecture: identity in ZITADEL, authorisation in Heimdall, MyEvoSys as the shared administration interface.

Back to all projects
Role
IAM modernisation lead
Timeframe
2022 – present
Context
2026 · whole product ecosystem, one IAM program
Technologies
Vue 3Node.jsExpressApollo GraphQLPostgreSQLSequelizeZITADELHeimdallOIDC / SSODockerPM2Sentry

MyEvoSys is the shared administration layer for users, organisations, services and subscriptions. In 2026 I drove the IAM modernisation for the whole product ecosystem: built the migration paths and brought them into the integration branches; rollout is in progress. Identity sits in ZITADEL, authorisation in Heimdall. 118 commits in MyEvoSys this year are mine (across all branches).

01

Context

The products had grown with their own user, session and access models. That created duplicated administration, different permission logic and significant overhead for SSO and organisations.

The modernisation needed one shared answer to: who is signed in, which organisation do they belong to, which modules may they use and how many seats are occupied?

02

My contribution

  • Drove the IAM modernisation for the whole product ecosystem: built migration paths and brought them into the integration branches; supported the rollout.
  • Moved identity to ZITADEL and authorisation to Heimdall; MyEvoSys remains the administration interface for profiles, services and subscriptions.
  • Implemented 18 migrations that removed the local user, session and access tables and removed the separate login client from the source code.
  • In 2022 I already helped shape the FloriPlan integration, the Vue 3 migration, language switching and admin tables in MyEvoSys — the IAM modernisation is part of the product history since 2022.
  • Introduced a consistent permission model with eight granular permissions and a wildcard system role; the route builder refuses to start if a route lacks permissions.
  • Built subscription, seat and app-tier management with transactional Heimdall sync and 409 handling when quotas are exhausted.
  • Built the internal organisation API for other products in the family so they can fetch data without accessing the MyEvoSys database.
  • Organisations are created and deleted across ZITADEL, Heimdall and PostgreSQL; partial failures are reported as 207 Multi-Status with per-system results.
03

Architecture & delivery

  • Vue 3 client and Node/Express server with Apollo GraphQL; PostgreSQL for profiles, services and release notes.
  • All products share the same IAM boundary: ZITADEL for identity, Heimdall for organisations, roles, modules and seats, MyEvoSys for administration, profiles and services.
  • A central route builder combines validation, Swagger metadata and mandatory permissions; GraphQL resolvers check the same permissions.
  • A separate internal REST API with a shared secret for other products in the family instead of shared databases.
System design Bringing identity, roles and billing together
Products
IAM boundary
MyEvoSys
Data & sync
Product ecosystem all products
MyEvoSys UI admin
ZITADEL OIDC · SSO
Heimdall roles · modules · seats
MyEvoSys API Express · GraphQL
Internal org API x-internal-accesskey
PostgreSQL profiles · services
Transactional sync ZITADEL + Heimdall
OIDC Roles CRUD Auth Internal API Commit

MyEvoSys remains the administration UI while identity moves to ZITADEL and authorisation to Heimdall. The internal organisation API serves sibling products without direct database access.

Design decisions
  • Identity in ZITADEL, authorisation in Heimdall, MyEvoSys as the admin UI.
  • Deleting an organisation coordinates three systems and returns partial results as 207 Multi-Status.
  • The RouteBuilder refuses to start when a route is missing its permissions.

Scroll horizontally to see the full design.

04

The hard parts

01

IAM without a local user store

Moving identity and authorisation into two external systems creates new data ownership: ZITADEL owns users, Heimdall owns organisations and permissions, MyEvoSys keeps profiles, services and release notes. Eighteen migrations had to move the existing data across the whole product ecosystem without breaking it.

02

One organisation, three systems

Creating and deleting an organisation must leave ZITADEL, Heimdall and PostgreSQL in the same state. There is no distributed transaction; partial failures are returned visibly as a 207 response with per-system results instead of being hidden.

03

Permissions you cannot forget

New endpoints must not go live without authorisation. The route builder makes permissions mandatory and aborts startup when they are missing; GraphQL resolvers check the same permissions.

05

Outcome

  • Migration paths for the whole product ecosystem are built and brought into the integration branches; rollout is in progress, with identity and permissions defined centrally.
  • Heimdall is the shared authorisation layer of the ongoing IAM architecture, MyEvoSys the administration interface for profiles, services and subscriptions.
  • Less duplicated user management and one permission vocabulary across the product family.
  • Subscriptions, seats and app tiers have a clear source and a defined enforcement point.

Contact

Let's talk about the next role.

I am looking for a position where I can take responsibility for systems and teams as a lead engineer or software architect. Ideally where reliability, data and real-world workflows meet.

Send an email [email protected]

Availability

Region
Thun/Bern
Workload
80%
Work location
On-site, hybrid or remote by arrangement
Travel
Generally yes, scope depending on the role and responsibilities
Start
by agreement