The hosting platform that runs on YOUR Kubernetes

Ship Next.js like Vercel.
Keep your cluster.

DeepHost turns any Kubernetes cluster into a multi-tenant application platform: git-push deploys, instant previews, SSR that scales to zero, and immutable releases — all driven by plain Kubernetes resources. No per-app pods. No vendor lock-in.

Deploy your first app See how it works

O(1)pods for N apps

<60spush to production

0idle compute cost

100%your infrastructure

Everything you expect from a PaaS.
Nothing you don't.

⚡ Git-push deploys

Push to main, get a build Job, an immutable artifact in S3, and a live Release. Every deploy is content-addressed and rollback-ready.

🧬 CRD-native

Apps, Builds, Releases and Domains are Kubernetes custom resources. ArgoCD, Helm and kubectl are first-class citizens — the API server is the database.

🌊 Scale to zero

A single shared runtime pool lazy-loads any app from object storage in seconds. Idle apps cost nothing; hot apps autoscale on real traffic.

🔐 Multi-tenant by design

Per-app environment injection, isolated Node runtimes, rate limiting at the edge, and dedicated pools when tenants need hard walls.

📦 S3 everywhere

Artifacts, ISR caches and static assets live in S3-compatible storage — AWS in prod, MinIO on your laptop. Same code, same interface.

🔀 Preview releases

Every build becomes an immutable Release with weighted traffic. Ship to 0%, share a preview URL, promote to 100% when it's green.

One pipeline. Three primitives.

Build

A Build CR triggers a sandboxed job: clone, install, compile, pack a tar.zst artifact into object storage.

kubectl get builds

Release

The operator promotes the artifact into an immutable Release with weighted traffic across stages.

kubectl get releases

Serve

The edge routes hosts to the runtime pool; hydra hydrates your app from storage on first hit.

curl your-app.com

$ kubectl get applications,builds,releases -n deephost
NAME                    READY  RELEASE
demo-storefront         true   rel-b-git-vke-2
demo-marketing          true   rel-b-git-vke-1

$ kubectl get httproutes -A   # rendered by the operator
paprika-e2e   store-front   paprika-gateway   104.156.233.70

Deploy in three commands

~/my-nextjs-app

$ deephost login --server https://your-cluster
$ deephost app create --tenant acme --name storefront \
    --framework nextjs --domain storefront.acme.com
$ deephost deploy --dir . --framework nextjs
build b-9f21ac queued… Deployed: rel-b-9f21ac ✓
→ live at https://storefront.acme.com

Prefer GitOps? Apply the Application manifest and let your controller (we ship native support for Paprika) drive every deploy.

Your cluster is already a PaaS.
You just need the control plane.

Start deploying

Ship Next.js like Vercel.Keep your cluster.

Everything you expect from a PaaS.Nothing you don't.