Developer (English)
Documentation for developers.
This page is being prepared. What follows is a draft, not the final text — do not rely on it for a legal or contractual decision.
Key points
- A REST API for users, domains and the tenant lifecycle.
- OIDC authentication through Keycloak, sessions on same-origin cookies.
- Background work runs on Temporal and is safe to retry.
1API
console-api exposes REST endpoints for users, domains and the tenant lifecycle. It is the same API the admin console itself uses, not a separate layer added on top.
2Authentication
Authentication is OIDC through Keycloak; sessions use a same-origin cookie rather than a token in localStorage. Permissions are checked server-side on every route.
3Integration
Long-running work — provisioning a tenant, cleanup, synchronisation — runs as a Temporal workflow. A failed step can therefore be retried without corrupting the steps that already succeeded.
4Environments and deployment
The platform runs on Kubernetes, is configured with helmfile, and each service has its own CI pipeline. Container images are built and then written back into the deployment repository to release.
Related pages