Last updated: 2026-08-09
Last updated: August 9, 2026. If you're self-hosted, on Community, or running Enterprise on your own server, and you're wondering why your instance shows "19.0" while an Odoo Online demo or a sales conversation referenced "19.4", here's the actual explanation, not the vague version most search results give.
The model, precisely
Odoo 19.0 is the major version. It is the version that gets packaged, released, and made available for download and self-hosted installation. Odoo 19.1 through 19.4 are intermediary releases that exist only inside Odoo Online, Odoo's own SaaS hosting. They are not separate downloadable packages. There is no .deb, no Docker image tag, no source tarball for "Odoo 19.4" that you can install on your own server, because it was never built to be installed that way. Odoo 19.4 landed on Odoo Online in July 2026.
Why this model exists
Odoo Online is a single, centrally managed platform Odoo controls end to end. Shipping smaller, more frequent feature updates to that platform (roughly quarterly, hence 19.1, 19.2, 19.3, 19.4) is operationally straightforward for Odoo because they control every instance's infrastructure directly. Self-hosted and Community installations are, by definition, not centrally managed, every business runs its own server, its own customisations, its own upgrade schedule. Shipping intermediary releases to that population would mean asking thousands of independently managed servers to take incremental upgrades multiple times a year, which is a much bigger support and compatibility burden than a single annual major version.
What self-hosted users actually get
Self-hosted, Community, and on-premise Enterprise users receive security patches and bug fixes to 19.0 on an ongoing basis, that maintenance stream is separate from the 19.1-19.4 feature releases. What you do not get automatically is the new functionality introduced in 19.1 through 19.4, those features arrive for self-hosted users only when the next major version, Odoo 20, ships and rolls the accumulated 19.x feature set into a new downloadable major release.
A concrete comparison
| Odoo Online (SaaS) | Self-hosted / Community / on-prem Enterprise | |
|---|---|---|
| Version shown | 19.4 (as of July 2026) | 19.0 |
| Gets 19.1-19.4 features | Yes, automatically | No, not until Odoo 20 ships them as part of a major release |
| Gets security patches | Yes, automatically | Yes, applied manually or via your own update process |
| Installable/downloadable | N/A, hosted by Odoo | Yes, this is the version you actually install |
| Next feature jump | 19.5 (if it exists) or 20 | Odoo 20, whenever it ships |
Why this causes confusion
Odoo's own marketing and sales conversations sometimes reference the newest Odoo Online feature set without always being explicit that it's SaaS-only. A prospective client who saw a 19.4 demo, then installs self-hosted Odoo and gets 19.0, reasonably assumes something is broken or out of date. Nothing is broken, this is the intended, documented split, it's just not always communicated clearly at the point someone actually experiences the mismatch.
We've seen this specific confusion play out the same way several times with clients: someone in the business watches an Odoo webinar or reads a feature announcement referencing something in 19.2 or 19.3, gets excited about it, then asks their DevOps team (or us) why it's missing from their production instance. The instinct is to assume a failed update or a misconfiguration. The actual answer is simpler and less alarming, the feature was never going to be on a self-hosted 19.0 instance in the first place, regardless of how up to date the patching is.
How to tell which one you're actually running
If you're not sure whether your instance is Odoo Online or self-hosted, or you've inherited a server and want to confirm, the version string alone is the fastest signal. Check the Settings > General Settings page in the Odoo backend, or query it directly:
# From an Odoo shell on the server
sudo -u odoo /opt/odoo/venv/bin/python3 /opt/odoo/odoo-bin shell -d your_db --no-http <<'EOF'
print(env['ir.module.module'].search([('name','=','base')]).latest_version)
EOFA self-hosted or on-premise Enterprise instance will report a version string starting 19.0. If you see anything else, and you believe you're self-hosted, that's worth investigating on its own, since it would mean either the instance isn't what you think it is, or something unusual happened during a past upgrade.
Does this affect Enterprise self-hosted the same way as Community?
Yes. The 19.1-19.4 intermediary release model is specifically tied to the Odoo Online hosting platform, not to the Community/Enterprise licensing split. A self-hosted Enterprise instance is on the same footing as a self-hosted Community instance here, both stay on 19.0 until Odoo 20 ships. Enterprise licensing gets you access to Enterprise-only apps and features within whatever major version you're on, it does not change which release cadence your server follows.
Why Odoo doesn't just backport 19.1-19.4 features to self-hosted 19.0
This is a reasonable question and worth answering directly rather than just stating the policy. Backporting individual feature releases to an already-shipped major version, rather than bundling accumulated changes into the next major version, would mean maintaining multiple parallel, diverging codebases of the same major version simultaneously, one for Odoo Online's current state and one for the original self-hosted 19.0 release, plus every point in between as more intermediary releases ship. That's a meaningfully larger ongoing engineering and QA burden than Odoo's actual model: one stable self-hosted release per major version, patched for bugs and security only, with new functionality reserved for the next major version. The tradeoff is real, self-hosted users wait longer for new features, but the alternative would mean less stability and slower security patch turnaround for the exact same self-hosted population, which is the opposite of what most self-hosted businesses actually want from their production Odoo instance.
What this means for evaluating Odoo based on a demo or sales call
If you're currently evaluating Odoo and someone shows you a live Odoo Online instance during a demo or sales conversation, ask directly which release you're looking at, and separately ask what you'd actually get on day one of a self-hosted or on-premise Enterprise deployment. This isn't a criticism of the sales process, Odoo Online genuinely does have the newest features and that's a fair thing to demo, but it means the demo and your actual production reality can differ meaningfully if you're planning to self-host, and it's better to know that gap going in than to discover it after a deployment decision is already made. If a specific 19.1-19.4 feature is the deciding factor in your evaluation, that's a legitimate reason to seriously consider Odoo Online itself rather than self-hosting, not a reason to be surprised later that self-hosted 19.0 doesn't have it.
How this plays out across a typical year
To make the timeline concrete: Odoo 19.0 shipped as the self-hosted major version at Odoo Experience 2025. Through 2026, Odoo Online received 19.1, 19.2, 19.3, and 19.4 in turn, each adding incremental functionality on top of the last, while self-hosted 19.0 installations received only bug and security fixes across that same period, no new features. When Odoo 20 eventually ships, expected around Odoo Experience 2026 in September with general availability following, self-hosted users get a single release that bundles the accumulated 19.1-19.4 feature work together with whatever's new specifically for 20. That's the mechanism by which self-hosted users do eventually catch up, just on Odoo's major-version cadence rather than the SaaS platform's quarterly one.
FAQ
Will I ever get 19.4 features on my self-hosted server?
Only indirectly, when Odoo 20 ships and rolls the accumulated 19.x feature work into the next downloadable major version.
Is my self-hosted 19.0 instance behind on security?
No, if you're applying the ongoing 19.0 patch stream. Security patching is separate from the 19.1-19.4 feature releases.
Can I migrate to Odoo Online to get 19.4 features sooner?
Yes, that's the only path to those specific intermediary features before Odoo 20 ships, but it means moving your hosting model entirely, not a small config change. If you're weighing that tradeoff against staying self-hosted for infrastructure control reasons, see our Odoo.sh vs self-hosted comparison, the same underlying tradeoffs apply between Odoo Online and self-hosting generally.
Does Odoo.sh follow the same version model as Odoo Online, or as self-hosted?
Odoo.sh runs the same downloadable major versions as self-hosted installations, 19.0 currently, not the 19.1-19.4 intermediary releases. Odoo.sh gives you managed infrastructure and Git-based deployment on top of a standard major version, it is a different hosting model from Odoo Online's SaaS platform, and the 19.1-19.4 releases are specific to Odoo Online, not to Odoo.sh.
If we're currently on 19.0 self-hosted, is there any benefit to waiting for 19.4-equivalent features versus just planning for 20?
No, waiting specifically for "19.4 equivalent" features isn't a real option for self-hosted users, those features only arrive bundled into Odoo 20 itself, there's no separate self-hosted 19.4 release to wait for. Plan around Odoo 20's actual timeline, not an intermediary release that was never going to be available to you as a standalone download.
Does Enterprise licensing change any of this?
No. Self-hosted Enterprise and self-hosted Community both stay on the 19.0 release stream. The 19.1-19.4 cadence is tied to Odoo Online hosting, not to your license tier.
Sources: Odoo official documentation.