Host clients on your own cloud — keep the margin.
Built for agencies running Odoo for many clients: connect your cloud, deploy each client tenancy on it, and own both the infrastructure and the markup.
Per-project, per-user hosting erodes your margin
On Odoo.sh, every client project is its own subscription, billed per user and per worker on Odoo's infrastructure. As your client roster grows, that bill scales linearly — and it scales on the dimension you least control, because adding seats is exactly what a healthy client does.
You can mark it up, but you're reselling someone else's platform at someone else's price. The end customer is one invoice away from realising they could buy it directly, and the underlying cloud cost is never itemised, so you can't show where the money actually goes. Your margin is whatever's left after the platform takes its cut first.
How CloudWady changes the math
Three shifts turn hosting from a cost you pass through into a margin line you control.
Per-company seat pools
You buy a pool of seats for a client company and allocate them across that tenancy — not a per-user line that climbs every time someone logs in. Adding a user inside the pool is free, so the client's growth stops being a tax on your margin and becomes room you already paid for.
Your cloud, no markup
Each client tenancy runs on a cloud account you own. The provider invoices the raw rate — CloudWady never resells compute or adds a margin on top of it. You pay a flat platform fee for the deploy and management layer, then set whatever price your client agreement supports. The spread is yours.
Repeatable rollouts
Deploying the eleventh client looks exactly like the first: connect the cloud, pick a region, push the repo, and CloudWady provisions the server, installs Odoo, issues SSL, and schedules backups. The same workflow runs across every tenancy, so onboarding a client is a process, not a project.
You stay in front of the client
Because the cloud account is yours and the tenancy lives inside it, you own the operational relationship end to end. You hold SSH on the server, root on the database, and visibility into every deployment — the access a partner managing real client systems needs, rather than the restricted editor a fully managed platform hands out.
The platform stays in the background. CloudWady is the control plane you operate the fleet from; your clients see the Odoo instance and your invoice, not a third party between you. And because everything runs on infrastructure you control, there's no vendor sitting one click away from your customer.
Run 10 clients without 10x the ops
The work that doesn't scale on a per-project platform is exactly the work CloudWady standardises across every tenancy.
One console, every tenancy
See all client deployments in a single dashboard — status, versions, and recent runs — instead of logging into a separate project for each.
Backups by default
Every tenancy gets scheduled backups to your chosen object store with per-tenant encryption — the same policy applied everywhere, not configured one client at a time.
Deploy from Git
Push to the client's repo and CloudWady rolls it out, with rollback if a release misbehaves. Your custom modules install the same way on every tenancy.
Roles per client
Grant each teammate the right access on the right tenancy without handing out the keys to everything. A client's own admin sees their dashboard, never your fleet.
EU residency, when your clients need it
Place any tenancy in an EU region and the data stays there, operated under EU rules by syscoon GmbH in Germany. For clients with residency requirements, you can answer the "where does our data live?" question with a region you chose — not one a platform chose for you.
Build a hosting line your clients can't buy direct
Connect your cloud, deploy your first client tenancy, and see the economics for yourself — per-company seat pools, your cloud at the provider's raw rate, and the markup staying with you.