Deploy an image and invoke it. Deployments, triggers, secrets, metrics and logs are all part of the same surface, so a function you ship is a function you can watch.
A whole machine, by the second.
Isolated shells for agents and untrusted code.
gatewayReadyEvery request enters here, so the limiter does too.
payments-apiReadyThe service the session above is changing.
checkout-webBuildingA build is running from the last commit on main.
docs-siteReadyStatic, published by the same pipeline as the rest.
api.hanzo.ai/v1/functions
Open in the consoleExample project. Every name in it is one you would give your own.
Admission, auth, routing, streaming and responses are boundary functions around the stack rather than another inference step. Outbound calls carry delegated credentials that stay in KMS.
A modular feedback architecture, not a claim of unattended production self-modification. Only candidates that meet the relevant evaluation and release gates are promoted.
MeasureTraces · regressions
Research / recursive improvement
Your cloud shouldnot lock you in.
The platform is open source, and the image we operate is the image you can pull: the same API and console on your cluster, in your network or on a laptop.
GPU targets are parallel hardware backends, not sequential stages. Zen is generative reasoning; Kai provides decision intelligence. ZAP is a native RPC protocol for supported interconnect paths. Research and evaluation form a gated improvement loop. “Native” describes Hanzo’s architecture surfaces; not every implementation, weight, driver or operating system is owned or open sourced by Hanzo.
Build on the stack. Or run it yourself.Build on the stack. Or run it yourself.
Models, agents, compute, data, security and observability behind one API, from prototype to production.