Try Hanzo

Hanzo · Open AI Cloud

Build what’s next.

Think it. Create it. Build it. Run it. Hanzo brings AI, agents, tools, data and infrastructure together, so an idea can become something real.

Private · Open source · Built for AI

Drop into any agent
Claude CodeOpenAI SDKCodexGeminiQwenCursorHanzo DevMCP ProtocolUniversal SDKs
Setup
Claude Codeclaude mcp add hanzo https://api.hanzo.ai/v1/mcp
Cursorcursor --add-mcp https://api.hanzo.ai/v1/mcp
Codex / OpenAIcodex --mcp https://api.hanzo.ai/v1/mcp
MCP Gatewayapi.hanzo.ai/v1/mcp
Hanzo Dev CLIcurl -fsSL https://hanzo.sh | sh
Browse skills — hanzoskills.com →Open the raw setup prompt (/skill.md)View agent integration docs →

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.

HHanzo Console
Dev Workspace
cloud.hanzo.ai/workspace/payments-api
prod-us-east
Inference: 148 tok/s
Latency: 18ms
Tests: 14/14 passed

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.

gateway/limit.go+42 lines
// Token-bucket rate limit per API key
lim := rate.NewLimiter(100/60.0, 10)
if !lim.Allow() {
    return c.SendStatus(429)
}

AI that works with you.

Research.Design.Code.Analyze.Ship.

Think together. Create together. Build together.

Start with one AI. Add more when you need them.

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

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.

Build an agent for anything.

Give it a job. Give it context. Give it tools. Give it permission to act.

you Add rate limiting to the payments API.
ensoReads the request. Picks who takes it.
Researcher
code · search · every route the limiter covers
Engineer
fs · apply_patch · gateway/limit.go and its test
Designer
ui · search · a limit notice for checkout-web
Operator
exec · run · hanzo deploy
tools · fs · exec · code · git · fetch · workspace · ui · and six more

one task, four agents · sample values

Researcher. Engineer. Designer. Analyst. Sales. Support. Operator.

Use one. Or build a team.

Meet Bots

Some work shouldn’t stop.

Agents help when you ask. Bots keep going.

InboxNeeds approval
Inbox Manager
Online · 24/7
disk → bot-inbox-manager
secrets → bots/inbox-manager
Outreach queueWaiting
Sales Outbound
Online · 24/7
disk → bot-sales-outbound
secrets → bots/sales-outbound
ExpensesScheduled
Expense Manager
Online · 24/7
disk → bot-expense-manager
secrets → bots/expense-manager

three bots on their own computers · the states are sample values

Browse the web. Use apps. Run code. Watch systems. Answer customers. Publish content. Research markets. Check inventory. Monitor competitors. Keep the work moving. Even when your laptop is closed.

Bot computer

A computer for every bot.

Browser. Files. Terminal. Apps. Memory. Identity. Tools. Models. Private sandboxes. Persistent storage.

Sales Outbound
Goal

prospecting · lead qualification · CRM sync

Mode

Long-running. The set is closed, and the platform refuses that mode without a schedule, so a bot that stays up carries the clock it wakes to.

login.salesforce.com
class   desktop · plus a screen
runtime gvisor · the boundary
project bot-sales-outbound · its disk
volume  attached · outlives the lease
status  screen openrunning
Tools

Only what the org has switched on. A name nothing has activated comes back unknown.

Secrets

Its own prefix in KMS, read by name and never by value.

Access

A connector belongs to the person who signed in to it, so a bot reaches an app through that grant rather than a login of its own.

one bot’s computer, as the lease answers it · sample values

Bots don’t just call APIs. They can operate computers.

Build a workforce

They don’t have to work alone.

People and AI working in the same system.

You
ask once
EnsoLead
reads the request · picks the models · calls the tools
Inbox
Sorts what came in, answers what it can, and parks drafts for your ok.
Sales outreach
Researches accounts, drafts messages in your voice, and leaves a review list.
Research
Reads, compares, and writes up what it found.
Bug reproduction
Reproduces the report, finds the failing step, and files it.
Expenses
Collects the receipts and files the report.
Chief of staff
Keeps the other bots on task and tells you what changed.

the bots an org hires, each with the work it stands for

One company

Everything connected.

Bots become dramatically more useful when they understand the same company.

Customers. Sales. Marketing. Engineering. Support. Finance. Operations. Products. Data. Infrastructure.

the rooms an org shares, and the bots that work in them

One system. One shared context.

The autonomous OS.

Your company, running on intelligence.

Hanzo connects the people, agents, bots, data, tools, infrastructure, and decisions behind the business.

See what’s happening. Understand why. Decide what matters. Let AI handle what comes next.

What needs my attention?
Revenue+12% this week
SupportRefund requests rising
EngineeringRelease ready
GrowthCampaign outperforming baseline
Operations1 approval required
ReviewApproveInvestigateHandle it

one question and what comes back · sample values

Ask the company.

Not the dashboard.

What changed? What’s working? What’s broken? Where are we losing money? What should we build next? Which customers need attention? Where should we grow?

Handle it.

  1. “Why did conversion fall?”
  2. Chief puts the team on it
  3. Research reads the funnel
  4. Analytics finds the drop
  5. Engineering traces it to checkout latency
  6. Enso proposes the fix
  7. You approveapproved
  8. Engineering deploys
  9. Conversion recovers

one question, from ask to outcome and back · sample values

Let the company run itself.

Set the direction. Set the rules. Let Hanzo handle more of the rest.

Agents think. Bots work. The platform connects everything. You stay in control.

12:10 AMInbox Manager clears the overnight threads.
3:42 AMExpense Manager matches the receipts.
6:15 AMSales Outbound queues the drafts.
8:03 AMTalent Scout drafts the intros.
9:00 AMYou open Hanzo.

one night, four bots · sample values

Everything important is waiting for you.

START

Say what you want.

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