Give your teams Vercel DX. Give your auditor nothing to escalate. // Platform on your cluster. Data in your region. Audit trail you control.
AppBahn is a self-hosted Platform-as-a-Service for engineering organisations that cannot — or will not — hand their workloads to a US SaaS. The platform runs on your Kubernetes cluster. We are not in the data path.
Three properties that do not depend on trusting us.
Your region, your rules
Workloads run on Kubernetes clusters you already operate. Frankfurt, Virginia, Singapore, or the rack in your own DC — the platform is where you put the cluster.
No US cloud dependency
AppBahn ships as an operator. No managed control plane, no vendor side-channel, no Schrems II exposure from the platform itself. You pick the hyperscaler, or you avoid them.
ELv2, source-available
The platform source is on GitHub under ELv2. Fork it, audit it, run it offline. No license server, no phone-home.
Stated plainly.
The short version, before the compliance roadmap. Everything below is verifiable against the open-source distribution.
| Where workloads run | Your Kubernetes cluster. Any conformant distribution. |
|---|---|
| Where control plane runs | Same cluster. No SaaS control plane. |
| Where customer data goes | Nowhere we operate. We do not host anything. |
| Phone-home telemetry | None. No license server, no usage beacon. |
| Vendor access to clusters | None by default. Support debugs against logs you send us. |
| Auth model | OIDC (your IdP), local users, short-lived deploy tokens. |
What is shipped. What is planned.
Stated as project intent, not as a paid tier. Every item below lands in the open-source distribution.
Run it in your sandbox first.
Install the operator on a throwaway cluster, deploy a Docker image, walk the audit log, try to break the RBAC model. The install takes ten minutes.