What Odoo.sh actually costs.

The itemised bill

Ten users, one worker, 50 GB storage, one staging environment:

The licence is 83% of it. That's the thing to understand before optimising anything: Odoo.sh's infrastructure charges are not where your money is going. The per-user Custom plan is, and it scales with headcount rather than with load.

Twenty users on the same infrastructure is roughly $1,082 a month. Fifty is about $2,552. The workers don't change; the licence triples.

What a "worker" is, and how many you need

A worker is a process handling requests. More workers means more concurrent users served and more background jobs processed in parallel.

Rough guidance, and treat it as rough:

• 1 worker — small teams, light usage, a handful of concurrent sessions
• 2–3 workers — dozens of concurrent users, or heavy scheduled jobs
• 4+ — high concurrency, large imports, heavy reporting, e-commerce traffic

The trap is that worker requirements are driven by concurrency and background load, not by user count. A ten-person business running a busy Shopify sync and nightly imports can need more workers than a thirty-person business doing light CRM. Sizing on headcount alone gets it wrong in both directions.

Staging environments bill separately, and most teams want at least one.

What you get for it

Being fair, because this page isn't an argument that Odoo.sh is bad:

• Git-based deployment with branch-per-environment. Push to a branch, get an environment. Genuinely good, and the main reason developer-heavy teams choose it.
• Managed backups and monitoring
• One-click staging builds from production data
• The official upgrade path, run by Odoo
• Odoo supporting the whole stack, so there's no argument about whose problem an issue is

If you have developers working on custom modules with a real deployment workflow, that Git integration is worth something concrete. Odoo.sh is a reasonable product priced for a specific kind of customer.

The question is whether you're that customer.

Where it stops making sense

You have no developers. The Git workflow is the main differentiator. If nobody on your team pushes to a branch, you're paying a premium for a feature you don't use.

Headcount is your growth axis. The licence is 83% of the bill and it's per-seat. Adding ten warehouse staff adds roughly $490 a month before a single extra worker.

You only wanted the API. Custom is required for external API access as well as for Odoo.sh, so businesses sometimes end up on this tier for an integration and inherit the whole cost structure with it.

You wanted staging, not a platform. Staging environments are useful and available far more cheaply elsewhere.

The alternatives, honestly

Odoo Online (Standard). Cheaper — around $31.10/user/month at US renewal — but no custom modules, no Python code, no Studio, no external API. Fine for standard workflows, a dead end for anything bespoke.

Self-hosted Community. No licence at all. You own backups, patches, upgrades, monitoring and sizing. Cheap in money, expensive in attention, and the failure mode is that upgrades quietly become nobody's job.

Third-party managed Odoo hosting. A middle path — someone else runs the infrastructure, without Odoo's per-seat licence. Quality varies enormously; ask the ownership questions before signing.

Enterprise licence on your own infrastructure. Keep the Enterprise licence and its upgrade service, host it yourself or with a provider. Works when Studio or an Enterprise app is genuinely required but Odoo.sh isn't.

The questions to ask before committing

1. How many workers do we actually need? Get this from expected concurrency and background job load, not headcount.
2. Is the licence line the real cost? At ten users it's 83% of the bill. Model it at your headcount in three years.
3. Will we use the Git workflow? If no developer touches it, that's the whole value proposition gone.
4. Do we need Custom for other reasons? Studio, multi-company, external API. If yes, the marginal cost of Odoo.sh is smaller than it looks.
5. Whose account is the subscription under? Ask in writing, of any provider. Who owns your Odoo database explains why.

What we charge instead

$150/month for up to 25 people. $450/month for unlimited people. Standard Odoo Community, hosted, with a live copy and a test copy, backups, security patches and version upgrades included — plus every module we've built.

At ten users that's $150 against roughly $593. At twenty-five it's still $150, against about $1,300.

What you give up, plainly: this is Community, so no Odoo Studio, no official Odoo SA support contract, no Enterprise-only apps, and no Git-branch deployment workflow. If your team lives in that workflow, Odoo.sh is a real product doing a real job and we're not a substitute for it.

What we do offer instead of Studio is plain-English module creation that writes ordinary Odoo code onto your test copy first — and the test copy covers most of what people actually use staging for. Your server and data are yours; download the database and go, no exit fee.

See the pricing · Flat-fee Odoo hosting

The rest of the cluster