Supported stacks
What Aozumi can run today, how each stack runs, and how sure we are. Every stack has a live test app deployed through the real pipeline, and ratings change when that evidence does.
Scorecard
| Stack | How it runs | For visitors | Rating |
|---|---|---|---|
| React / Vite | Built once in the static builder; files served by Aozumi's static path | No startup wait; public pages are edge-cached | Test app live; the last five production Vite deploys are live. |
| Static HTML | Same static path as Vite | No startup wait; edge-cached when public | Test app live. |
| Next.js (static export) | Static path, served from out/ with clean URLs (/about serves about.html) | No startup wait; edge-cached when public | Test app live. |
| Next.js (server) | Dedicated Next.js runtime that sleeps when idle | Wait after sleep; wakes faster than the general container runtime | Test app live. |
| Node.js / Express | Container that sleeps when idle | Wait after sleep | Node and Express test apps live. |
| Remix | Container that sleeps when idle | Wait after sleep | Test app live. |
| FastAPI | Container running uvicorn on the module that creates the app | Wait after sleep, plus pip install on first boot | Test app live. |
| Flask | Container running gunicorn when listed, otherwise flask run, on the real module or factory | Wait after sleep, plus pip install on first boot | Test app live. |
| Django | Container running gunicorn on the wsgi module when listed, otherwise runserver; collectstatic output is served | Wait after sleep, plus pip install and collectstatic on first boot | Test app live, with /static/ CSS served when DEBUG is off. Without gunicorn it uses Django's development server. |
| Go | Dedicated Go image; compiles inside the container on first boot | Wait after sleep, plus a compile on first boot | Test app live. |
What the ratings mean
- Fast for visitors, cheap to host, and proven by passing deploys.
- Works, but slower or more expensive than it needs to be. “Proven” means a live test app passed through the real pipeline.
- Likely to fail for common projects, or runs in a way unsuitable for production.
Static sites
Static HTML, Vite builds and Next.js static exports are published as files and served directly, so there is no app process to start and nothing to sleep. Public static pages are cached at the edge. Hosting costs little more than storage.
Deploy them from GitHub, or build locally and publish with the CLI, which skips the hosted build entirely.
Server apps
Apps that need a running process run in a container. Aozumi sets the PORT environment variable; your server must listen on it rather than a hard-coded port. The current release keeps serving while a new one starts, and traffic moves only when the new release is ready.
Server apps sleep when nobody is using them and start again on the next visit, which means that visitor waits. How long an app stays awake is up to you; see sleep when idle.
Python apps
Aozumi finds the start command from your source instead of assuming a file name. It looks for the module that creates the app (for example main:app or api.main:app), and uses gunicorn when your project lists it.
Python apps run pip install when they first boot, and Django also runs collectstatic; Aozumi then serves your STATIC_URL files. That makes the first start slower.
Go apps
Go apps from GitHub run in a dedicated Go image. The app compiles inside the container on first boot, so the first start takes longer than later wakes.
Questions
- Which frameworks does Aozumi support?
- Every stack below has a live test app deployed through the real pipeline. Static HTML, React with Vite, Next.js static exports and Next.js server apps are rated Good. Node.js and Express, Remix, FastAPI, Flask and Go run as containers that sleep when idle and are rated OK, proven. Django is OK with gunicorn and weak without it.
- Is there a cold start on Aozumi?
- Static sites have none: files are served by the gateway with no app process. Server apps sleep after a period without visitors, depending on the app's sleep mode, and the next visitor waits while the app starts. Choose Stay warm to turn automatic sleep off.
- Can I deploy a Docker image?
- Aozumi deploys from a repository or a CLI artifact, not from an image you push. The repository inspection recognises a Dockerfile and checks it; a container image that runs as root is flagged for review.
Checked against the product on .