Download

Hanzo · Open AI Cloud

Build what’s next.

Start on your machine. Keep going in the cloud. Pick it up anywhere.

Download Hanzo

Open source · Local first · /v1 everywhere

payments-api — Hanzo

Add rate limiting to the payments API.

Read 14 files. The limiter belongs in the gateway, not the handler — one place, every route.

Wrote gateway/limit.go and a test at 100 req/min per key. Tests pass.

Same work. Every surface.

One session, one history, one set of permissions. Move between the app, a terminal, the cloud and your editor and pick up mid-sentence.

AppThink and build
CLIDrive it from a shell
CloudKeep it running
EditorLand the change

Meet Enso

Ask once.

Describe what you want. Enso reads the request, picks the models, calls the tools and stands up the infrastructure — then hands you back the work, wherever you are.

Start typing. The system draws itself behind you.

ON YOUR OWN MACHINE

Your laptop is the cluster.

One line installs the CLI. The next one boots a real Kubernetes control plane inside a native microVM — Virtualization.framework on a Mac, KVM on Linux — and hands you a kubeconfig your existing tools already understand. Nothing to install underneath it.

~/work
curl -fsSL https://hanzo.sh | sh
hanzo → /usr/local/bin/hanzo
hanzo up
→ creating the k3s checkpoint (downloads k3s once)…
✓ k3s is up — API at https://127.0.0.1:64437.1s
export KUBECONFIG=~/.kube/hanzo.yaml
kubectl get nodes
NAME STATUS ROLES AGE
hanzo Ready control-plane,master 4s
hanzo vm run --allow-net alpine
✓ booted0.30s
0.30s

to boot the microVM — the same on Apple silicon, Ryzen and GB10.

7s

from cold to a Ready node, every platform we ship.

No Docker

and no daemon, no VM manager, and no cloud account to open.

START

Say what you want.

A sentence is enough to open a chat, start a coding agent, or put something in the cloud.

Deploy NowChatDocs