Headless app platform · private beta

The backend your agent signs up for.

Git, hosting, Postgres, migrations, environments, cron and domains behind one CLI and one MCP server. Your coding agent ships the app. You approve what matters.

Give it to your agent See the loop

The stack, collapsed

Six dashboards became one tool list.

Today an app needs a Git host, a hosting platform, a database provider, DNS, a scheduler and a logging service. Each one has its own login, its own keys and a UI built for a person with a mouse. Plinth puts all of them under one account that an agent can drive end to end.

You used to openYour agent now callsWhat it does
GitHubplinth pushPrivate git repos on your account. Branches, history, server-side revert.
Vercelplinth promoteStatic frontend, serverless functions or a full Node server from one push. A preview environment per branch.
Supabaseplinth db.queryPostgres per environment, SQL migrations with automatic snapshots, nightly backups and one-command restore.
Cloudflare DNSplinth domains.connectMap a domain you own to any environment.
cron-job.orgplinth cron.addScheduled calls to your functions, with run history and status.
Datadogplinth logs.queryApp, build and cron logs plus request metrics the agent can query to debug its own deploys.

The ship loop

From commit to production without a browser tab.

Every change takes the same path. The agent runs it continuously, and every step is reversible.

  1. Commit

    Push a branch to your Plinth repo.

    plinth push feat/x

  2. Preview

    The branch gets its own URL and database branch.

    plinth env.list

  3. Migrate

    Schema changes run against a fresh snapshot first.

    migrations/*.sql

  4. Verify

    The agent reads logs and error rates before moving on.

    plinth metrics.get

  5. Promote

    Staging, then production. One command rolls it back.

    plinth promote

Environments

Staging and production come with every project.

Each environment has its own database, secrets, domain and cron schedule. Data never leaks from production into a preview unless you seed it.

preview

per branch
URL
/_p/acme-crm/feat-invoices/
Database
branch of staging, seeded
Lifetime
deleted with the branch

staging

always on
URL
staging.acme.co
Database
Postgres · nightly snapshot
Cron
paused by default

production

live
URL
crm.acme.co
Database
Postgres · nightly snapshots, 7 kept
Deploys
promote only, never direct

You stay the owner

The agent does the work. You approve the risk.

Routine actions run on their own. Anything that costs money, deletes data or touches production gets sent to you as a link to approve with one tap.

Runs on its own

  • Commit and push branchesgit.push
  • Deploy previews and stagingdeploy
  • Additive migrationsmigrations/*.sql
  • Add and edit cron jobscron.add
  • Read logs, metrics and traceslogs.query

Waits for your tap

  • Create the account or a new projectaccount.create
  • Promote to productionpromote
  • Drop a column or table in productionDROP · TRUNCATE
  • Buy a domaindomains.buy
  • Restore a backup over live datadb.restore

Interface

One MCP server. One CLI. Same verbs.

Add Plinth to Claude Code, Codex, Cursor or any agent that speaks MCP. The CLI exposes the same actions for scripts and CI, and every command returns JSON. Install it with curl -fsSL https://plinth-cloud.fly.dev/_plinth/install.sh | sh.

# add to your agent's MCP config
{
  "mcpServers": {
    "plinth": {
      "command": "npx",
      "args": ["-y", "https://plinth-cloud.fly.dev/_plinth/cli.tgz", "mcp"]
    }
  }
}
# tools the agent sees (GET /v1/tools)
  • account.create
  • project.create
  • project.list
  • git.push
  • git.log
  • git.revert
  • deploy
  • promote
  • rollback
  • env.list
  • env.secrets.set
  • deploy.status
  • db.query
  • db.migrate
  • db.snapshot
  • db.restore
  • db.migrations
  • db.connection
  • cron.add
  • cron.run
  • cron.runs
  • domains.connect
  • logs.query
  • metrics.get
  • approval.status
  • approval.wait
  • policy.set

Pricing

Priced per project, capped by you.

Your agent can never spend past the cap you set. Beta pricing, subject to change.

Hobby
$0 / project
  • 1 project, preview + production
  • 500 MB Postgres, daily backup
  • 5 cron jobs
Pro
$19 / project / mo
  • Preview, staging and production
  • 10 GB Postgres, nightly snapshots kept 7 days
  • Custom domains, unlimited cron
Studio
$99 / mo
  • Up to 15 projects
  • Shared spend cap across agents
  • Audit log of every agent action

Paste one line into your agent.

Read https://plinth-cloud.fly.dev/_plinth/agent.md, then put this repo on Plinth: sign me up, push to staging, run the migrations and send me the link to approve production.