# 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. Sign-up is open at https://superzero.dev/signup: email confirmation only, no card. Pricing: Free plan (no time limit; 2 projects; push, email and OAuth sign-in; no SMS). Pro plan JPY 3,980 tax included or USD 25 per month, billed from the day a card is registered: SMS verification, 5 projects. Errors with code BILLING_REQUIRED (HTTP 402) mean a Free-plan limit was hit; run "superzero billing setup" to get the card URL and hand it to a person. 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 changes no infrastructure; apply is idempotent; destructive changes need a flag. - The console is read-only. All changes go through the CLI or MCP. ## Docs - [Full reference](https://superzero.dev/llms-full.txt): config schema, commands, MCP tools, error codes - Japanese is available from the language switch on the site; the canonical text is English. 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 init | projects | keys | billing | plan | apply | verify | status | secrets | logs - MCP tools: superzero_plan, superzero_apply, superzero_verify, superzero_status, superzero_logs, superzero_config_schema, superzero_billing - SDK: @superzerodev/client — createClient() from inside the deployed app, for authentication (email, OAuth, SMS) and push. Server side only; see the full reference for why the key must not reach a browser or a mobile app.