Hanzo

Hanzo PaaS

The platform.hanzo.ai control plane for deploying and operating services on Hanzo's Kubernetes clusters.

Hanzo PaaS

API reference · Hanzo PaaS API → — every endpoint, generated from the OpenAPI spec.

Hanzo PaaS is the deployment and operations control plane for the Hanzo platform, served at platform.hanzo.ai. 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.

Control planehttps://platform.hanzo.ai
Canonical APIhttps://platform.hanzo.ai/v1
AuthHanzo IAM (interactive) · API key / service token (machine)
SecretsHanzo KMS via KMSSecret CRDs — zero plaintext
IngressHanzo Ingress + cert-manager (automatic Let's Encrypt TLS)

How it fits together

push image / git  ──▶  platform.hanzo.ai  ──▶  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/environment/application model, the /v1 container redeploy, the build pipeline, clusters, domains, and the observe/drift board — 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

How is this guide?

Last updated on

On this page