Teammates you can hand real work to.
Give a bot a job. It has its own computer, signs in to your tools the way you do, and comes back when the work is done. On your machine, in our cloud, or both.
Open source. Run it on your own machine if you want to — your keys and your data stay with you.
api.hanzo.ai/v1/botOpen in the consoleWhat a bot is
A teammate with its own computer
Not a chat window. A bot has a computer of its own and works while you do something else.
Its own computer
Each bot runs in its own sandbox with a browser, a terminal and your apps. Nothing it does touches your machine unless you let it.
Works where you work
Sign it in once. It uses the same tools and websites you do, including the ones that are hard to automate.
Comes back when it is done
Give it a task and go do something else. It returns with finished work and asks only when it needs your say.
Give each bot a job
One bot per job
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.
Work with many at once
Bots that hand work to each other
One gateway, many bots
Each bot has its own workspace, sign-ins and history, and each message goes to the bot it is meant for.
Sub-agents
A bot can start background runs that work in parallel and post what they found back in the chat that asked.
Bots message bots
One bot can read another’s session and send it a message, so a handoff needs no copy and paste.
Show it how it is done
Teach it a routine once
Skills
Write the steps in a plain Markdown skill, and the bot uses it whenever the job comes up.
On a schedule
Every morning, or in twenty minutes. Scheduled jobs survive a restart and can post the result to a chat.
Your say at each step
A multi-step routine can stop at the steps you mark and wait for your yes before it goes on.
Gets better as it goes
It remembers what it learns
Memory is files
Decisions, preferences and running notes go into Markdown files in its workspace, not into the model.
It looks things up
It searches those notes when it needs them, so what you told it last week still counts.
Yours to read and fix
Open the files, correct them or delete them. The next session starts from what you left.
How it starts
Three steps
Name it and give it a job
Say what you want done, in plain words.
Sign it in to your tools
Once. It keeps the access it needs and nothing more.
Let it work
It comes back when it is done, or when it needs you.
Talk to it anywhere
Message your bots where you already are
Pricing
Free on your own machine
Your machine
- Open source, MIT licensed
- macOS or Linux, Windows through WSL2
- Your model keys, or a local model
Hanzo Cloud
- Runs on your organization’s plan
- Billed for the compute and model calls it uses
- Every charge on one spend breakdown
Enterprise
- On-prem or air-gapped deployment
- Committed-volume pricing
- Security review and DPA
Install
On your Mac in two commands
Node 22 or newer, on macOS or Linux. The second command walks you through your model, channels and skills, and keeps the gateway running in the background.
Works where you work
Sign it in to the tools you use
You log in once in the bot's own browser. It keeps the session and works in the same tools and sites you do.
200 tools. Each mark belongs to its owner and is shown to say what Hanzo connects to — not to imply any partnership or endorsement.
FAQ