One platform. Every layer.
Models, agents, the record they leave, and the machines underneath. One API for all of it.
The system
One OS. Every layer of the company.
From the company down to the machines under it, with learning and governance across every layer.
10 of 120 route families · read from /v1/openapi.json
One system from the first prompt to production.
Ask a question, ship a change, launch a product, or run the stack yourself. Every path opens onto the same models, agents, data, and policy.
Ask
Use every model through one conversation and one API. Your app stays as it is.
Build
Give Dev a goal. It reads the repo, makes the change, runs the tests, and prepares it to ship.
Deploy
Launch with data, identity, secrets, storage, search, and events already connected.
Own it
Take the same open stack to your Kubernetes or laptop. Keep the control plane and data where you choose.
Agent runtime
Agents with hands.
Enso decides. Agents coordinate. Tabs gives them somewhere secure to act.
one tool dispatch, as the run’s span records it · sample values
Autonomous within boundaries. Accountable everywhere.
Every action leaves the same record, whoever or whatever started it.
one audit record · sample values
Every tool has a permission, every secret a policy, every execution a boundary, and every consequential action an approval when you require one. Identity, authorization, secrets, isolation, networking and audit are built into Hanzo OS.
See the whole company think.
One trace connects the objective that started the work to everything that followed.
Logs, metrics, traces, sessions and scores share the same operational context.
Everything works better together.
install, sign in, start working
The services an app needs anyway
Platform ships your code. These are the pieces it lands next to. Deploy each one beside your app, or reach it on Hanzo Cloud.
Core Services
Auth & IAM
Authentication, SSO, OAuth, JWT, and sovereign user management out of the box
Serverless Functions
Serverless functions with automatic scaling and edge deployment
Database & Datastore
High-performance SQL, vector search, and real-time subscriptions
Object Storage
S3-compatible distributed object storage with global CDN integration
Realtime Sync
WebSockets, presence, and live state replication for collaborative apps
Secrets & KMS
Hardware-backed secret management, envelope encryption, and key rotation
Additional Services
"The wise engineer owns their tools, lest their tools own them."
Principle 14
Where it runs is your call
Same platform, same console, same API. You pick the machines.
Self-Hosted
One command on a server you already pay for. The whole platform, on hardware you can walk up to.
- ✓ Runs anywhere Docker runs
- ✓ Scales out across a Swarm cluster
- ✓ Drives a Kubernetes cluster you own
Hanzo Cloud
The same platform, run for you. Sign in and deploy.
- ✓ The machines are already running
- ✓ Deploy on push, or only on a tag
- ✓ Metered and billed per organization
Hybrid
Run the control plane on your own server. It deploys to the servers and clusters you already have.
- ✓ Servers stay where they are
- ✓ One console over all of them
- ✓ Per-app target: this host, Swarm, or Kubernetes
Open source, all of it
Apache-2.0. Forked from Dokploy, and it says so in the NOTICE.
Apache-2.0
Use it commercially. Change it. The upstream attribution travels with it.
It is your server
Builds, images, databases and backups sit on machines you chose, in a region you picked, under credentials you hold.
Read the code
The code behind every deploy is right there, and so is the OpenAPI document the console itself calls.
Up to 5% of compute goes back to open source
Every deployment is SBOM-verified. Contributors to Dokploy earn a share of compute revenue — transparent, on-chain, and customizable by the community.