Hanzo PaaS

Hanzo PaaS is the deployment and operations control plane for the Hanzo platform. The Studio (browser UI) is at platform.hanzo.ai; every programmatic call goes to api.hanzo.ai/v1/platform, the one Hanzo API host. You register an application, point it at a container image or Git repository, attach a domain, and the platform builds, deploys, and operates it on Hanzo's Kubernetes clusters — with deployment history, rolling updates, and drift detection.

How it fits together

push image / git  ──▶  api.hanzo.ai/v1  ──▶  operator  ──▶  Kubernetes
                     (declare + drive)      (reconcile)    (run + serve)
                              ▲                                     │
                              └──────────  observe (drift)  ────────┘

• Declare & drive — register applications and trigger deploys through the control plane.
• Reconcile — the operator applies the declared state to the cluster.
• Observe — the control plane tracks declared vs running vs latest image tags and surfaces drift.

Secrets are never embedded in manifests — workloads read them from Hanzo KMS, synced into Kubernetes with KMSSecret CRDs.

Get started

The full control-plane reference — the project/application model, /v1/platform deploys, /v1/runner builds, clusters, and domains — lives in the Platform docs:

The container/app model and deployment workflow

The /v1 control surface and the /api build pipeline

API keys, service tokens, and IAM tokens

Create, deploy, redeploy, and operate applications