Odoo Hosting and Deployment: The Complete Guide

This is the overview page for everything we publish on running Odoo in production, hosting it, deploying it, upgrading it, and fixing it when something breaks. We built this because most "Odoo hosting guide" content online is either a thin marketing page or a single narrow tutorial. This page links out to the real depth, organised by what you're actually trying to solve.

Where most Odoo hosting problems actually come from

Across 70+ Odoo deployments, the pattern repeats more than people expect. Production incidents rarely trace back to Odoo itself being broken, they trace back to infrastructure that was configured once, worked at the time, and was never revisited as load or data grew. A worker count set for a 10-user pilot still running unchanged at 100 concurrent users. A postgresql.conf left on its out-of-the-box defaults on a database that's now 40GB. Nginx timeouts copied from a tutorial that never accounted for long-polling traffic. None of these are Odoo bugs, they're infrastructure decisions that quietly stopped matching reality. The posts linked below exist because these are the specific, recurring gaps we keep finding and fixing.

There's also a second pattern worth naming: decisions made under time pressure during an incident tend to be worse decisions than the same decisions made calmly beforehand. Raising a timeout value during an active outage, without first confirming the actual root cause, is a common example, it often masks the symptom just long enough for the same failure to recur at a worse moment. Nearly everything in this guide is written to be read before you need it, not during an active incident, the troubleshooting posts are the exception, built specifically for the moment something is already broken and you need the fastest accurate path to a real fix.

How to use this guide

If you're evaluating Odoo hosting options before committing to an approach, start with the comparisons section, particularly Odoo.sh vs self-hosted and Community vs Enterprise, both directly affect what your infrastructure even needs to look like. If you're already running Odoo and something specific is broken right now, skip straight to troubleshooting, every post there leads with the exact error message so you can confirm you're in the right place before reading further. If you're planning a new deployment or a version upgrade, the deployment guides and the Odoo 20 cluster below are written in the order we'd actually work through a real project: provision correctly first, tune the database, set up backups before you need them, then plan version upgrades with a real staging rehearsal rather than a live cutover on faith.

Odoo 20: what's coming, and what to do now

Odoo 20 hasn't shipped yet, but there's real prep work worth doing today, and a lot of confident guessing online that we've deliberately avoided repeating. Start with the pillar post, then go deeper on the two most technically significant infrastructure changes.

• Odoo 20 release date, features and roadmap: the full picture, sorted into confirmed facts and open speculation.
• Odoo 20 native MCP server: what ai_mcp actually ships, and how it differs from the community mcp_server module.
• Odoo read replicas and PostgreSQL scaling: what changes, and what you can already do today without waiting.
• Should you upgrade to Odoo 19 now or wait for 20? A decision framework by your current version.
• Odoo 19 to 20 upgrade planning: prep work you can start before 20 even exists.
• Odoo 19.4 vs Odoo 19 self-hosted: why your self-hosted instance doesn't show 19.4, explained properly.

Troubleshooting: exact errors, ranked causes, real fixes

If you landed here from a search for a specific error message, these posts are built for that: the error up top, ranked causes with diagnostic commands, and a working fix.

• Odoo 502 Bad Gateway Nginx
• Odoo worker timeout and limit_time_real
• Odoo WebSocket not connecting through Nginx
• Why your bus.Bus errors are actually an Nginx problem
• Odoo restore: attachments missing after filestore restore
• Odoo psycopg2.OperationalError: role does not exist
• The Odoo workers formula that stopped our server crashing

Deployment guides: from bare server to production

• Install Odoo 19 on Ubuntu 24.04 for production
• Odoo 19 Docker Compose for production
• PostgreSQL tuning for Odoo, concrete values by server size
• Automated Odoo backups to S3
• Uptime Kuma for an Odoo fleet

Comparisons and migration

• Odoo.sh vs self-hosted VPS, an honest comparison
• Migrate from Odoo.sh to your own server
• Odoo 17 to 19 upgrade guide
• Odoo Community vs Enterprise 2026
• Contabo vs Hetzner vs DigitalOcean for Odoo hosting
• How we migrated 11 production Odoo servers with zero downtime

A note on how we handle version 20

Odoo 20 doesn't exist yet as a stable release, and a lot of what's published about it online right now is confident-sounding speculation. We've deliberately structured every post in the Odoo 20 cluster with an explicit confirmed-vs-speculation split, and a visible "last updated" line, because this is a fast-moving topic and we'd rather be honest about what's uncertain than join the pile of guesses. If you're reading this after Odoo Experience 2026 (September 24-26, Brussels), check the "last updated" date on each post, we intend to keep them current as real information replaces the current roadmap-stage picture.

How the pieces fit together, in the order a real project actually runs

Most businesses don't need every post in this guide at once, but it's worth understanding how they connect for when you do. A typical engagement starts with a hosting decision (Odoo.sh vs self-hosted, Community vs Enterprise), moves into a correct initial deployment (the Ubuntu or Docker install guides, followed immediately by PostgreSQL tuning and backup automation before go-live, not after), then settles into steady-state operation where the troubleshooting posts become the reference material for whatever comes up. Version upgrades are a separate, periodic project layered on top of that steady state, planned in advance rather than reacted to. The Odoo 20 cluster exists because that particular upgrade decision is on a lot of businesses' minds right now, specifically, and deserves its own honest treatment rather than being folded into generic upgrade advice.

Why we wrote all of this

We run Odoo infrastructure for a living, 70+ deployments across Odoo 13 through 19, Community and Enterprise, Docker-based and service-based. This guide, and the posts it links to, are written from that production experience, not from reading Odoo's own documentation and rephrasing it. Where something is genuinely uncertain, in particular anything about Odoo 20 before it ships, we say so directly instead of writing a confident guess dressed up as fact. We'd rather a post be slightly less exciting to read and be right, than confidently wrong in a way that costs someone a bad infrastructure decision.

If you need hands-on help with any of this, hosting, migration, upgrades, or ongoing management, see our Odoo DevOps and Infrastructure service or get in touch.