🦘
Live · Free to start · Open source

We never ask if
you're human.

The deployment platform built for agents — not walled against them. Free to start — one command, no account, no credit card, no CAPTCHA.

bash
$ npx openpouch deploy

Pick your case: built or static folder → npx openpouch deploy  ·  raw Vite / Next / Svelte source → npx openpouch deploy .  ·  full-stack Node + React → npx openpouch deploy . — openpouch installs, builds & runs it for you.

See how it works View the source

→ a live *.openpouch.sh URL in seconds — free, no signup. Anonymous previews last 72 h; claim extends yours to 7 days — or save it with a free account and it stays live as long as it's used.

The problem

Your agent can write the app. Then the cloud asks it to click a fire hydrant.

Right as agents start shipping real software, every platform they touch is slamming the door: CAPTCHAs, "verify you're human," bot-walls, OAuth flows that dead-end in a headless browser. openpouch is the opposite of that — every surface is built for agents, with zero human-verification anywhere.

🤖

For agents, end to end

The whole lifecycle — plan, preview, deploy, verify, logs, rollback — is a CLI with --json + exit codes and an MCP server. Same behavior either way. Drop it into Claude Code, Cursor, Codex, OpenClaw, Hermes, or your own harness.

🗣️

For the humans who run them

Every result carries a plain-language summary and a live link. The non-technical founder watching their agent work sees a sentence and a URL — never a build setting.

🔒

Safe by construction

Previews ship autonomously. Production needs a human approval — and the approval is TTY-gated, so an agent literally can't approve its own production deploy, in any harness. That's the line we don't move.

🦘

Our own agent-native infra

Not a wrapper over someone else's dashboard. Your deploy runs a real container on our boxes, behind our router, with our own isolation — agent-native from the metal up.

How it works

Empty folder to live URL in three steps.

Run one command

From any project directory: npx openpouch deploy. No account, no provider key, no manifest to write.

Get a live URL

A few seconds later, a real *.openpouch.sh URL. The agent gets JSON + an exit code; your human gets a link they can click.

Claim to keep it

Anonymous previews live 72 h. One click extends yours to 7 days — or save it with a free account and it stays live while it's used (it only expires after ~90 days without a single visit, warning mail first). Abuse is controlled by accounts, quotas, and egress filters — never by asking a machine to prove it's a person.

For the agent builder

JSON in, JSON out — no screen-scraping.

Every command speaks --json with stable exit codes, so your agent acts on structured data, never parsed text. The agent-safe full-stack deploy is npx openpouch deploy . --json --health-path /api/health --redact-secrets — machine-readable result, backend proven, claim token kept out of your report. A deploy returns:

deploy result · json
{
  "ok": true,
  "url": "https://my-app-x7k2ab.openpouch.sh",
  "authenticated": false,
  "ownership": "anonymous",
  "expiryPolicy": "fixed",
  "healthStatus": "healthy",
  "pending": false,
  "claimUrl": "https://openpouch.sh/claim/my-app-x7k2ab?token=…",
  "claimUrlIsPrivate": true,
  "summary": "Your app is now live — share the link to open it.",
  "nextCommands": {
    "verify": "npx -y openpouch verify --json",
    "logs": "npx -y openpouch logs --json",
    "inspect": "npx -y openpouch inspect --json"
  },
  "deployment": {
    "id": "my-app-x7k2ab",
    "url": "https://my-app-x7k2ab.openpouch.sh",
    "expiresAt": "2026-07-13T18:04:00.000Z",
    "status": "live",
    "kind": "static",
    "framework": null
  },
  "evidence": [
    "deploy.manifest.json", "deploy.policy.json",
    "deploy.evidence.json", "DEPLOYMENT.md"
  ]
}

url is the shareable result · healthStatus tells you deployed vs. actually reachable (so you never hand over a dead link) · deployment.expiresAt says exactly when the preview ends (rolling for account-owned apps: any visit resets the ~90-day clock) — claimUrl extends it from 72 h to 7 days or ties it to a free account, and it's flagged claimUrlIsPrivate so you don't relay the token · nextCommands are ready-to-run follow-ups · summary is plain-language for your human · the evidence files land in the repo, so a fresh agent resumes after context loss.

Pricing

One account, many apps, one predictable bill.

A flat bundle, not a per-service meter. Paid plans check out in your browser via our Merchant of Record (Paddle) — your agent hands you the link, you pay, the account upgrades itself.

$0 Start free — no credit card. The free tier includes 2 dynamic apps + 25 static previews — and account-owned apps stay live as long as they're used. Paid tiers add capacity, always-on apps, and persistent /data volumes when you outgrow it.
Starter
$15/mo

6 dynamic apps

For your first few apps

  • 60 static previews
  • 1 always-on app · 1 GB /data
  • API key + MCP
  • No usage bills
MOST POPULAR
Pro
$49/mo

15 dynamic apps

For agencies & power users

  • 200 static previews
  • 3 always-on apps · 5 GB /data
  • API key + MCP
  • Predictable, flat price
Scale
$109/mo

25 dynamic apps

For growing portfolios

  • 500 static previews
  • 8 always-on apps · 20 GB /data
  • Higher rate limits
  • No surprise overages
Business
$179/mo

40 dynamic apps

For high-volume teams

  • 1000 static previews
  • 15 always-on apps · 50 GB /data
  • Top rate limits
  • Priority support
Founder cohort · honored

Founder pricing is live — applied automatically.

Accounts created before general availability are the founder cohort: they check out at our launch prices, automatically — no code, no coupon. Ready when you are: ask your agent to upgrade, or run it yourself.

npx openpouch upgrade --plan pro

The free tier stays free — account-owned apps stay live while they're used. Payment happens in your browser at our Merchant of Record; agents never touch it. See the refund policy and what works today.

Need more than 40 apps or dedicated infra? Talk to us about Enterprise.

FAQ

"Can't I just deploy with GitHub?"

For a static site, sure — GitHub Pages serves static files from a repo. Two catches:

  • A dynamic app — a Node.js server, an API, a backend — can't run on GitHub at all. It gets built, then handed off to a separate host. Back to accounts and dashboards.
  • All of it assumes a human: a repo, an account, a dashboard, an OAuth login in a browser. An agent can't click through that.

openpouch is one command from any folder — no repo, no account, no dashboard, no OAuth, no CAPTCHA:

bash
$ npx openpouch deploy

→ a live URL in seconds. It serves your built static site (React, Vue, Svelte, plain HTML) and runs real Node.js apps in a container. The agent deploys what's in front of it; your human gets the link.

Honest status

What works today, what's on the way.

Everything under "available today" is live right now and works for real — from an agent or a terminal.

Available today

  • Anonymous one-command deploys — no account, no key
  • Static sites and real Node.js apps in a container — Express servers, JSON APIs, webhooks
  • Build-on-deploy — ship a Vite/Next/Express source folder, the server builds it
  • Agent-readable logs — install, build & runtime output via openpouch logs
  • Accounts, API keys + MCP, per-account quotas
  • Usage-based persistence — 72 h anonymous, 7 days claimed, account-owned apps stay live while they're used (~90-day inactivity window, warning mail first)
  • Environment variables & secrets for dynamic apps (--var / --env-file)
  • Governed lifecycle: preview autonomous, production human-approved
  • Self-service billing via Merchant of Record — paid tiers with always-on apps and persistent /data volumes (payment is human-only)

On the way

  • Custom domains
  • Managed databases
  • Dedicated infrastructure (Enterprise)

Every other cloud is busy proving you're not a bot.
We're busy preparing the world for agents.