Odoo Online vs Odoo.sh vs Self-Hosted: How to Choose the Right Odoo Hosting

One of the first decisions you'll make when adopting Odoo is where to host it. Odoo gives you three options: Odoo Online, Odoo.sh, and self-hosted (on-premise or your own cloud VPS). Each has genuine trade-offs, and choosing the wrong one can cost you time, money, and flexibility down the line.

This guide breaks down exactly what each Odoo hosting option gives you, what it doesn't, and how to decide which one fits your business. No jargon walls — just the practical stuff.

The three Odoo hosting options at a glance

Before we go deep, here's the quick version:

• Odoo Online — Odoo's fully managed SaaS platform. Odoo hosts it, updates it, and maintains it. You log in and use it. No custom code allowed.
• Odoo.sh — Odoo's platform-as-a-service (PaaS). Git-based deployments, staging environments, and the ability to install custom modules. Odoo manages the infrastructure; you manage the code.
• Self-hosted Odoo — You host Odoo on your own server (on-premise or cloud VPS like AWS, DigitalOcean, Hetzner). Full control over everything — infrastructure, code, updates, backups.

Odoo Online: simplest, but most limited

Odoo Online is the easiest way to get started with Odoo. You sign up at odoo.com, pick your apps, and you're live in minutes. Odoo handles all the infrastructure, backups, security, and version upgrades automatically.

What you get with Odoo Online

• Zero infrastructure management — Odoo handles servers, backups, SSL, and updates
• Automatic upgrades to new Odoo versions as they're released
• Access to all standard Odoo Enterprise apps
• Simple per-user pricing model
• Built-in Odoo support

What you don't get with Odoo Online

• No custom modules — you cannot install any third-party or custom-built Odoo modules. This is the biggest limitation.
• No direct database access — you can't run SQL queries or access the Odoo database directly
• No server-level control — no cron jobs, no custom Python packages, no server configuration changes
• Limited third-party integrations — anything requiring server-side code won't work
• You're on Odoo's upgrade schedule — you upgrade when Odoo says so, not when you're ready

Odoo.sh: the middle ground

Odoo.sh is Odoo's own cloud platform built specifically for businesses that need custom modules but don't want to manage servers. It's tightly integrated with Git, gives you proper staging environments, and handles deployments through a clean CI/CD pipeline.

What you get with Odoo.sh

• Custom module support — install your own Odoo modules, third-party apps from the Odoo App Store, and bespoke code
• Git-based deployments — push to a branch and Odoo.sh deploys it. Every branch gets its own environment.
• Automatic staging environments — staging branches clone production data, so you can test changes against real data before deploying
• Built-in CI/CD — automated testing on every push, with deployment triggered by merging to production
• Managed infrastructure — Odoo handles servers, backups, SSL, monitoring, and disaster recovery
• Shell access and logs — you can SSH into your Odoo.sh instance and access server logs directly
• Odoo App Store integration — install and update third-party Odoo modules directly from the platform

What you don't get with Odoo.sh

• Full server control — you can't install arbitrary system packages, change Nginx configs, or run non-Odoo services on the same box
• Predictable costs at scale — Odoo.sh pricing scales with staging branches and workers, which can get expensive for large deployments
• Multi-tenancy — you can't run multiple Odoo databases on a single Odoo.sh subscription the way you can on self-hosted
• Choice of data centre region — Odoo.sh hosting locations are limited compared to choosing your own cloud provider

Self-hosted Odoo: maximum control

Self-hosted means you run Odoo on infrastructure you control — whether that's a cloud VPS (AWS, DigitalOcean, Hetzner, Vultr), a managed server, or physical hardware in your office. You're responsible for everything: installation, configuration, backups, security, and upgrades.

What you get with self-hosted Odoo

• Full control — install anything, configure anything, run Odoo alongside other services
• Custom modules without restriction — any Odoo module, any Python package, any integration
• Direct database access — full PostgreSQL access for reporting, migrations, and debugging
• Odoo Community Edition option — self-hosting is the only way to run Odoo Community (free, open-source) in production
• Cost efficiency at scale — for large user counts, self-hosted Odoo is often significantly cheaper than Odoo.sh or Odoo Online
• Choose your data centre — host in Australia, in a specific region, or on-premise for data sovereignty requirements
• Multi-database support — run multiple Odoo instances or databases on the same server

What you don't get with self-hosted Odoo

• Managed infrastructure — you're responsible for uptime, backups, security patches, and monitoring (or you hire someone like us to do it)
• Automatic upgrades — Odoo version upgrades are manual and require testing, especially with custom modules
• Built-in staging — you'll need to set up your own staging environments
• Git-integrated CI/CD — you'll need to build your own deployment pipeline or use external tools

Key factors to consider when choosing

1. Do you need custom Odoo modules?

This is the single biggest decision point. If the answer is yes — or even "probably, eventually" — then Odoo Online is off the table. You'll need Odoo.sh or self-hosted. If you're confident you'll only ever use standard Odoo apps, Odoo Online is the simplest path.

2. What's your technical capability?

Odoo Online requires zero technical knowledge. Odoo.sh requires developers who understand Git and Odoo module development. Self-hosted requires Linux sysadmin skills (or a managed hosting partner). Be honest about what your team can actually support.

3. What does Odoo hosting actually cost?

Pricing varies significantly across the three options:

• Odoo Online — per-user subscription. Simple and predictable, but you're paying for every user.
• Odoo.sh — base subscription plus per-user fees, plus additional cost for extra staging branches and workers. Costs grow as your instance grows.
• Self-hosted Odoo — you pay for infrastructure (typically $50–$300/month for a VPS) plus Odoo Enterprise licensing if you want Enterprise features. No per-worker charges. Often the cheapest option at scale.

4. How important is uptime and disaster recovery?

Odoo Online and Odoo.sh both include managed backups and disaster recovery as part of the platform. With self-hosted Odoo, you need to set this up yourself — automated backups, tested restores, monitoring, and an incident response plan. It's not hard, but it does need to be done properly.

5. Do you have data residency or compliance requirements?

Some Australian businesses need their data hosted in Australia, or on infrastructure they control, for regulatory or compliance reasons. Self-hosted Odoo gives you full control over where your data lives. Odoo.sh and Odoo Online host data on Odoo's infrastructure, which may or may not meet your requirements.

6. How many users will you have?

Per-user pricing on Odoo Online and Odoo.sh means costs scale linearly with headcount. If you're a 10-person team, the difference is negligible. If you're a 200-person company, self-hosted Odoo with an Enterprise licence can save you tens of thousands per year compared to Odoo.sh.

7. How often will you need to upgrade Odoo?

Odoo Online upgrades automatically — which is great unless you're not ready. Odoo.sh gives you control over when you upgrade, with staging to test first. Self-hosted Odoo lets you stay on any version as long as you want — but you're responsible for planning and executing the upgrade when you're ready.

Quick comparison: Odoo Online vs Odoo.sh vs self-hosted

Here's a side-by-side summary to help you compare Odoo hosting options:

• Custom modules — Odoo Online: ❌ No | Odoo.sh: ✅ Yes | Self-hosted: ✅ Yes
• Odoo Community Edition — Odoo Online: ❌ No | Odoo.sh: ❌ No | Self-hosted: ✅ Yes
• Managed infrastructure — Odoo Online: ✅ Yes | Odoo.sh: ✅ Yes | Self-hosted: ❌ You manage
• Git-based CI/CD — Odoo Online: ❌ No | Odoo.sh: ✅ Yes | Self-hosted: ❌ DIY
• Staging environments — Odoo Online: ❌ No | Odoo.sh: ✅ Automatic | Self-hosted: ❌ DIY
• Direct database access — Odoo Online: ❌ No | Odoo.sh: ⚠️ Limited | Self-hosted: ✅ Full
• Automatic version upgrades — Odoo Online: ✅ Auto | Odoo.sh: ⚠️ Manual | Self-hosted: ⚠️ Manual
• Data residency control — Odoo Online: ❌ No | Odoo.sh: ❌ Limited | Self-hosted: ✅ Full
• Cost at scale (100+ users) — Odoo Online: 💰💰💰 | Odoo.sh: 💰💰 | Self-hosted: 💰

Our recommendation

After implementing Odoo for businesses across Australia, here's our honest take:

• Choose Odoo Online if you're a small business (under 15 users), you'll only use standard Odoo apps, and you want the absolute simplest setup with zero maintenance.
• Choose Odoo.sh if you need custom Odoo modules, want proper development workflows, and prefer not to manage infrastructure. It's the best balance of flexibility and convenience for most Australian businesses using Odoo.
• Choose self-hosted Odoo if you need full control, have data residency requirements, want to run Odoo Community Edition, or have a large user base where per-user pricing becomes expensive. Make sure you have the skills in-house or a managed hosting partner.

The worst thing you can do is pick Odoo Online because it's easy, then realise six months later you need a custom module and have to migrate everything. Think ahead. Start on the right platform.

Need help choosing the right Odoo hosting?

We help Australian businesses choose, set up, and manage their Odoo hosting every week. Whether you're starting fresh or thinking about migrating from Odoo Online to Odoo.sh (or vice versa), we'll give you an honest recommendation based on your actual needs — not what generates the biggest licence fee.

Book a free call and we'll walk through your situation together.