lavela

lavela — launch and operate the app you built, from one conversation (MCP-first).

This page is for both humans and AI agents (Claude Code, Cursor, or any MCP client) landing here from a blog post, a shared link, or a search — it's the same data the lavela.capabilities MCP tool returns, so what you read here matches what a connected agent sees.

Connect

npx @lavela/cli connect

Run that in any repo — a browser opens to console.lavela.dev, you sign in and click "Authorize & connect," and the CLI writes the connection into your Claude Code config (no token to copy-paste). Reconnect an already-open session with /mcp. Once connected, every tool below is callable as mcp__lavela__*.

No separate dashboard-then-docs detour: the point of lavela is that an AI agent already in your coding session can provision infrastructure, accept payments, and run ad campaigns through the same kind of tool call it already makes for everything else.

Suggested order

  1. analyze_stack — see what the repo is
  2. launch_saas — create the project + decide the stack
  3. provision_hosting — deploy a SIMPLE WEB FRONTEND (Next/Vite/static) to a live URL
  4. provision_compute — OR run ANY container (Java/Go/Python/backend/multi-service) when it is not a simple web frontend — you build+push the image, lavela runs it (billed monthly)
  5. provision_database / provision_cache / provision_storage — managed Postgres / Redis / object-storage, wired into the service (NOT currently usage-billed — quota-bounded only)
  6. set_compute_secret — inject API keys + secrets (write-only, encrypted), then run_compute_job for DB migrations (e.g. alembic upgrade head)
  7. compute_wire — connect multi-service stacks (api ↔ worker ↔ db) on a private network; get_logs / get_errors to debug
  8. security_scan — check the repo for dependency vulnerabilities + committed secrets right after the first deploy (poll security_scan_status)
  9. compliance_generate — privacy policy + terms
  10. connect_stripe — start accepting payments (KYC 1-5d)
  11. create_checkout — charge customers (settles to you in full, no lavela fee)
  12. provision_domain — connect a custom domain you already own (free — no purchase, DNS only)
  13. provision_email — inbox-safe sending on the domain
  14. ads_draft — acquire customers across platforms (you write the copy)

Not a fixed pipeline — skip what you don't need, and every tool result carries a next_step suggesting what to call next.

What you can do

Discover

Launch

Compute

Data

Provision

Operate

Grow

Pricing

Your OWN sales settle to you IN FULL via Stripe Connect — lavela takes 0% of your revenue and is not the merchant of your sales. There is no subscription and no per-charge fee. lavela makes its money on the infrastructure it runs for you: compute (containers, disk — provision_compute / provision_compute_from_repo / run_compute_job / schedule_create) is billed monthly for what you run (real money from day 1; idle ≈ $0), plus a ~10% commission on any ad spend lavela manages for you. provision_hosting (a simple static/Next/Vite frontend on Vercel) is a SEPARATE, free lane — don't conflate it with billed compute. Managed Postgres/Redis are provisioned but NOT currently usage-billed (a resource-count quota bounds them, not a dollar meter) — don't promise the user these carry a fixed price. Managed object storage (provision_storage) is ALSO disabled by default on most deployments (shared-key risk) — check that tool's own description before recommending it.

Good to know

Learn more

Questions? Contact us at the email in this document. · Terms · Privacy