Skip to content
AOZUMIDocs

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

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.

The AOZUMI Cloud console on its Apps page. An orange sidebar lists Apps, Deployments, Usage, People, Activity and Settings, then the tools Foldy, Canvas and Agents. Four app cards show the statuses Live, Asleep, Needs setup and Failed, each with one action.
The Cloud console. Each app card shows what visitors get now and the one thing to do next.

Quick start

The fastest path for a static site or single-page app that already builds on your machine:

Terminal
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

  1. InspectionFor GitHub imports, AOZUMI reads the repository and reports the framework, the environment variables it needs and a security review.
  2. PlanYou see what will run and anything still missing, such as secrets. Findings that need a decision wait for you.
  3. 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.
  4. 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

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 .