Hanzo

Documentation

Build Anything with Hanzo. Every model, every tool, one key — in our cloud or on your own machine.

Hanzo

Build Anything with Hanzo

Over 400 models, one platform. Pick how much you want to type.

Build me a multiplayer snake game with a
leaderboard, and deploy it.
EnsoOur frontier model, and the default on every surfaceZen stays open weights. Meet Enso →
Get startedOr build a game →

Every model, one key

Zen
Open weights
OpenAI
GPT
Anthropic
Claude
Google
Gemini
Qwen
Open
Llama
Open
DeepSeek
Open
Mistral
Open

Browse every model we serve — the catalogue is live, so the id you copy and the rate beside it are the gateway's current answer — or see what a request costs before you send one.

The platform, by domain

Every capability has one name and one route — /v1/<name> — and lives in exactly one domain. Nothing is duplicated, so nothing is ambiguous.

Intelligence

Every model, agent and tool you can call — one key, one endpoint, and the standard chat-completions shape, so a client you already have works unchanged.

Make your first call
hanzo run zen-1 'summarize this repo'

Identity & Trust

Who someone is, what they may touch, and where secrets stay. Every other domain reads its caller's identity from here.

Set up an org
hanzo auth login && hanzo keys create --name prod

Data

Somewhere to put your data and read it back fast — relational, vector, key-value, full-text and object, each behind its own /v1 route.

Store something
hanzo kv set greeting hello && hanzo kv get greeting

Streams

Move messages and run work in the background, with delivery you can reason about rather than hope for.

Move a message
hanzo pubsub publish orders '{ "id": 1 }'

Observability

Metrics, logs, traces and evals for everything above — including the model calls, tagged by org and project so tenants stay separate.

See what is happening
hanzo o11y query 'sum(rate(http_requests_total[5m]))'

Commerce

Turn usage into money — meter it, price it, bill it. The same ledger the gateway debits when you call a model.

Meter usage
hanzo billing balance

Platform

Run your code next to everything else — one gateway in front, your choice of machine behind.

Ship your code
hanzo deploy .

Applications

The finished products built on the domains above — useful on their own, and a worked example of the platform if you are building your own.

Open the apps

Take it with you

The cloud above and the one you can run yourself are the same software — same binary, same contract, same /v1 routes. Bring your own GPU or Kubernetes, or mine on any device.

curl -fsSL hanzo.sh | bash

This is V8 · Open Edition, specified in HIP-0127: one contract, many bindings, thin clients, and a wire — never FFI — between languages. See Engineering Philosophy for the why.

Build with it

  • The hanzo CLI — one ~15 MB Rust binary that talks to any live cloud: prod, laptop, or self-host
  • SDKs — Python, TypeScript, Go, Rust and more, all derived from one contract
  • API reference — every endpoint, generated from its spec
  • ZAP protocol — Zero-Copy App Proto, the wire the Go and Rust halves speak
  • Zen models — frontier open-weight models, 4B edge to 1T+ reasoning
  • Architecture — one binary, one contract, and why

Resources

How is this guide?

On this page