# Superzero

> One infrastructure provider for applications built by AI agents. It provisions Postgres,
> container hosting, authentication (email, OAuth, SMS OTP) and mobile push (APNs, FCM)
> from a single declarative file, driven by a non-interactive CLI or an MCP server.
> No dashboard step is required at any point.

Status: P0 prototype. Not open for sign-up. No public pricing.

Why it exists: Supabase has a database and auth but no application hosting. Vercel has
hosting but no database or auth. Outside Firebase, essentially no modern developer platform
offers SMS authentication or mobile push. Agents can write the application code; the part
they cannot do is the dashboard clicking needed to wire up infrastructure.

Design rules that shape the API:
- Every error carries a stable code and a suggestedFix naming the command to run.
- The config schema is strict; unknown keys are rejected rather than ignored.
- plan has no side effects; apply is idempotent; destructive changes need an explicit flag.
- The console is read-only. All changes go through the CLI or MCP.

## Docs
- [Full reference](https://www.superzero.dev/llms-full.txt): config schema, commands, MCP tools, error codes
- [Japanese overview](https://www.superzero.dev/ja): the same page in Japanese, for human readers.
  Note the data residency section there: compute runs in Tokyo, but the database
  currently runs in Singapore because Neon does not offer a Tokyo region.

## Interfaces
- CLI: superzero plan | apply | verify | status | secrets | logs
- MCP tools: superzero_plan, superzero_apply, superzero_verify, superzero_status,
  superzero_config_schema