Kubernetes-native PaaS

Ship like Vercel.
Run on your own rails. // Vercel-class DX. Your infrastructure. Your rules.

AppBahn is a self-hosted Platform-as-a-Service that deploys apps from Git or Docker onto any Kubernetes cluster. Real orchestration — not Docker Compose wrappers. Your data, your region, your compliance.

Read the docs Star on GitHub
Image → live · today's deploy path pipeline ready
01
image
Container image reference
02
api
Resource recorded by the platform
03
operator
Deployment, Service, Ingress applied
04
tls
cert-manager issues the certificate
05
live
{slug}.{env}.{cluster-domain}
Runs on
KubernetesPrometheusVictoria LogsTraefikcert-manager
— Positioning

Vercel-class DX on real infrastructure — and it stays self-hosted.

Most self-hosted PaaS tools are Docker Compose in a trench coat. AppBahn runs real Kubernetes — with a real operator — so Deployments roll, Ingress routes, TLS issues, and your cluster's autoscaler sees the workloads AppBahn creates exactly like any other Kubernetes workload.

01 · KUBERNETES-NATIVE

Real orchestration

A native operator manages Deployments, Services, and Ingresses directly. No Compose wrappers. No external GitOps. Just Kubernetes, the way it was meant to be used.

02 · DATA SOVEREIGNTY

Your infra. Your region.

Runs on any Kubernetes cluster — on-prem, in your VPC, or at the edge. Application data, logs, and secrets stay on your cluster. Your compliance posture stays yours to argue, not ours.

03 · MULTI-TENANT

Workspaces → Resources

A four-level hierarchy with RBAC at every tier. Give each team a workspace. Each product a project. Each branch an environment. Each service a resource.

— The landscape

Self-hosted, not SaaS — on purpose.

There is no AppBahn-operated cloud. Every other self-hosted option in this space is either a Docker Compose wrapper or a Kubernetes YAML editor. AppBahn is the one that gives you Vercel-class DX on real production infrastructure — on your cluster.

PlatformModelRegion focusSelf-hostableOrchestration
Vercel SaaS US-centric No —
Railway SaaS US-centric No —
Heroku SaaS US-centric No —
Render SaaS US-centric No —
Fly.io SaaS Global No —
Coolify Self-hosted Any Yes Docker
Dokploy Self-hosted Any Yes Docker
AppBahn Self-hosted Any Yes Kubernetes
layer 01 Web Console workspaces · rbac · resources
layer 02 Platform API teams · tokens · deploys
layer 03 AppBahn Operator Resource CRD · reconcile
layer 04 Kubernetes your cluster, any distribution
— Architecture

Three pieces. One operator.

A web console for managing workspaces, projects, environments, and resources. A platform API that records teams, resources, and deploys. And an operator that runs on any Kubernetes cluster — reconciling Resource CRDs into Deployments, Services, and Ingresses.

AppBahn integrates with the stack already in your cluster: Prometheus and Victoria Logs for observability, cert-manager for TLS, whichever Ingress controller you already run. Everything visible in the console.

— Multi-tenant by design

Workspace → Project → Environment → Resource

A four-level hierarchy with RBAC at every tier. Model your org once; everything else inherits.

01 · TOP

Workspace

Tenancy boundary. SSO, audit log, quotas. Usually one per organisation.

acme-corp
02

Project

A product or codebase. Groups related services together.

storefront
03

Environment

Isolated deploy target. Separate config, RBAC, and domains per environment.

production
04 · LEAF

Resource

A running service backed by a container image. Scales per resource.

api-gateway
— Ready when you are

Deploy the platform. Then deploy on it.

Install the operator on your cluster in under ten minutes. Open source, ELv2 licensed, built in Europe.

Read the docs Download the CLI Star on GitHub →