Hanzo Platform
The AI‑native cloud.
Run models, agents, applications, data and infrastructure through one operating plane.
Kubernetes-native. Fully observable. Open source. Run it on Hanzo infrastructure or infrastructure you control.
GPUs · Functions · Containers · Databases · Observability · One API
One stack.Down to the kernel.
Build with agents. Route with Enso. Reason with Zen. Decide with Kai. Run on infrastructure you control.
Gateway
One entry for the AI stack: keys, orgs, admission, usage limits and routing to the right model or service.
A stable API boundary, independent of which backend runs the request.
AI API
A compatible inference interface for chat, completions, embeddings, multimodal models and agent workloads.
The same client and key can move between models without rebuilding the application.
Enso
Choose models and execution paths by capability, quality, latency and cost. Invoke a specific model when the application needs exact control.
Enso routes. Zen reasons. Kai decides.
Enso Ultra answered 152 of 159 new questions right, against 93.1% for the best single model on the same questions.
How Enso routesZen
Hanzo’s open-weight generative model family for reasoning, coding, language and multimodal generation.
The reasoning layer: language, synthesis, plans and generation.
View the measurementsKai
Typed decisions and policy-aware evaluations for choosing actions, scoring evidence and protecting agent execution boundaries.
Reasoning can generate proposals; Kai helps turn evidence into accountable decisions.
View the measurementsAgents
Composable agents coordinate tasks, use tools, schedule work and continue from intention to verified results.
Agents act across software and services instead of stopping at a response.
Hanzo Dev beside Claude Code on the same coding repairs, paired over 42 tasks both solved; 95% interval 2.06–4.36×.
Hanzo DevSandboxes
Isolated execution for code, browser work and agent tools, with controlled permissions and lifecycle.
Keep tool execution separated from model inference and production resources.
Cloud
Deploy and coordinate inference and agent systems across Hanzo infrastructure, your clusters or a hybrid environment.
One operating plane connects identity, usage, execution and infrastructure.
Node
Connect your machines to the agent execution fabric, advertise capabilities and receive authorized invocations.
Connected nodes can be invoked for the work they advertise.
Engine
The native serving engine with continuous batching, paged attention, quantization and persistent KV caching.
The inference work runs in one serving binary, from local hardware to GPU-backed systems.
View the measurementsHanzo ML
Rust tensor, neural-network and model-execution primitives with accelerated device backends.
Hanzo owns framework code close to the math, not just the API wrapper.
Kernel DSL
A first-party Rust kernel DSL targeting CUDA, ROCm, Vulkan and Metal alongside backend-specific implementations.
One portable kernel expression, optimized and validated for each device. Backend performance is workload-specific.
One kernel DSL. Four targets.
Four parallel acceleration backends, not four extra hops. First-party kernels and performance tuning for supported workloads.
Intelligence that connects to every layer.
Agent capabilities sit alongside the inference path; not every request crosses every subsystem.
Semantic + Graph
Semantic retrieval, durable memory, provenance and connected knowledge for agent work.
LoCoMo, held-out test split: every evidence turn of a multi-hop question in the top 20 for 37.5% of questions, against 18.8% for cosine search.
Code Intelligence
Symbols, ASTs, references and repository-aware code navigation for coding agents.
In. Out. Under control.
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.
Not just running. Learning.
- 01 / ObserveMeasureTraces · regressions
- 02 / ProposeHypothesizeCandidate upgrades
- 03 / IsolateExperimentSandboxed variants
- 04 / ProveBenchmarkQuality · latency · cost
- 05 / ControlGate + promoteReview · rollback
A modular feedback architecture, not a claim of unattended production self-modification. Only candidates that meet the relevant evaluation and release gates are promoted.
Inspectable product, docs and source links for each architectural surface.
CUDA, ROCm, Vulkan and Metal; backend-specific validation, never blanket speed claims.
Published measurements are scoped to a named model, workload, hardware and baseline.
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.
One runtime for every kind of work.
The same plane, held for a millisecond or for a month. What changes is how much of a machine the work needs, not what you have to learn.
Functions
Scale to zero between calls.
Containers
Your image, deployed and addressable.
Sandboxes
Isolated shells for agents and untrusted code.
Machines
A whole machine, by the second.
GPUs
Accelerators attached to any of them.
Kubernetes
The substrate all of it runs on.
Every request enters here, so the limiter does too.
api.hanzo.ai/v1/functionsOpen in the consoleThe data primitives AI applications use.
Each primitive is the right shape for its job, and they share one project, one key and one bill.
Datastore
Columnar analytics over everything you collected.
Object Storage
Objects, signed URLs, lifecycle rules.
Base
An application backend: records, rules, realtime.
Memory
What an agent is allowed to remember between runs.
One control plane. Any infrastructure.
The API, the console, the identities and the bill stay the same when the machines underneath change.
Hanzo Cloud
Capacity we operate and meter, provisioned by the call.
Your cloud account
Your credentials and your machines, under the same control plane.
Your cluster
Attach Kubernetes you already run and address it like any other.
Security is part of the cloud, not a product on top of it.
An agent gets an identity because it runs here, and the trail is written because every call goes through the same door.
Identity
One issuer for people, programs and agents, each request scoped to the org it acts for.
Permissions
Access follows the resource, not the caller.
Secrets
Held in KMS and handed only to the environment that needs them.
Audit
Actions written to a trail you can query, attributable to whoever took them.
One API. Every capability.
The same key, organization, project, policy and usage ledger behind every path. The interface changes; the system does not.
- api.hanzo.ai/v1/models
- api.hanzo.ai/v1/agent
- api.hanzo.ai/v1/function
- api.hanzo.ai/v1/provisioning/sql
- api.hanzo.ai/v1/provisioning/vector
- api.hanzo.ai/v1/s3/buckets
- api.hanzo.ai/v1/…
Five operations, one key, no glue. Each is checked against the published OpenAPI document on every build.
One org, one afternoon: a spaceship shop that did not exist this morning.
Start with the models.
GET /v1/modelsReturns the list of available models from the routing table.
Push code. Get a production system.
An address, a certificate, secrets, metrics, logs and its share of the bill come back with it, because none of them is a separate purchase.
Push
A commit to the forge starts the build.
Build
The image is built in the cluster, never on a laptop.
Release
It rolls out with its secrets and its address, ready to roll back.
Observe
Logs, metrics and traces from its first request.
Your cloud should not 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.
Pay for what runs.
Nothing is billed for existing. One organization balance and one usage ledger, and every line traces back to a request.
Models
By usage
Compute
By execution
Storage
By consumption
Managed services
By usage
Explore the platform.
Every plane, and what is in it.
Dev
CLI · Playground · Desktop · API Keys
Observe
Logs · Metrics · Dashboards · O11y · AI Metrics
Network
Gateway · DNS · Service Mesh · Nodes
Build on the stack.Or run it yourself.
Models, agents, compute, data, security and observability behind one API, from prototype to production.