Skip to content
Projects / A93-03

Jetpump

Say "deploy" to your AI coding agent and get a live HTTPS URL back. No dashboards, no YAML.

jetpump.dev ↗
Part no.
A93-03
Status
beta
Platform
MCP · Google Cloud
Year
2026
Stack
TypeScriptNodeMCP SDKCloud RunCloud BuildFirebaseTerraformStripe
1Word to deploy
$0Idle cost: every part scales to zero
5Custom least-privilege IAM roles
116Commits to production beta
01 — The problem

AI agents can write a whole app in minutes, then hand you a list of hosting chores. Deploying is where vibe-coded projects stall.

02 — The case for it

Deployment as a tool call. A solo-run SaaS only pays off if it costs nothing when nobody is using it, so the design rule was simple: every part scales to zero. Free tier with a Stripe upgrade path, in two launch gates (free beta, then paid).

03 — Back of the napkin
Back of the napkinRough · not a forecast

Freemium. Free deploys to a jetpump.dev subdomain, with a paid tier (≈ €9/mo) for custom domains, databases and more builds.

  1. Sign-ups (assumption)1,000
  2. ×Free → paid5%
  3. =Paying users50
  4. ×Price€9/mo
  5. =Monthly recurring revenue€450
  6. −Build cost (≈ 2 min on Cloud Build)≈ $0.01/deploy
  7. =Gross margin≈ 90%
Running costs
Idle infrastructure
≈ €0 (scales to zero)
Fixed (domain, Firestore, monitoring)
≈ €30/mo
Hard daily cap on build spend
yes
At 10× / 100×

Costs follow usage because everything scales to zero, and the daily build-spend cap limits the worst case. At 100× the limits are Cloud Build concurrency quotas and abuse (people mining crypto in free builds), not the margin.

Verdict

The unit economics are fine. The risk is competition from Vercel, Netlify and Railway; the edge is being built for AI agents first.

04 — How it works
Diagram · From agent prompt to public URL
  1. 01Agent says deployLocal MCP server inside Claude Code, Cursor or Windsurf.
  2. 02Zip & uploadProject is packed and uploaded to GCS with a presigned URL.
  3. 03API + queueCloud Run API records the deploy in Firestore.
  4. 04Sandboxed buildCloud Build runs nested Docker with the metadata server blocked and images pinned by digest.
  5. 05ShipStatic sites go to Firebase Hosting, dynamic apps to their own Cloud Run service.
  6. 06Live URLhttps://<id>.jetpump.dev, with optional Neon Postgres.
05 — On screen
jetpump.dev: three steps from editor to live URL
jetpump.dev: three steps from editor to live URL
Landing page on mobile
Landing page on mobile
06 — Engineering highlights
01

Pentested

Five custom IAM roles, the metadata server blocked with iptables, images pinned by SHA-256 digest, IDOR fixes and idempotent Stripe webhooks.

02

A cap on runaway costs

After a cost-spike scare I added a hard daily cap on Cloud Build spend, so one bad loop can’t become a big bill.

03

Decisions written down

Architecture decision records, plus a CI check that fails if docs drift out of docs/.