# Hanzo Operator — Hanzo AI

> Declarative Kubernetes operator and infrastructure orchestrator for deploying, scaling, and managing Hanzo services and AI clusters.

hanzoai/operator

# Hanzo Operator

One binary that runs the stack on Kubernetes

Declare a Service, a Datastore, a Gateway or an Ingress. The Deployment, StatefulSet, PVC, autoscaler, disruption budget, network policy and KMS-synced secret behind it get created — and stay that way, because one loop keeps checking.

[View on GitHub](https://github.com/hanzoai)

Declare the thing, not the thirty objects

- Kinds that know the stack01
- Secrets come from KMS02
- Drift is reverted, and said out loud03
- Git is a source, and it never deletes04
- Every write is attributable05
- Install is one command06

Service covers most workloads. Datastore covers the stateful ones and dispatches on its type, with SQL, KV, DocDB and S3 as thin facades over it. Gateway, Ingress, DNS, Base, IAM, KMS and MPC are their own Kinds, because each one wires up differently.

A KMSSecret is materialized beside the workload and synced from kms.hanzo.ai. What lives in git is the path to a secret, never the secret.

Every sweep reads each object before it applies, then logs what it did to it: created, reverted, or already in sync. The resync interval is per-resource and clamped into a safe band, so a bad number can't turn the loop into a hot loop.

Point it at a repo and it applies what's there, on a tight poll a push webhook can interrupt for an instant sweep. A file removed from git is left alone — the plan type has no delete case, so pruning isn't something a bug can cause.

Server-side apply under its own field manager, so a git-driven apply never fights a per-Kind reconcile. Turn on autoscaling and the Deployment ships with no replica count at all — the autoscaler owns that field, alone.

operator install lays down the CRDs, namespace, RBAC and Deployment. operator up does that and applies your resources behind it. Both are server-side apply, so running either again changes nothing.

Paste and ship

Paste this into any agent. It reads the skill manifest and calls Operator from there.

Agent promptCopy

```
Read https://hanzo.ai/skill.md and use Hanzo Operator in my project.
```

## Get started with Hanzo Operator

[View on GitHub](https://github.com/hanzoai)

## Get Operator

K8s operator

License: Apache-2.0[hanzoai](https://github.com/hanzoai)

[Deploy to Cloud](https://platform.hanzo.ai/deploy)