New — April 2026
Claude Code, Cursor, Codex — anything that speaks MCP — connects to Launchmatic over OAuth. No API keys to copy, no tokens on disk, revocable per-app from the dashboard.
OAuth handshake in your browser, you pick the scopes, the connection is bound to your team. 11 concrete tools plus a meta-agent for fuzzy multi-step requests.
claude mcp add launchmatic --transport http https://mcp.launchmatic.ioSetup docs
The same agent and tools, but in your terminal. Interactive REPL, one-shot mode, JSON output, resume threads across sessions. Streams over SSE.
$ lm agent > why did my last deploy fail? agent: Pulling the latest deployment for api...All CLI commands
The platform
A real-time dashboard for every project, deployment, database, and metric — all in one place.
Systems online
Push to your branch and we build, test, and deploy. Automatic framework detection. Zero config.
Scale your services from 1 to 10 replicas with a single click. Configure replicas per service to match your traffic.
Postgres, Redis, and MongoDB — provisioned in seconds with persistent storage.
Bring your own domain with automatic certificates. SSL is always on, always free.
Per-service Insights tab: live logs, CPU and memory, pod restart timeline, cluster events with OOM and crash reasons, deploy + audit history — auto-refreshing. Click Explain on a red metric and the agent reads the logs for you.
Invite your team, manage permissions, and share environments across your organization.
Launch sequence
Link your GitHub repo. We detect your framework, runtime, and build settings automatically.
Push to any branch. Auto-deploy triggers on every push to your configured branch.
We build your app with smart caching, parallel steps, and zero-config optimizations.
Your app is live with automatic HTTPS, real-time logs, and resource monitoring — all instant.
Runtime support
First-class support for every major runtime. Or bring a Dockerfile — we'll run that too.
Node.js
Python
Go
Rust
Ruby
Docker
Bun
Deno
The difference
We built Launchmatic because deploying software shouldn't require a PhD in Kubernetes. Your code is ready. Your infrastructure should be too.
# The old way
$ vim Dockerfile
$ docker build -t my-app .
$ aws ecr create-repository ...
$ docker tag my-app:latest 123456.dkr.ecr...
$ docker push 123456.dkr.ecr...
$ vim deployment.yaml
$ vim service.yaml
$ vim ingress.yaml
$ kubectl apply -f deployment.yaml
$ kubectl apply -f service.yaml
$ kubectl apply -f ingress.yaml
$ kubectl get pods # pray
... 35 more commands ...
→ 2–3 days. Maybe a weekend.
# The Launchmatic way
$ git push
✓ Live at my-app.launchmatic.io
→ 30 seconds. No YAML harmed.