AOZUMI documentation
Ideas, deployed. AOZUMI has three products that share one account and one set of workspaces. Pick the one you came for.
Three products
- BetaAOZUMI CloudDeploy a web app from GitHub, your terminal or an AI coding tool. Choose who can open it, add domains, variables and a database.aozumi.dev/console
- By inviteAOZUMI DBSQLite databases served over HTTPS. Use one from an app, a script or your laptop with the client you already use.db.aozumi.dev
- Cloud by inviteAOZUMI AgentsCoding agents in Hachi, the Mac app. Run them on your Mac, or give a thread its own cloud sandbox that keeps working.Hachi for Mac
Three ways to deploy
Cloud takes your app from any of these. They all end in the same place: an app in your workspace with a link you control.
- From GitHubSign in, choose a repository, review the plan and put the app online from the console.
aozumi.dev/console - From your terminalBuild locally and publish the output with one command.
aozumi deploy my-site - From an AI coding toolConnect any MCP client with an agent key and let it run the steps.
https://aozumi.dev/mcp

Quick start
The fastest path for a static site or single-page app that already builds on your machine:
npm i -g @aozumi/aozumi
aozumi login
# in your project folder
aozumi deploy my-site
The CLI prints the site URL when the upload is verified. Read the CLI guide for flags, link access and CI use. To deploy a repository with a server or a database, start from GitHub.
What happens on a deploy
- InspectionFor GitHub imports, AOZUMI reads the repository and reports the framework, the environment variables it needs and a security review.
- PlanYou see what will run and anything still missing, such as secrets. Findings that need a decision wait for you.
- ReleaseAOZUMI builds or receives the artifact and starts a new release. The current release keeps serving until the new one is ready, so a failed deploy never takes a live app down.
- LinkThe app is served behind AOZUMI's gateway, which applies the link access you chose before a request reaches your app.
One account
You sign in with GitHub. The same account and workspaces work everywhere:
- Cloud console at aozumi.dev/console: apps, deployments, usage, people and workspace settings.
- AOZUMI DB console at db.aozumi.dev/console: databases, SQL and tokens. You stay signed in from the Cloud console.
- Hachi, the AOZUMI Agents app for Mac. It signs in with a code you approve in the browser.
Members and their roles are set once per workspace; see Workspaces and members. Keys for AI coding tools and CI live on your Profile; see API keys.
All guides
Start
Console
Configure
- Link access and sharingAnyone with the link, Workspace or Invited people only; share links and invites
- Custom domainsYour app's AOZUMI link and your own domains with automatic HTTPS
- Environment variablesEncrypted, write-only Production variables; previews on Canvas
- Databases and managed PostgresEvery database an app uses; Postgres with backups and restore
- Feature flagsTurn features on for previews, a share of Production, or chosen IDs
- Firewall and rate limitsAllow, block or log requests, and limit requests per visitor
- Log drainsSend build and runtime logs to your own endpoint
Operate
- Pull request and branch previewsOpt-in private previews for pull requests and branches
- Releases and restoreRestore an earlier release
- Size and sleepMinimum size, and Eco, Balanced, Responsive or Stay warm
- Status, logs and healthWhat each app status means, build and runtime logs, health checks
- Notifications and alertsThe inbox, and alerts to Slack or a signed webhook
- Limits and quotasBeta limits for apps, deploys, members and sizes
AOZUMI DB
- AOZUMI DB overviewSQLite databases over HTTPS: get access, create one, run SQL
- Connect from your code@libsql/client, Drizzle or plain HTTP with two .env lines
- Databases for your appsGive an app environment a database, hand one over, take it back
- Tokens and accessShow, scope and rotate tokens; who can do what
- Backups and restoreEvery change backed up; restore to a moment, in place or as a copy
- Limits and data safetySize, time and request limits, refused SQL, and keeping data safe
Agents
- AOZUMI Agents overviewCoding agents on your Mac or in their own cloud sandbox
- Install HachiInstall the Mac app, sign in, and keep it updated
- Cloud agents and plansCreate, start and stop agents; model keys; agent hours
- Keep working when your Mac sleepsCloud standby takes over a local session when the Mac sleeps
- Repositories and pull requestsClone private repos and open draft pull requests from an agent
- Agent previewsOpen a dev server running in a cloud agent
- Connect an AI coding tool (MCP)Endpoint, agent keys, tools and the review gate
- REST API and API keysScoped, expiring keys for CI: deploy, status, logs, variables
- AOZUMI DB from a coding agentAgents create databases, get the .env lines and run SQL
Building with AI coding tools? See how they work with AOZUMI, from the first check to the share link.
Questions
- What is AOZUMI?
- AOZUMI is three products under one account. Cloud deploys small web apps from GitHub, the CLI or an AI coding tool, and gives each app a link whose audience you choose. AOZUMI DB serves SQLite databases over HTTPS, for an app or on their own. AOZUMI Agents runs coding agents in the Hachi Mac app and in cloud sandboxes. All three are in beta.
- Do I need a separate account for each product?
- No. You sign in with GitHub once. Your workspaces, members and roles are the same in the Cloud console, the AOZUMI DB console and Hachi.
- Can anyone use AOZUMI DB and AOZUMI Agents?
- Not yet. Both are invite-only. A workspace owner or admin asks for access from the AOZUMI DB console or from Agents in the Cloud console, and the AOZUMI team lets workspaces in a few at a time. Local agents in Hachi need no account and no invite.
- Can an AI coding tool deploy to AOZUMI?
- Yes. Connect any MCP client to https://aozumi.dev/mcp with an agent key from your Profile, under Deploy from Cursor or Claude, sent as the X-API-Key header. The tool can check a repository, import it, set secrets, deploy, read status and logs, and create a share link. It cannot import a repository with a blocking finding, and findings that need review wait until a person accepts them.
- Is my app's link public?
- Only if you choose that. When you import from GitHub in the console, Workspace is preselected, so only people in your workspace can open the app until you pick Anyone with the link or Invited people only. New CLI sites are private unless you choose otherwise. Apps imported by an AI coding tool default to Workspace. Change it anytime on the app's Access tab.
Checked against the product on .