Skip to content
Docs

Deploy from GitHub

Sign in with GitHub, choose a repository, review the launch plan and security findings, deploy, and share a link to your app.

Before you start

  • A GitHub account and a repository with a web app in a supported stack.
  • The names and values of any environment variables the app needs, such as API keys.
  • About five minutes. Builds of larger apps take longer.

No repository? The CLI publishes a folder from your machine instead.

Sign in with GitHub

Go to aozumi.dev/signin and continue with GitHub, then finish the short workspace setup. Signing in only tells Aozumi who you are; it does not grant access to any repository.

Pick a repository

  1. Connect GitHubInstall the Aozumi GitHub App and choose exactly which repositories Aozumi may inspect. Private repositories need this installation.
  2. Choose or paste a repositoryPick one of the approved repositories, or paste a github.com URL.
  3. Wait for the inspectionAozumi reads the repository and reports the framework, the branch, the environment variable names the app expects, and a security review of what the code can do.

Review the plan

Before anything runs, Aozumi shows a launch plan. Read three parts of it carefully.

Security review

The inspection ends in one of three states:

Clear
Nothing needs a decision. You can import straight away.
Review
The code does something worth knowing about, such as running dependency install scripts, evaluating code dynamically, allowing every browser origin, or calling a private network address. Read each finding and confirm it to continue. Aozumi records who accepted it and for which commit.
Blocked
The repository asks for host-level permissions. Remove them from the repository and import again; this cannot be accepted.

Environment variables

The plan lists the variable names the app expects. Add values now or after import; the plan shows the app as not ready to deploy while required values are missing. See environment variables.

First audience

Choose who can open the app: anyone with the link, your team, only you, or specific people you invite. Anyone with the link is preselected, so change it now if the app is not meant for everyone. You can change it at any time from the app's Access tab. See link access.

Deploy

Importing creates the app; it does not deploy it. Start the deploy from the app's Deployments tab. The release moves through queued and building to live, and the console shows progress and logs as it goes.

A queued deploy is not live yet. If a deploy fails, read the build output first, then the runtime logs. Aozumi adds a diagnosis for common causes such as a missing variable or a server that does not listen on the PORT environment variable, which Aozumi sets for you. See logs and health.

Deploy on push

Turn on deploy on push in the app's deployment settings to deploy every push to the default branch. It is off by default. Each push is inspected again, and it deploys only if the review is clear or finds nothing beyond what an owner already accepted. Anything new waits for a person, with the reason recorded in the audit log.

Share

When the release is live, use Share to invite teammates by email or create a share link. People you share with open the app only. They do not see the code, the workspace or the deploy controls.

A share link can expire after a day, a week or a month, and you can turn it off at any time. Creating a new link for an environment replaces the old one.

After the first deploy

Questions

Does signing in give Aozumi access to all my repositories?
No. Signing in with GitHub only establishes who you are. Aozumi can read a repository only after you approve it in the Aozumi GitHub App installation, where you choose exactly which repositories it may inspect.
Can I deploy an app built in Lovable, Bolt or v0?
Yes, once its code is in GitHub. Export the project to a GitHub repository first, then paste that repository URL into Aozumi.
Does importing deploy the app?
No. Importing creates the app and its launch plan. Deploying is a separate step you start when the plan has nothing missing.
What happens if a deploy fails?
The release is marked failed and the previous live release, if any, keeps serving. Open the deployment to read the build or runtime logs and Aozumi's diagnosis, fix the cause, and deploy again.

Checked against the product on .