Deploy and manage every app on any VPS, with AI you control.
An AI can write your app. DeployOS gets it live. Paste a server IP, click deploy, and get a working HTTPS site in minutes, with no DevOps hire, no command line and no monthly hosting bill.
Email alerts when a server or container stops answering, sent through your own mail provider.
Problem 4 of 4Developers wary of AI
An AI agent near production feels reckless.
What goes wrong
Most agent tools get a broad key and no limits.
You learn what it changed after the fact.
One bad prompt can delete data or take a site down.
There is rarely a quick way to stop it once it starts.
Whatever it does is logged, if at all, on someone else’s server.
How DeployOS clears it
Fixed
Every write is its own switch, off by default. Reading logs, metrics and app status is always available. Deploying, restarting, scaling, database writes and cron are each a separate toggle you turn on one at a time.
Destructive actions need your click. Tearing down an app, scaling to zero, restarting an app tagged critical and removing a cron job open a confirmation dialog. No answer in two minutes counts as no.
A local log of every change. Tool, target, arguments, result and duration for each write, filterable and exportable as CSV. It stays on your computer and is never sent anywhere.
One switch pauses all AI access. If an assistant misbehaves, pause every write at once, then resume when you are ready. Your servers keep running either way.
Secrets stay unread. Your assistant sees the names of your environment variables, never their values, and template passwords are stripped before anything is handed over.
It runs on your machine, not ours. The MCP server is a local program talking to your servers over SSH. There is no DeployOS cloud in the middle holding your keys.
One switch per write action, all off by default. Tools that only read are always available.
Unscripted: Claude Code operating a live DeployOS account through its MCP connection.
Find the holes before someone else does.
A new server is probed by bots within hours. DeployOS can attack your own apps first, in a way that only reads and never breaks anything, and hand you a report with the fix for each problem it finds.
Find it.
After you deploy, DeployOS tests your server and your apps’ own domains the way a stranger would. Can anyone download your .env, your .git folder or a database dump? Is a database or Docker port open to the internet? Is HTTPS forced? Does your API trust any website? It also looks for what is about to break: a disk filling up, a certificate about to expire, containers that will not restart after a crash, and databases with no backup.
Fix it.
Every finding says how an attacker would use it and what it can break, then gives the fix written for your setup, for Caddy or Traefik. DeployOS checks the fix before you use it: nothing destructive, no firewall change that could lock you out of SSH, and a dry run on your own server. You apply it, press retest, and see it pass.
Keep it fixed.
Add a finding to your deploy checks and the same mistake is caught next time: a warning, or a stopped deploy if you choose, before a secret file or an open database port reaches your server. Or switch on the automatic run and a fresh report is waiting after every deploy.
Exposed files1
Open ports1
HTTPS and certificatesOK
Security headers3
What could break2
critical/.env is publicly readableexample.com/.env
What we saw
https://example.com/.env answered 200 and the content looks like an environment file. The content is not shown or stored.
How an attacker uses it
Downloads it with a browser, reads the database and API credentials inside, then logs in as you.
The fix
Remove the file from what is served, add it to .dockerignore, then rotate every secret that was inside it.
Checked on your server: safe to apply
Nothing destructive or lock out prone
The proxy accepts this configuration (dry run)
The fix can be proven with a retest
Check this fixI applied it, retestAdd to deploy checks
An example report. The findings shown are illustrative and are not from a real server.
A deep server audit.
SSH settings, firewall, exposed ports, Docker risks, accounts and sudo, authorised keys, file permissions and kernel hardening. Read only, and a check that could not run is shown as unknown, never as passed.
A safer admin account.
Create a sudo user and give it your SSH key in one step, so you can turn off root login without locking yourself out. Errors say what went wrong and how to recover.
Your AI can dig deeper.
Ask your assistant to investigate one finding further. It confirms the problem and finds where to fix it. It sees the names of your secrets, never their values.
It is a strong first pass, not a full penetration test. It cannot see inside your app’s own logic or behind a login, so it complements a human review and does not replace one.
Templates, monitoring, a terminal, scheduled jobs and secrets live in the same window. These are real screens from a real server.
220+ apps, one click each
WordPress, n8n, Ghost, Grafana, Ollama and hundreds more, plus ready made stacks. Tell it which paid tool you want to replace and it shows the self hosted alternative.
220+ templates
Multi app stacks
Replace a paid tool
1 / 5
Works for any server, from any vendor
DeployOS talks to your server over plain SSH. If you can SSH into it, DeployOS can run it. Switch vendors any time, because nothing about your setup is tied to us.
Tools you host yourself, like Coolify and Dokploy, are free and genuinely good. But they run an always on dashboard on your server with root access to Docker, open to the internet. DeployOS runs nothing there except your apps and the small web server that routes traffic to them.
0 agents on serverNo dashboard portOS keychain onlySSH only
What people say after using it
“It took me less than 60 seconds to deploy my vibe-coded app with DeployOS — no Dockerfile, no server config, just a live, health-checked HTTPS URL. That app has since generated over $7,000+ in revenue.”
Ugochukwu Onwuchekwa
DeployOS user
“It took me less than 60 seconds to deploy my vibe-coded app with DeployOS — no Dockerfile, no server config, just a live, health-checked HTTPS URL. That app has since generated over $7,000+ in revenue.”
Ugochukwu Onwuchekwa
DeployOS user
Everyone else rents you software. Buy this one once.
DeployOS turns any $5 VPS into your own VPS Manager — push from GitHub, automatic HTTPS, databases, backups, 220+ one-click apps, no per-site cap. Runs on macOS and Windows, connects to any server over SSH with zero agents installed. What costs $19–39/month on managed platforms or per-site on shared hosting costs you a single payment. You pay once and own it forever — no subscription, a year of updates included, license emailed instantly.
For agencies reselling hosting to their own clients.
Everything in Pro
Client Hosting Mode - unlimited clients
White-label Client Portal - no DeployOS branding
Lower managed-billing commission when it ships
Priority support
Coming Soon — Help Shape DeployOS Agency
Run your own hosting business, manage client servers, offer branded hosting dashboards, and build recurring revenue. Vote for the features you want most and get early access.
14-day money-back guarantee, no questions asked. One license covers macOS and Windows. Licenses keep working after the 12-month update window ends — renew at 50% to keep receiving new versions.
Compare plans
Free
Solo
Pro
Agency
Price (one-time)
$0
$79
$149
$499
Availability
Available now
Available now
Available now
Coming soon
Servers
1
Unlimited
Unlimited
Unlimited
Templates
5 starter
All 220+
All 220+
All 220+
Stacks (curated combos)
✓
✓
✓
Move apps between servers
✓
✓
Device licenses
1
1
3
3
Client Hosting Mode
Up to 3 clients
Unlimited clients
White-label Client Portal
✓
Updates included
1 year
1 year
1 year
Support
Community
Email
Priority
Priority
Everything people ask before buying
Do I need to know Docker or Linux?
No. You paste your server's IP address and SSH key once, DeployOS installs Docker, configures the firewall and HTTPS routing, and from then on you deploy from a visual app. There's a Simple mode that hides the infrastructure entirely, and an Advanced mode with every dial when you want it.
How is this different from shared hosting (cPanel, GoDaddy, Bluehost)?
Shared hosting rents you a slice of someone else's server and caps what you can run, usually one site, PHP only, hard CPU and RAM limits. A VPS is a full server that's entirely yours, but managing one yourself usually means learning Docker, Nginx and Linux first. DeployOS is that missing piece: it turns a bare $5 VPS into something as easy to run as a hosting panel, except there's no per site cap, host as many apps, databases and background jobs as the hardware can hold, for one price instead of one bill per site.
Why not just use Ansible, Terraform or NixOS instead?
If you're already comfortable maintaining playbooks or Nix configs across a fleet of servers, those tools are genuinely great and DeployOS isn't trying to replace them, they're built for infrastructure as code at scale. DeployOS is for the much more common case: deploying a handful of apps without writing or maintaining a playbook for each one. It's push button where Ansible is code first, less powerful for managing a large fleet, much faster for a side project, a client site, or a small business's handful of apps.
Why pay anything when Coolify, Dokploy or CapRover are free?
Because they're genuinely good and you should seriously consider one. Coolify is free and open source, and its community is bigger than ours by a lot, more contributors, more Discord, more answers when something breaks at 2am. If free and open source is the deciding factor for you, use it; we mean that without qualification. The difference is architectural, and it comes down to one question: what runs on your server permanently? Those tools answer 'a web dashboard with root level Docker access, listening on a port.' DeployOS answers 'nothing.' No agent, no daemon, no dashboard, no listening port, the control plane is the desktop app on your own machine, and it connects over SSH on demand. That's why the security tradeoff they ask you to accept is one DeployOS doesn't ask you to accept: there is nothing on your server between deploys for a vulnerability to live in, and nothing reachable from the internet holding your infrastructure credentials. That isn't a claim DeployOS makes about itself being safer than mature open source, it's a smaller amount of machinery, which is easy to reason about and easy to verify. It's also a real tradeoff running the other way: those tools get real inbound webhooks from GitHub because they have an always on process to receive one. DeployOS polls, so auto deploy has extra latency and only runs while the app is open. And being smaller is a genuine cost: DeployOS is one founder, not a community. If a large maintainer pool matters to you for critical infrastructure, that's a legitimate reason to pick the free option. See /vs/coolify for the full honest comparison.
Isn't it reckless to let an AI agent manage production infrastructure?
It's a real concern, and we'd rather you ask it than assume we handled it. That's exactly why the free plan ships a read only MCP server, and why every paid plan gates the dangerous tools behind settings that are off by default. Every write action, deploy, restart, scale, teardown, database writes, cron, is its own toggle. Teardown, scaling to zero, restarting a critical tagged app, and removing a cron job all require a human confirmation dialog before they execute, with a two minute timeout that defaults to 'no.' Every write call is logged locally, tool, target, arguments, result, duration, filterable and exportable, and never transmitted anywhere. The read only tools are always available and never return secret values, template passwords and env values are stripped before anything is handed to the assistant. One global switch pauses all AI access instantly, regardless of individual settings. We think that's the right standard for anything touching production. If you disagree, the safe default is to leave it paused and deploy from the GUI, which is a fully supported way to use the product.
Is it safe to run the security attack simulation on a live site?
Yes, it is built to be. It only reads and connects: about 25 plain page requests per domain, an OPTIONS request, a CORS check with a made up website and TCP connections to well known database ports. It never logs in, never sends a payload, never puts load on the site and only tests your own server and the domains of apps you deployed with DeployOS. It does not store the contents of any file it finds, only that the file is there and what kind of thing it is. It never applies a fix for you. It is a strong first pass, not a full penetration test, because it cannot see inside your app's own logic or behind a login. Nothing runs on your server for it: the checks run from your computer, plus read only commands over SSH.
I don't have a server. Where do I get one?
Any VPS provider works: Hetzner (from ~€4/mo), DigitalOcean, Vultr, Contabo, Linode, OVH, AWS, Hostinger, if you can SSH into it, DeployOS can run it. Create the cheapest Ubuntu server they offer, paste its IP into DeployOS, and it handles the rest.
Is it really pay once? What's the catch?
Really. Your license works forever, and includes a year of app updates. After that year the app keeps working exactly as it is, you only renew (at 50% off) if you want to keep receiving new versions. There is no subscription and nothing hosted by us to pay for.
What happens when a deploy breaks?
DeployOS is built for exactly that moment: it detects the app isn't answering, hunts for the right port automatically, surfaces the app's own crash logs in the deploy output, and the Doctor pinpoints DNS/proxy/network issues in one click. The last three builds stay cached on your server for instant rollback.
Where do my secrets and SSH keys live?
In your operating system's keychain, on your machine. DeployOS has no backend, your credentials are never uploaded anywhere, because there is nowhere to upload them to. The app talks straight to your server over SSH.
How do I know the free alternatives aren't the smarter bet here?
In a lot of cases they are. Self hosted PaaS tools like Coolify are free, open source, and maintained by a community, that is a real, structural advantage over a product maintained by one person, and anyone claiming otherwise is selling you something. What DeployOS offers is a different bet on how much should run on the server itself: the free tools need an always on dashboard to work, DeployOS needs nothing. Fewer moving parts to patch, no exposed management port, no third party service holding root level access to your infrastructure, and your credentials never leave your machine. You also get a licensed product with a 14 day money back guarantee and someone accountable when it breaks, instead of a project whose maintainers can change direction. Free and community backed is the better choice if you want the code and the maintainers. DeployOS is the better choice if you want the smallest possible footprint on the server and a clear security boundary between your apps and the thing managing them. Both are legitimate. Read /vs/coolify before deciding, it's written by us and spends most of its length on where the alternatives win.
Will it interfere with things already running on my server?
No. DeployOS scans what's already there and adopts it non destructively, existing containers keep running and get imported into the dashboard. If another proxy already owns port 443, DeployOS steps back and tells you instead of clobbering it.
Which platforms does the desktop app run on?
macOS (Apple Silicon and Intel, one universal build) and Windows 10/11 (64 bit), both downloadable today, and one license covers either. Linux is next on the roadmap; join the newsletter below to hear the moment it ships.
Windows warned me about an "unknown publisher", is the download safe?
Yes, that warning appears because our Windows installer isn't yet signed by a public certificate authority (the macOS build is fully notarized by Apple; the Windows CA certificate is in progress). The installer is built from the same code, served only over HTTPS from this site, and we publish its SHA-256 checksum on the download page so you can verify the file yourself. Click "More info → Run anyway" to proceed.
What happens to my apps if my server dies?
You restore them. Database backups and full server snapshots can be pushed offsite to S3 compatible storage (AWS, Backblaze B2, Wasabi, Cloudflare R2 or MinIO), and a snapshot restores onto a brand new, already bootstrapped server: every app comes back up, routes republish and the backup schedule reinstalls itself. A Verify action restores a backup into a throwaway database and reads it back, so you know it works before the day you need it. Restoring onto a different server is a Pro feature; restoring in place is included from Solo.
Can my team use it, or do we have to share one password?
Each person gets their own revocable login. Team access creates a tightly restricted account per member on one of your servers (no shell, no sudo), so removing one person deletes only their access and nobody else is affected. A teammate installing DeployOS joins with just the server's address and their own username and password, no SSH key to pass around.
What if it's not for me?
Every paid plan has a 14 day money back guarantee, no questions asked. And the Free plan is a real license, one server, real deploys, so you can prove it works on your VPS before paying anything.
Something else on your mind? Email us and a human answers.
Run your own servers, pay once
Download DeployOS, paste a server IP, and get your first app live over HTTPS. The free plan needs no card.
Download DeployOS freeFree plan, no card needed. Paid plans have a 14 day money back guarantee.