Turn the RAM you're not using into recurring revenue
Most VPS boxes run at a fraction of what you're paying for. DeployOS's Client Hosting Mode lets you carve the spare CPU, RAM and disk into priced packages, host your own clients on them, and bill monthly - all from the same desktop app you already deploy with, with no separate control panel, no cPanel licence, and no new subscription.
The math that makes this worth doing
You're already paying for the whole box. Most of it is probably idle most of the time - this is what that's worth once you start selling it.
A typical $20/mo VPS
8 GB RAM, 4 cores. Your own apps might use 2 GB and half a core, most of the time - the rest just sits there.
What's left over
6 GB RAM and 3.5 cores of capacity you already paid for and aren't billing anyone for.
What it's worth
Three clients on a $50/mo "1 app, 1 GB RAM" package is $150/mo from capacity that was otherwise doing nothing - against a server that costs you roughly $20/mo either way.
How it works
Packages, Clients and billing live on mydeployos.com so you can manage your hosting business from a browser. Only the desktop app ever touches the server - the same split DeployOS already uses for everything else.
1. Define Packages
Name, price, interval, and real limits: CPU cores, RAM, disk, app count, backup schedule. You set the numbers; DeployOS enforces them.
2. Add a client, assign a Package
Pick which of your servers they land on. DeployOS checks there's actually room - sold RAM across every client plus the new Package has to stay under 90% of what the server really has - before it lets the request through.
3. Real Docker limits, not a promise
`--cpus`, `--memory`, `--pids-limit` - actually applied to the container, not a number on a page. One client can't starve another, or you.
4. Collect payment however you already do
Your own Stripe Payment Link, PayPal.me, bank transfer, cash - DeployOS never processes a payment itself. Mark an invoice paid and the client's service restores automatically.
5. Non-payment suspends itself
A small opt-in container on the VPS polls your billing status and serves a branded "paused" page the moment a client goes overdue past your grace period - even if your laptop is closed.
Why not just use WHMCS + cPanel
That's the traditional way to resell hosting, and it still works - it's also two separate recurring subscriptions, from two different companies, on top of your server. See the full breakdown.
One licence instead of two subscriptions
A realistic WHMCS + cPanel stack runs upwards of $70/month, recurring, with prices that have risen every year since 2019. DeployOS's Agency licence is $299 once.
Modern apps, not just PHP sites
cPanel accounts are built for shared-hosting-era PHP/MySQL sites. DeployOS clients can run anything Docker can run - Node, Python, Go, databases, any of DeployOS's 247 templates.
Who this is actually for
Freelancers hosting client sites
You're already running 3-5 client projects on a VPS informally. Turn that into priced packages with real limits and a paper trail instead of one shared box with no billing attached.
Agencies standardizing client hosting
Stop hand-rolling a resource plan per client. Define a few Packages once, assign new clients to one, and let suspension on non-payment happen automatically.
Anyone with spare capacity on a server they already run
If you're paying for a VPS for your own apps and it isn't maxed out, Client Hosting Mode is a way to make the unused half of it pay for itself.
Questions
Do I need a separate server for my clients?
No - clients run on the same VPS as your own apps, isolated from each other with per-client Docker resource limits and a dedicated network per client, so one client's app can't see or affect another's.
What stops me from overselling my server?
DeployOS checks real numbers, not guesses. A one-time SSH probe reads the server's actual total RAM; before provisioning a new client, DeployOS sums what's already sold and blocks the request if it would push the server past 90% of real capacity - the same check runs on the website and in the desktop app, so you can't bypass it from either side.
How do clients actually pay me?
However you already collect payment - your own Stripe Payment Link, PayPal.me, a bank transfer. DeployOS never processes the payment itself; it tracks whether an invoice is paid and drives suspension/restoration from that.
What happens when a client stops paying?
Their invoice goes overdue, their service moves into a grace period you control (in days), and once that elapses their site automatically starts serving a branded "paused" page - enforced by a small container on the VPS that polls your billing status continuously, independent of whether your desktop app is even open. Marking the invoice paid restores it on the next check.
Which DeployOS licence do I need?
Pro ($149 one-time) includes Client Hosting Mode for up to 3 clients. Agency ($299 one-time) unlocks unlimited clients and a white-label Client Portal with no DeployOS branding.
Is this the same as DeployOS's own pricing - do I pay DeployOS per client?
No. Client Hosting Mode is included in your one-time Pro or Agency licence. What you charge your own clients, and how you collect it, is entirely yours.
Keep reading
Free plan for one server, Solo $79, Pro $149 - one-time, includes a year of updates.