Hanzo writes the code and runs it. Data, sign-in, AI, storage, and deployment are ready from the first build.
Each one is a Hanzo product, connected before you ask for it. Scroll, and the builder opens the part that does it.
Say what you want and Hanzo writes the files — components, styles, routes, and the server code behind them
The generated code is right there. Read it, change it by hand, and keep talking about it in the same window
One click puts the app on a hanzo.app address. Point your own domain at it from the app's settings
API keys live in Hanzo KMS and never in the code. Sign-in and org-scoped access come from Hanzo IAM
Every app gets Hanzo Base — SQLite with realtime queries — and its schema comes from what you asked for
Once an app is published, its dashboard fills up with who came, what they did, and where they clicked
The parts worth knowing about before you type the first sentence.
Describe the app and Hanzo writes all of it — the screens, the styling, and the code running behind them. You never start at a blank file.
Ask for a change and it opens the files it needs first, so the edit fits the code around it instead of replacing it.
Upload a screenshot or a mockup and ask for that. Describe the layout in words instead, and it builds from the description.
It chooses the framework and the components that fit what you asked for, so you don't have to name them before you start.
The same infrastructure Hanzo runs on.
Global CDN, edge computing, and auto-scaling infrastructure
Hanzo Base (SQLite), Hanzo SQL, and Hanzo KV with auto-backups
Zen and Enso, plus Anthropic, OpenAI, Google and Mistral, through one endpoint
Open the builder, type what you want, and watch it get written.