Odoo.sh was the obvious choice for agencies managing client Odoo deployments when it launched. Integrated CI/CD, branch-based staging, and direct Odoo SA support seemed compelling. But after running real client portfolios on it, many agencies have concluded that the cost structure, limitations, and lack of server control make it the wrong long-term choice. Here's an honest breakdown of why agencies are leaving — and where they're going.
The Cost Problem: 10 Clients on Odoo.sh
Odoo.sh pricing is per-project (i.e., per client instance). As of 2026, pricing starts at approximately €19.90/month per project for the One plan. At the more practical Production plan with staging support, costs rise to roughly €39.90/month per project.
Run the math for 10 clients:
- Odoo.sh (One plan, 10 clients): ~€200/month (~$220)
- Odoo.sh (Production plan, 10 clients): ~€400/month (~$440)
Compare that to self-hosted:
- 10 x Hetzner CX22 VPS: ~€50/month total — or ~€100/month on dedicated CX32 instances
- DeployMonkey Agency plan: $150/month for managed hosting across your client portfolio
The gap compounds annually. An agency with 20 clients on Odoo.sh Production pays ~$880/month in hosting alone. The same portfolio on BYOS managed hosting with DeployMonkey costs $150/month plus roughly $200/month in VPS costs — a total of $350/month. That's $530/month saved, or $6,360/year, which is real margin that goes back to the agency.
No Server Control
Odoo.sh abstracts the underlying infrastructure entirely. You cannot SSH into the server, tune PostgreSQL settings, install system packages, configure nginx rules, or adjust worker counts. If a client has a performance problem that requires a database index or a configuration change, you're limited to what Odoo.sh exposes in its interface.
For agencies building serious custom modules, this is a fundamental constraint. Some third-party integrations require system-level packages. Some performance optimizations require PostgreSQL configuration. On Odoo.sh, these are simply not available.
With BYOS hosting, the server is yours. You can SSH in, install what you need, tune what's slow, and configure infrastructure to match the client's actual requirements.
Community Edition Not Supported
Odoo.sh only supports Enterprise edition. If you have clients who don't need Enterprise features — or clients for whom the Enterprise per-user cost doesn't make business sense — Odoo.sh is simply not an option.
Many agency client projects run perfectly well on Community edition. Accounting, CRM, inventory, manufacturing, website, and eCommerce are all available in Community. For these clients, forcing Enterprise just to use Odoo.sh adds unnecessary cost to the client relationship.
BYOS hosting supports both Community and Enterprise. You choose the right edition for each client based on their needs, not based on what the hosting platform requires.
Staging Environment Limitations
Odoo.sh's branch-based development workflow is genuinely useful for development agencies. However, the staging environment shares the project's resource allocation, and testing heavy data migrations or load scenarios is constrained by what the plan allows.
On your own VPS, you can spin up a staging instance on a separate server, run database copies for testing, and tear them down when done — all without extra per-project cost.
Migration Path from Odoo.sh
Migrating a client from Odoo.sh to a BYOS deployment is straightforward:
- Download a full database backup from the Odoo.sh project dashboard
- Provision a new VPS on your preferred provider (Hetzner, Vultr, DigitalOcean)
- Install Odoo on the same version as the client's current deployment
- Restore the database backup and filestore
- Update DNS to point to the new server
- Verify SSL, email, and payment provider configurations
The migration typically takes 2–4 hours per client for an experienced administrator. DeployMonkey can handle the managed infrastructure side once the server is provisioned, so you're not adding ongoing server management work — just eliminating the Odoo.sh fee.
What You Give Up
Odoo.sh's integrated CI/CD and branch preview environments are genuine features. If your development workflow relies heavily on branch-based testing with Odoo.sh's automatic staging builds, you'll need to replicate that with your own tooling (Docker-based local development plus a shared staging server works well for most agencies).
Odoo.sh also provides direct Odoo SA infrastructure support. On BYOS, you manage the infrastructure yourself (or via a managed host like DeployMonkey). For most agencies, infrastructure issues are infrequent and manageable — but if you rely on Odoo SA support for server problems, factor that into the decision.
DeployMonkey for Agencies
The DeployMonkey Agency plan ($150/month) is designed for exactly this scenario: an agency managing multiple client Odoo deployments on BYOS infrastructure. You get managed hosting for your client portfolio, with SSL, backups, monitoring, and support included — on servers you and your clients own.
Read our full DeployMonkey vs Odoo.sh comparison or see the broader landscape of Odoo.sh alternatives in 2026. For a complete agency hosting guide, see Odoo hosting for agencies.
Frequently Asked Questions
Can I keep the Odoo.sh CI/CD workflow when I migrate?
Not directly — Odoo.sh's branch preview system is proprietary. Most agencies replace it with a Docker-based local development workflow plus a shared staging server. It requires more initial setup but gives more flexibility.
Will my custom modules work on a BYOS deployment?
Yes. Custom modules that run on Odoo.sh run on any Odoo installation of the same version. You may need to install additional system packages that Odoo.sh previously provided, but this is straightforward with server access.
How long does migration from Odoo.sh take?
Typically 2–4 hours per client instance for an experienced administrator. The process is database backup, server provision, restore, DNS update, and verification. Downtime can be kept to under 30 minutes with good planning.
Does DeployMonkey support Odoo Community edition clients?
Yes. DeployMonkey supports both Community and Enterprise across Odoo 14–19. You choose the right edition for each client.
Can clients have their own server accounts separate from my agency account?
Yes. Each DeployMonkey account is independent. You can manage your client portfolio under your agency account or help each client set up their own DeployMonkey account and manage their own server.