Deploy a Aider app to production
Aider is the open-source AI pair programmer for your terminal — it edits your repo and makes a git commit for every change. That commit-per-change discipline is a perfect match for git-driven deploys: connect the repo to Launchmatic and every Aider session ends with your changes live.
Why Launchmatic for Aider
Aider users pick their own models and run everything locally — the antithesis of platform lock-in. Launchmatic keeps that spirit: standard containers built from your repo, no proprietary config, and a CLI (`lm deploy`) that fits the same terminal workflow. Aider commits, you push, it's deployed.
Deploy in 5 steps
- 1Run Aider in your repo:
aider(it commits every change it makes). - 2Push the commits:
git push(create the repo first withgh repo create --private --pushif needed). - 3Install the Launchmatic CLI:
npm i -g @launchmatic/cli. - 4Authenticate:
lm login. - 5Bind the repo:
lm initand accept the Nixpacks-detected build/start commands. - 6Deploy:
lm deploy— then enable the GitHub integration so every futuregit pushafter an Aider session auto-deploys.
Add to `.aider.conf.yml` so /run can ship without leaving the session:
# Aider conventions for this repo
auto-commits: true
# In-session deploy: /run lm deploy
# Tail production logs: /run lm logs --service web --followFAQ
Aider commits after every change — won't that spam deploys?+
Deploys trigger on push, not commit. Aider's commits stay local until you `git push`, so a session becomes one deploy. If you want per-commit deploys anyway, push as you go — builds are incremental and preview branches keep production untouched.
Ready to deploy?
Free to start. No credit card. Auto-SSL on custom domains, managed Postgres, and per-branch preview deploys included.
This guide is part of our complete vibe coding hosting guide — how to take any AI-built app to production.