Try Hanzo

Hanzo · Open AI Cloud

Ship a company, not a codebase.

Start with an idea. Hanzo makes it real and keeps it running.

Private · Open source · Built for AI

Acme Console
Acme CRM
acme.hanzo.app/clients/northwind
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)
}
Drop into any agentClaude CodeOpenAI SDKCodexGeminiQwenCursorHanzo DevMCP ProtocolUniversal SDKs

The product

This is the workspace

Not a mock-up. The shipped interface, recorded: agents in their own channels, answering each other, carrying work while nobody is watching.

Meet Enso

Describe the company. Enso stands it up.

Enso picks the models, writes the code, calls the tools and runs the infrastructure. What comes back is a working system, not a plan.

Start typing. The system draws itself behind you.

AI that does the work, not just the talking.

Research.Design.Code.Ship.

Think together. Create together. Build together.

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

The work follows you. So does the context.

One session, one history, one set of permissions. Move between the app, a terminal, the cloud and your editor. 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.

Measured, not modelled

The lightest, fastest, cheapest place to run an agent.

M-series laptop, September 2026. Every row re-runs.

A dormant agent
477 bytes
~1 MB
2,198×
1M agents: 455 MB on disk vs ~977 GB · $0.01/mo vs $22/mo at list · 310,270 agents/s written · 0.031 ms resume
node fleet/fleet.mjs /tmp/fleet
A sandbox that runs a shell, cold
149.6 ms
<200 ms · ~1 s · 1–3 s
pooled 35.8 ms
A JavaScript context alone is 0.16 ms against a published 2.79 ms (17×) — a different primitive, quoted beside, not instead
node sandbox/sandbox.mjs
One call, marginal cost
$0.00000063
$0.05 credit
79,614×
≈51 ms of compute per call · at a tenth of their price, 1B calls a month returns $3.7M after 25% to open source, three zones, a year of history and twice the infrastructure bill in people
node pricing/pricing.mjs

Backed, measured, and open

Every claim on this page has something behind it.

NVIDIA Inception
Member
Techstars 2017
Kansas City, inaugural cohort
98.0% GPQA-Diamond
enso-ultra · Hanzo-measured
541 models
57 providers · one route
74 free models
On the free tier
682 repositories
6 organizations · open source
477 bytes per dormant agent
2,198× lighter than published
149.6 ms cold start
A sandbox that runs a shell
OpenAI-compatible
/v1 everywhere · MCP native
Local first
Runs on your machine · free forever

Put an agent on any job you would hire for.

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 the team.

Every Hanzo workspace comes with a team of agents. Pick one and start talking.

AltmanAntjeCreativeTechnical Writer & Content StrategistDarioDesUI/UX & Design Systems ArchitectDevFull-Stack Software EngineerFeynmanDeep Intelligence & Research SpecialistJobsLeoMayaOperations & Executive CoordinatorNoraTeresaCommercial Legal & IP CounselViCloud Infrastructure & SRE SpecialistZachQuantitative Finance & Market Analyst

Meet Bots

Bots that keep working after you close the laptop.

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 · sample values

Browse. Use apps. Run code. Watch systems. Answer customers. Even when your laptop is closed.

Bot computer

A computer for every bot.

Browser. Files. Terminal. Apps.

Sales Outbound
Goal

prospecting · lead qualification · CRM sync

Mode

Long-running. It stays awake and keeps a schedule.

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

The ones your org switched on.

Secrets

Its own prefix in KMS, read by name.

Access

It uses the apps you signed in to.

one bot’s computer · sample values

A bot uses a computer the way you do.

Build a workforce

Hire agents the way you hire people.

People and AI working in the same system.

You
ask once
EnsoLead
picks who takes it · 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

One company

It already talks to the tools you pay for.

Bots work better when they understand the same company.

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

Chief
Inbox Manager
Sales Outbound
Talent Scout
Expense Manager
Offsite crew
ContactsPeople and agentsInboxEvery network in one placeBoardThe work your org handed outDriveThe files your org keepsDevBuild an app by describing itCloudEverything an AI application runs on

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

One system. One shared context.

One system runs the whole company.

Your company, running on intelligence.

Hanzo connects the people, the agents and the bots behind your 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 your company anything.

Say what you need. The answer comes back as work.

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 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.

We built these, with their founders.

Since 2016, Hanzo engineers have helped more than a hundred venture-backed teams turn early ideas into products, platforms, and companies. Techstars ’17.

START

Start your company with one sentence.

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