Launchbase
Sign inGet started
internal alpha · Stripe test mode · free 7-day trial

Launch your app.
Skip the infrastructure.

One account for hosting, database, auth, email, payments and domains. Describe what you are building, approve the configuration and the budget, and your coding agent deploys to a live URL through the dashboard, the JSON API or a remote MCP.

Get startedConnect your agent
Tool and endpoint names are real; output abbreviated.
// any MCP client (Claude Code, Cursor, …) → https://launchbase.build/mcp
▸ validate_source   { projectId, files: { "package.json": …, "app/page.jsx": … }, options: { healthcheckPath: "/api/health" } }
✓ Next.js detected · build: npm run build · start: next start
▸ create_release    { projectId, sourceId: "8f2a1c…", requestId: "notes-v1", message: "Notes app v1" }
  queued → building → starting → health 200 → live
  https://notes-production.up.railway.app
▸ get_release_logs  { projectId, releaseId: "c0ffee…", kind: "build" }   // real provider logs, not a summary
# one credential, scoped to one project
curl -X POST https://launchbase.build/api/v1/projects/$PROJECT/releases \
  -H "Authorization: Bearer lb_agent_…" \
  -H "Content-Type: application/json" \
  -d '{"sourceId":"8f2a1c…","requestId":"notes-v1","message":"Notes app v1"}'
# → 202 { "data": { "number": 2, "status": "queued" } }
curl https://launchbase.build/api/v1/projects/$PROJECT/releases/$RELEASE/logs?kind=build \
  -H "Authorization: Bearer lb_agent_…"
# packages the directory (no .env, .git, node_modules), uploads privately, verifies the stack, creates a release
LAUNCHBASE_URL=https://launchbase.build LAUNCHBASE_TOKEN=lb_agent_… LAUNCHBASE_PROJECT=<project id> \
node src/cli/launchbase.mjs deploy ./my-app --health /api/health
✓ release 2 · building → starting → health 200 → live
# on failure the CLI prints the build and runtime logs

Free draft workspace. Paid resources are created only after you choose a plan.

Dedicated resources per project onRailwaySupabaseStripeResendCloudflare

How it works

Nothing is provisioned before you approve it.

Three steps, each with an explicit checkpoint. The dashboard, the API and the MCP show the same state, including failures.

  1. Describe or select

    Tell Launchbase what you are building or pick services yourself: hosting, database, auth, email, customer payments, an optional domain. Every component can be managed, connected to your own account, or turned off.

  2. Approve configuration and budget

    Review exactly what will be created and what it costs. Start the free 7-day trial or pick a plan; add a prepaid balance with a spending cap if you want usage beyond it. Nothing is provisioned before that.

  3. Your agent deploys

    A coding agent with scoped permissions uploads private source, deploys, reads the real build and runtime errors, fixes them and redeploys. You get a live URL and a status that tells the truth.

Review before creating

Exactly what will exist and what it costs. Nothing runs until you subscribe.

  • hostingmanagedRailway · eu-west
  • databasemanagedSupabase Micro · RLS on
  • authmanagedemail + password
  • emailyour Resend keyno markup
  • paymentsoffenable later
  • plan$29 / monthPAYG off · cap $0
What an agent sees
▸ tools/list
  list_projects · get_project · create_project · validate_source · create_release
  get_release_logs · restore_release · attach_domain · verify_domain · send_email
  get_payments · quote_domains · get_migration_plan · request_export · whoami …
▸ whoami
  { "kind": "agent", "scopes": ["project:read", "deploy:write", "logs:read"],
    "project": "notes", "budget": { "monthlyCapMinor": 2000 } }
▸ start_payments_connect { projectId: "…" }
  { "actionRequired": { "actor": "owner", "url": "https://connect.stripe.com/…" } }
// payments, purchases and provider keys always come back as an action for the owner

Developer and agent experience

Connect your agent this afternoon.

One credential or an OAuth grant. Every MCP tool has a JSON API twin with the same authorization, so humans and agents see the same project.

  • Scoped credentials, optionally bound to a single project, rotated or revoked at any time
  • Remote MCP over Streamable HTTP with OAuth 2.1, PKCE and a consent page you approve
  • Agent-first drafts: the agent starts, you claim the project, it receives a credential once
  • Preauthorized invites with scopes, a project binding and a spend limit
  • Payments, purchases and provider keys always return an action for the owner

What is included

Managed services you can swap for your own accounts.

Each project gets dedicated resources under our provider accounts. Any component can be connected to your own account instead, one at a time, without disturbing the others.

tested

Hosting

Static, React/Vite, Next.js, Node, Python or a Dockerfile. Exact provider deployment ids, health-checked live status.

tested

Database & auth

A dedicated Postgres database with row-level security and email/password auth for your users.

tested

Releases & logs

Idempotent releases, one in flight per service, real build and runtime logs, restore any previous release.

tested

Transactional email

Send from your own Resend account today; delivery, bounces and suppressions are tracked. A managed sending domain is pending.

test mode

Customer payments

Your own Stripe key today; Stripe Connect onboarding is built and awaits platform enablement. Verification is shown, never hidden.

tested

Domains

Bring your own domain: ownership check, exact DNS records, automatic TLS, auth redirects re-wired. Buying through Launchbase is not available yet.

tested

Exports & migration

Source snapshots, a portable database dump with checksums, auth users and step-by-step guides for leaving.

tested

Budgets & ledger

Plan, prepaid balance and caps in cents. Reservations before spend, settlements after; nothing unbounded.

later

AI (optional, later)

OpenRouter and fal.ai through project-scoped keys at provider cost plus 5%. Never bundled into a plan.

Dashboard

Everything in one place. Nothing hidden.

Deployments, domains, budgets and the audit trail show provider truth: failures with their logs, pending steps with what you must do next.

Deployments

Each release is tracked to the exact provider deployment and goes live only after a real health check.

  • #3Notes app v1.1live2 min ago
  • #2Notes app v1.1failedbuild: Module not found ./lib/db
  • #1Notes app v1supersededrestore

Domains

Ownership first, then records, then TLS.

  • TXT_launchbase-verifyverified
  • CNAMEapppropagated
  • TLScertificateissued

Budget

Reserved before spend, settled after.

Plan$29.00 / month
Usage this month$3.20 of $20.00 cap

Audit trail

Every action names its actor: you, a member, or an agent credential.

  • release.create · agent notes-bot · requestId notes-v1
  • domain.verified · owner · app.example.com
  • payments.connect_created · action required · owner completes Stripe onboarding
  • export.downloaded · owner · 1 part · 10-minute link

Your keys, your data, your exit

Leave whenever you want. With everything.

Mix managed components with your own provider accounts. Source stays private. When you go, you take the source, the database, the users and a migration plan written for agents.

  • Per-component BYOK: your Resend key, your Stripe key, your domain
  • Portable database export with per-table checksums and a verified restore script
  • Byte-identical source snapshots and the deploy manifest
  • Migration steps with checks, rollback and dual-running costs
  • Managed resources are retired only after you confirm
What leaving looks like
export-8f2a1c.tar.gz
├─ manifest.json            sha256 of every file
├─ inventory.json           resources, regions, URLs, releases
├─ migration-plan.json      ordered steps · checks · rollback
├─ GUIDE.md
├─ source/release-0003-….tar.gz     byte-identical to your upload
└─ database/
   ├─ schema.pre.sql · schema.post.sql
   ├─ data/public.posts.ndjson       counts + order-independent checksums
   └─ auth/users.ndjson              password hashes move with you
$ node scripts/restore-export.mjs --export ./export --database-url $DESTINATION
✓ 4 tables · checksums match

Pricing

Start free. Grow when you need to.

A 7-day free trial that pauses instead of billing you, three paid tiers with growing capacity, and bring-your-own accounts on any of them. Allowances are provisional until measured on real workloads.

Free trial

$0 · 7 days
  • 7 days, then everything pauses
  • Deploy with hosting, database and auth
  • 100 emails in total
  • No custom domains
  • Data kept 30 days after the pause; pick a plan to resume
Start free trial

Launch · per project

$29 / month
  • 1 production environment on managed hosting
  • Micro Postgres database (shared vCPU, 1 GB RAM) with auth
  • Hosting allowance $5.00/month at provider cost (provisional)
  • 1,000 emails / month (provisional)
  • Dashboard, JSON API, remote MCP, scoped agent credentials

Usage beyond the allowance: provider cost + 20%, off by default, always capped by you.

Start with Launch

Grow · per project

$79 / month
  • 1 production environment on managed hosting
  • Small Postgres database (2 GB RAM) with auth
  • Hosting allowance $20.00/month at provider cost (provisional)
  • 10,000 emails / month (provisional)
  • Custom domains, exports, everything in Launch

Usage beyond the allowance: provider cost + 20%, off by default, always capped by you.

Start with Grow

Scale · per project

$199 / month
  • 1 production environment on managed hosting
  • Medium Postgres database (4 GB RAM) with auth
  • Hosting allowance $60.00/month at provider cost (provisional)
  • 50,000 emails / month (provisional)
  • Everything in Grow with the largest included usage

Usage beyond the allowance: provider cost + 20%, off by default, always capped by you.

Start with Scale

BYOK

Bring your own accounts, on any plan.

Connect your own Resend, Stripe and domain today; the plan price stays the same and Launchbase adds no markup on providers you pay directly. Your own hosting and database accounts are next.

  • Your Resend key: unlimited sending at your Resend price, no Launchbase markup
  • Your Stripe account or Connect onboarding: you are the merchant of record
  • Your domain: ownership check, DNS records, TLS
  • Switching a component later is a staged migration, never a surprise

Questions

Straight answers.

Is there a free trial?

Yes: 7 days with hosting, database and auth, up to 100 emails, no custom domains. When it ends everything pauses and your data is kept for 30 days; pick a plan to resume exactly where you left off.

Can I use my own provider keys?

Yes, per component. A managed database with your own email provider is fine. Switching later is a staged migration, not a key swap.

Do I need GitHub?

No. Agents and the CLI upload private source directly. A private GitHub connection is optional.

What apps are supported?

Web services and APIs on the listed stacks. Workers, WebSockets, volumes and special hardware need explicit validation before we advertise them.

Can I add a domain later?

Yes. Attach a domain any time; the existing app is re-wired rather than duplicated and the generated URL keeps working.

What happens if my budget runs out?

New paid work is blocked or the exhausted service is limited. Data is never deleted automatically.

Do I need Stripe verification to charge my customers?

Yes. Stripe requires business verification for connected accounts; we show the exact steps and never claim it can be skipped.

How do I leave?

Request an export: source, database, users, configuration and migration guides. Managed resources are retired only after you confirm.

Get started

Launch your app today.

Free draft workspace. Paid resources are created only after you choose a plan.

Get startedRead the agent guide