You’re paying for the engineer.
One app, on a real URL, with me watching. It sleeps when nobody visits and wakes when someone does.
For an app people rely on. Always on, on your own domain, with incidents handled while you sleep.
Dedicated infrastructure and a team around the work. Pre-approve categories of action with budgets.
Launch pricing — subject to change.
An action is one completed piece of work: an investigation with a conclusion, or a change with evidence. “Renewed your certificate” is one action. “Investigated Tuesday’s slowdown and found the query that caused it” is one action.
We never meter tokens, requests, or anything else you’d need a dashboard to understand. Your plan includes a monthly allowance of actions; if you run out, I pause new work and tell you — nothing you run breaks.
After about fifteen minutes without visitors, your app pauses. The next visitor wakes it — the first request takes a few seconds, everything after that is normal. Nothing is lost while it sleeps. If people rely on your app, Launch keeps it always on.
No. The free tier needs nothing but your GitHub login. A card is only asked for when you upgrade to a paid plan.
Delete data, spend beyond a budget you set, or change anything about your domain. Those always wait for a human. Everything else follows the leash you choose: ask-first by default, or pre-approved categories with budgets. And the global pause button always works.
Yes, at any time. Your repo contains everything needed to run your app anywhere, because every change I make lands there as a commit or pull request. Cancel and nothing about your code stops working.
Paid plans include a managed database with automatic backups. Already have one — Supabase, for example? Keep it. I run your app, watch the connection, and leave your database exactly where it is.
No. I read your code to operate your app — to deploy it, watch it, and fix it. It is never used to train models, and never shared.