Launchmatic: a Render alternative for AI-built apps
Render is a solid Heroku successor: managed containers, background workers, cron jobs, managed Postgres, and infrastructure-as-code via render.yaml. For teams that want a traditional PaaS with predictable per-service pricing, it's a credible default.
When to stay on Render
Stay on Render if you rely on its breadth of primitives — private services, cron jobs, static sites, and blueprints (render.yaml) in one platform — or if your team already encodes infrastructure in blueprints and the workflow works. Render's paid tiers are priced sanely; the friction is concentrated in the free tier and the deploy loop, not the platform's ceiling.
When to switch to Launchmatic
- Render's free Postgres has an expiry date — a countdown doesn't work for a side project you want to keep alive. Launchmatic's free 1 GB Postgres never expires.
- You want the cheapest always-on option: Launchmatic's $9 Hobby tier keeps one site awake, below the cost of Render's cheapest always-on service plus database.
- Your deploys feel slow and you want the runtime auto-detected instead of configuring build and start commands per service.
- You want agent-driven operations — Launchmatic's MCP server lets Claude Code or Cursor deploy and read logs directly.
Render vs Launchmatic
| Render | Launchmatic | |
|---|---|---|
| Free tier behavior | Web services spin down when idle; cold start on next hit | Free service sleeps after 30 min idle too — but wakes automatically, and $9/mo makes it always-on |
| Free database | Free Postgres expires after a fixed period | Managed Postgres on the free tier, no expiry |
| Build configuration | Manual build & start commands per service (or render.yaml) | Nixpacks auto-detects 30+ runtimes — usually zero config |
| Pricing model | Flat per service (plus per-user on team plans) | Flat per service; free tier forever |
| Background workers & cron | First-class service types | Supported — any process a container can run |
| AI agent integration | None | Remote MCP server — deploys as tool calls |
| Infra-as-code | render.yaml blueprints | CLI-driven (lm init writes service config to the repo) |
Pricing, honestly
Render and Launchmatic share the same per-service pricing philosophy, so the comparison is honest: both free tiers sleep on idle. The differences are at the edges — Launchmatic's free Postgres never expires where Render's has a countdown, and the $9 Hobby tier is the cheaper path to an always-on service with a database attached.
Migrating from Render
- 1Install the CLI:
npm i -g @launchmatic/cli && lm login. - 2From the repo root:
lm init. Delete nothing — render.yaml is ignored and your build/start commands are inferred by Nixpacks. - 3If Nixpacks guesses wrong (rare), pin commands with
lm deploy --build-cmd "..." --start-cmd "..."instead of recreating a blueprint. - 4Re-set env vars:
lm env set KEY=valuefor each var in your Render dashboard. - 5Migrate Postgres with
pg_dump/psqlinto the database fromlm db create app-db --service <serviceId>. - 6Deploy with
lm deploy, verify, then repoint your custom domain — SSL issues automatically.
FAQ
Does Launchmatic have an equivalent of render.yaml?+
Service configuration lives in the repo after `lm init`, so deploys are reproducible. There's no multi-resource blueprint format yet — for a typical vibe coded app (one service plus a database) you won't miss it; for complex private-network topologies, Render's blueprints are still ahead.
Will my app cold-start on Launchmatic's free tier?+
Yes — like Render's, the free tier sleeps after 30 minutes of inactivity and wakes automatically on the next request. The difference is the upgrade path: $9/mo (Hobby) keeps one site always-on, and the free Postgres never expires either way.
Can I bring my Render cron jobs and workers?+
Yes — workers deploy as ordinary services (any long-running process works), and scheduled jobs can run as lightweight services or in-app schedulers.
Try the migration
Free to start, no credit card — deploy next to your Render setup and compare before you switch anything over.