Point DevOps Buddy at a Git repo, paste a docker-compose, or pick a ready-made app like WordPress or Nextcloud. It provisions the VM, wires DNS and HTTPS, and keeps your apps running — on infrastructure you own, at cloud-provider prices.
Start deploying — free Read the docs$ git push origin main buddy › cloning bitbucket.org/acme/store (private)… buddy › nixpacks detected php · composer install ✔python · pip install ✔node · npm install ✔ buddy › building image buddy-app-store ✔ buddy › DNS store.acme.com → 34.9.112.4 ✔ buddy › TLS via Let's Encrypt ✔ ✔ live at https://store.acme.com (58s)
Connect an API token and Buddy provisions VMs for you — or install the agent on any Linux server you already run.
From zero to a production URL in minutes — no Dockerfiles, no nginx configs, no SSH.
Add a provider API token and pick a region and size — Buddy creates the VM, installs Docker, Traefik and the agent. Or run one command on a server you already have.
Paste a Git URL — Bitbucket, GitHub or GitLab, private repos included with a read-only token (PHP, Node, Python, Go… built with Nixpacks, composer/npm included) — or a docker-compose file for anything else.
Pick a domain and subdomain. Buddy sets the DNS record, gets a TLS certificate and routes traffic. Deploy, restart, logs and metrics from the dashboard.
The features of a managed platform, without handing your infrastructure to someone else.
If it runs in Docker, it runs here. Multi-service compose apps, databases, workers — attached to one shared ingress network per VM.
Bitbucket, GitHub, GitLab or your own server — public or private. Buddy clones and builds on your VM with Nixpacks: composer install, npm build, pip install handled automatically. No Dockerfile needed.
Traefik + Let's Encrypt on every VM, Cloudflare DNS records managed for you. Your app is live at its domain in minutes.
App data is archived to a bucket in your own cloud project over pre-signed URLs — credentials never touch the VM. Restore any snapshot with one click.
CPU, memory and disk per server, plus per-app container metrics straight from the agent — refreshed every 20 seconds.
WordPress, Drupal, Joomla, Nextcloud and Magento — deployed with their database and HTTPS wired up, and installed for you. You land on a working site with an admin account, not a setup wizard.
Clone any app to a staging copy — same code, own subdomain — with one click. Test before you touch production.
Add one webhook and every git push to your branch ships. Signed by GitHub and GitLab, so only your repository can trigger it.
Scheduled commands and always-on background processes — a Laravel queue, a nightly export — run by systemd and restarted when they die.
Give each teammate their own key-only account instead of sharing root, and take it back without touching anyone else's.
Security headers on every response, PHP refused inside upload directories, and a 403 for the .env and .git that bots ask for within minutes. WordPress gets xmlrpc.php blocked and its login rate-limited. You do not switch any of it on.
Open only the ports you mean to — containers included — and let each VM install its own security patches.
TOTP 2FA with any authenticator app. Cloud credentials are encrypted at rest; agents authenticate with per-server tokens you can revoke.
The agent polls out over HTTPS — no SSH keys to share, no management ports open on your servers.
You pay your cloud provider directly for the VMs. Buddy never resells compute or locks your workloads in.
Start free. Upgrade when you need more servers — never pay a markup on infrastructure.
Free during the beta, until 17 September 2026. The paid plans open after that — leave your address and we'll tell you.
Nothing, unless you choose otherwise. The free plan stays free and keeps its limits — 1 server · 1 domain · 3 apps. The paid plans open after 17 September 2026; if you want one, leave your address on the plan above and we will write to you. Nobody is moved onto a paid plan or charged without asking.
A server is one machine running the Buddy agent — yours, on your cloud account or in your office. An app is one thing deployed onto it: a site, an API, a worker. A staging copy is an app of its own, because it has its own files and its own database. Delete either and the slot comes back the same day.
No. You pay your cloud provider directly, at their price, with no markup from us — a small VM is about $5–6 a month at Vultr or DigitalOcean. What Buddy charges for is the software that runs them.
Only through the API token or service-account key you add, encrypted at rest, and only for the operations you trigger (creating VMs, DNS records, backup buckets). You can revoke the token at your provider at any time.
Anything Nixpacks supports: PHP (composer), Node.js, Python, Go, Ruby, Rust, Java, .NET and more. If your project needs something custom, paste a docker-compose instead — that path supports literally anything that runs in Docker.
Your apps keep running. They live on your VMs behind Traefik; the control plane is only needed to make changes. That's the point of bring-your-own-cloud.
In an object-storage bucket inside your own cloud project (GCS today, S3-compatible targets on the roadmap). Transfers use short-lived pre-signed URLs, so storage credentials never reach the VM.
Yes, trivially. On a container server your apps are ordinary docker-compose projects in
/var/lib/buddy/apps/; on a classic server they are ordinary nginx sites under
/var/www/. Stop using Buddy and they keep working exactly as they are.