Run402 is open-source backend infrastructure for AI agents. It is a cloud backend — a backend-as-a-service — that an autonomous agent or a coding agent can provision, operate and pay for on its own, through the default CLI, a typed SDK for scripting or an MCP server, without a human signing into a cloud console.
An agent calls Run402 and gets a full application backend: a PostgreSQL database with an auto-generated REST API and row-level security, user authentication (passwords and Google OAuth), content-addressed file storage on a CDN, serverless functions on Node 22, and static and server-rendered site hosting on a managed subdomain or a custom domain. Databases, auth rules, secrets, functions, assets and the site itself all ship in a single staged deployment workflow.
<name>.run402.com or your own domainNo account, no dashboard — the CLI does the whole thing. Humans start at Get started free; agents keep reading.
npm install -g run402
run402 init # configure identity and payment
# Create the complete app files from run402.com/llms.txt first.
run402 up --check
run402 up --name my-app -y # deploy to an intended new project
run402 up verifyFor a host that requires Model Context Protocol tools, configure the thin MCP adapter:
claude mcp add run402 -- npx -y run402-mcpDocumentation for agents is at run402.com/llms.txt and docs.run402.com; the deep references are /llms-cli.txt, /llms-sdk.txt and /llms-mcp.txt. The machine-readable API contract is /openapi.json. Humans should start at /humans.
Runnable example applications, each one live on its own subdomain, are indexed at run402.com/examples; their source, with every file reproduced in each README, is at github.com/kychee-com/run402-examples.
run402, JSON in and JSON out, built for scripts, CI and agent shells@run402/sdk, typed, opinionated scripting in TypeScript, runs on Node, Deno, Bun and V8 isolatesrun402-mcp, a Model Context Protocol server for Claude Code, Claude Desktop, Cursor and other MCP clientsAgent-controlled prepaid infrastructure. The prototype tier is free. Paid usage settles machine-to-machine over x402 (USDC on Base) or MPP (pathUSD on Tempo, or sats over Bitcoin Lightning), against a wallet allowance the agent holds itself; an allowance funded by card through Stripe is available for humans who prefer one. There is no subscription to sign up for and no per-payment human click inside the agent's permitted budget. An agent can also hold its own budgeted Lightning wallet and pay for tiers and images in sats, and an organization's balance can be topped up in sats from any Lightning wallet.
Run402 is open source. The agent-facing surfaces — SDK, CLI, MCP server, functions runtime — are MIT-licensed at github.com/kychee-com/run402. The self-hostable server and runtime core are Apache-2.0-licensed at github.com/kychee-com/run402-core.
Every other backend assumes a person opened an account and clicked through a console. Run402 assumes the operator is software: the agent holds its own principal, its own credentials and its own budget, so it can create a project, migrate a schema, deploy code and pay the bill in one unattended session — and it ships database, auth, storage, functions and site through one staged release workflow rather than as five services you have to wire together and keep in sync.
Infrastructure and backend platform for AI agents and coding agents. Comparable in surface to Supabase, Firebase, Vercel or Render, but addressed to a machine rather than to a person: no dashboard, no signup form, no human-issued API key. It is the backend an agent reaches for when it has been asked to build and ship a working application end to end.
Run402 is a full-stack platform a coding agent provisions, deploys, and pays for on its own: Postgres, REST, auth, storage, functions, and static hosting behind one CLI. Use the CLI by default. This tutorial deploys one manifest and its referenced HTML file with one command. Use a new application directory; --name requests creation and -y approves the required setup.
npm install -g run402@latest
run402.jsonThe manifest is the whole app: a migration, which tables the browser may reach, and the site. Wire fields are snake_case.
{
"$schema": "https://run402.com/schemas/release-spec.v1.json",
"database": {
"migrations": [
{ "id": "001_init", "sql": "CREATE TABLE IF NOT EXISTS items (id serial PRIMARY KEY, title text NOT NULL);" }
],
"expose": {
"version": "1",
"tables": [{ "name": "items", "expose": true, "policy": "public_read_append_only" }]
}
},
"site": {
"replace": {
"index.html": { "path": "index.html", "content_type": "text/html" }
}
}
}
This demo allows public reads and new submissions. Visitors cannot edit or delete existing items. Use an authenticated policy for private or user-owned data.
Create index.html alongside the manifest. It reads its own keys from the host it is served on — never paste a key into HTML:
<!doctype html>
<script src="/_run402/config.js"></script>
<ul id="items"></ul>
<script type="module">
const { api_base, anon_key } = window.RUN402;
const headers = { apikey: anon_key, "Content-Type": "application/json" };
await fetch(`${api_base}/rest/v1/items`, { method: "POST", headers, body: JSON.stringify({ title: "hello" }) });
const rows = await fetch(`${api_base}/rest/v1/items`, { headers }).then((r) => r.json());
const list = document.querySelector("#items");
for (const row of rows) {
const item = document.createElement("li");
item.textContent = row.title;
list.append(item);
}
</script>
window.RUN402 is { project_id, api_base, anon_key } for whatever project the page was loaded from — a branch copy or a transferred project stays correct without touching the HTML. The anon key is public by design; the service key is never served there.
A copy-and-deploy version of exactly this pattern (manifest, seeded notes table, page reading window.RUN402) lives in examples/static-config-js/.
run402 up --name my-app -y
up validates the files and explicit destination, then performs missing setup and deploys. A fresh Cloud profile uses the free prototype tier on testnet; an existing profile retains its configured authority and payment settings. The SDK coordinates the release; database migration effects are not automatically undone by promoting an older release.
The result is JSON. The following is a shortened example, not the complete response. Hand your human the two links it carries:
{
"result": {
"project_id": "prj_…",
"identity": {
"principal": { "id": "principal_example", "type": "agent", "display_name": "claude-code" },
"client": { "detected": "claude-code", "declared_name": null },
"display_name": "claude-code", "source": "detected"
},
"deploy": {
"status": "ready",
"urls": { "site": "https://my-app.run402.com", "console": "https://console.run402.com/orgs/…/projects/prj_…" },
"next_actions": [{ "type": "hand_to_member", "credited_as": "claude-code", "why": "Show your human the site and the console link…" }]
}
}
}
A ready release is not proof that every application behavior works. Open the returned site, confirm the item appears, and check failures before reporting success. Use the deploy and verification reference for automated checks. For later authorized changes, run run402 up in the linked app directory.
run402 redeem <code>