Odoo Community Edition is genuinely powerful software. It's free, open-source, and covers more business functionality than most companies will ever use. But if you've been running it for a while, you've probably started bumping into things it won't do or discovered that some hosting options you were considering don't support it.
This guide is honest about both. It explains which limitations are real blockers, which are commonly misunderstood, why Odoo.sh won't accept Community Edition deployments, and what your actual hosting options are.
What Odoo Community Edition actually is
Odoo Community is the open-source version of Odoo, released under the LGPL licence. It is free to download, free to use commercially, and free to modify. There are no per-user fees, no module licensing costs, and no restrictions on how many people use it.
It is not a stripped-down trial version of Enterprise. It is a fully functional ERP platform that covers CRM, sales, inventory, accounting, purchasing, manufacturing, eCommerce, project management, point of sale, HR, and more. Hundreds of thousands of businesses worldwide run on Community Edition without ever upgrading to Enterprise.
The limitations that do exist are specific and worth understanding clearly before you decide what to do about them.
The real limitations of Odoo Community Edition
1. Certain advanced modules are Enterprise-only
Some Odoo modules exist only in the Enterprise edition. The list varies by Odoo version, but commonly Enterprise-exclusive features include:
- Odoo Studio: the visual interface builder that lets non-developers customise views, create reports, and build automations without writing code
- Advanced accounting features including full IFRS reporting, account asset management, and certain localisation modules
- VoIP integration
- E-signature
- Some marketing automation features
- Certain HR and payroll modules depending on your country
This does not mean Community Edition lacks accounting, HR, or reporting. It has all of these. The Enterprise versions add specific advanced capabilities on top of what Community already provides.
What you can do about it: Many Enterprise-exclusive features have Community-compatible equivalents in the OCA (Odoo Community Association) module library. The OCA is a global organisation that maintains open-source Odoo modules, there are over 3,000 of them. Before assuming you need Enterprise for a specific feature, check OCA first.
2. No Odoo Studio
Odoo Studio is the drag-and-drop interface for customising Odoo views, creating custom reports, automating workflows, and building simple applications without code. It is exclusively available in Enterprise.
What you can do about it: For businesses with a technical team or an Odoo developer available, most of what Studio does can be achieved through XML views and Python code. This is more technical but more flexible, code-based customisation has no limits that a GUI tool does. For non-technical teams that genuinely need Studio's visual workflow builder, this is a real limitation and Enterprise should be evaluated.
3. No Odoo support from Odoo S.A.
Enterprise customers get access to Odoo's own support team. Community Edition users do not. If something goes wrong at the application level, you are relying on the community forum, your implementation partner, or your own technical knowledge.
What you can do about it: The Odoo community forum is large and active. Most common issues have been encountered and documented. For businesses that need guaranteed response times on application-level issues, a support contract with a certified Odoo partner is the practical alternative to Enterprise support.
4. No access to Odoo.sh
This is arguably the most practically significant limitation and the one that most confuses people when they first discover it.
Odoo.sh is Odoo's own managed hosting platform. It offers git-based deployment, staging environments, automated builds, and a professional developer workflow. It is an excellent product for what it does.
It is available to Enterprise customers only.
If you are running Odoo Community Edition, Odoo.sh will not host you. This is not a technical limitation that can be worked around. It is an explicit product decision by Odoo S.A. to restrict their hosting platform to paying Enterprise subscribers.
This leaves Community Edition users with a gap: the most obvious managed hosting option is unavailable to them. We address this directly in the hosting section below.
5. No native mobile app
Odoo's official mobile app connects to Enterprise instances. Community Edition does not have official mobile app support from Odoo S.A.
What you can do about it: Odoo's web interface is responsive and works on mobile browsers. For most use cases this is sufficient. OCA also maintains community-built mobile solutions for specific modules.
What Odoo Community Edition is not limited on
It is worth being clear about what Community does not limit, because this is frequently misunderstood.
Users. There is no user limit in Community Edition. You can have one user or ten thousand. No per-user fee, no tier restriction.
Custom modules. You can build, install, and run any custom module on Community. OCA modules, bespoke development, third-party addons, all fully supported.
Database access. Community gives you full access to the underlying PostgreSQL database. You can query it, back it up, integrate it with external tools, and run custom reporting against it directly.
API access. Odoo's XML-RPC and JSON-RPC APIs are available in Community Edition. You can integrate Odoo with any external system that supports API connections.
Customisation. Everything you can customise in Enterprise through code, you can customise in Community. The difference is Studio, code-based customisation is fully available in both.
Odoo.sh and Community Edition: the full picture
Because this question comes up constantly, it is worth addressing it directly.
Is Odoo.sh available for Community Edition?
No. Odoo.sh only supports Odoo Enterprise. To use Odoo.sh you must hold a valid Odoo Enterprise subscription. There is no workaround, no legacy plan, and no exception — this is Odoo S.A.'s explicit policy.
This is a significant constraint for Community Edition users because Odoo.sh's git-based workflow is genuinely well-designed for Odoo development. Agencies and developers who work with both Community and Enterprise clients frequently cite this as a pain point, they can use Odoo.sh for Enterprise clients but cannot offer the same workflow to Community clients.
The practical implication: if you are running Odoo Community Edition and want managed hosting with a professional deployment workflow, you need a third-party managed host that explicitly supports Community Edition. Not all of them do.
Hosting Odoo Community Edition: your real options
Option 1: Self-hosting on a VPS
You rent a virtual private server, install Odoo Community yourself, and manage everything from that point forward. This is the default path for many Community users because it has no hosting fee beyond the server cost.
The real cost is time. Setting up Odoo on a fresh VPS takes 20–40 hours for someone who hasn't done it before. Ongoing maintenance: security patches, SSL certificate renewals, Odoo version updates, database optimisation, backup management — typically runs 15–25 hours per month. When something breaks in production at 2am, you are the one who fixes it.
For developers who enjoy infrastructure work, self-hosting is a legitimate choice. For business owners who want to focus on running their business rather than running servers, it is a persistent operational burden.
Option 2: Managed hosting that supports Community Edition
A managed Odoo host takes care of the infrastructure so you don't have to. The hosting provider handles deployment, backups, SSL, security, monitoring, and support. You connect your code repository, push to deploy, and Odoo runs.
The critical thing to check: not every managed Odoo host supports Community Edition. Some providers only accept Enterprise deployments. Before signing up with any managed host, confirm explicitly that Community Edition is supported and that OCA modules and custom addons deploy cleanly on their platform.
Skysize supports both Odoo Community and Enterprise on the same managed infrastructure, same git-based deployment workflow, same ISO 27001 certified environment, same 99.95% uptime SLA. Community Edition runs at the same price as Enterprise. No Enterprise license required. See how Skysize Community hosting works →
Option 3: Upgrade to Enterprise
If the specific features you need are genuinely Enterprise-only and have no suitable OCA equivalent, upgrading is the right decision. Enterprise licensing is priced per user per month with regional pricing, check Odoo's official website for the current rate in your country.
Upgrading from Community to Enterprise is a well-documented process. Your data, customisations, and OCA modules migrate. The main consideration is that any Community-only OCA modules you rely on may need to be replaced with Enterprise equivalents or maintained as custom code post-upgrade.
How to decide what to do
Start with this question: what specific thing can I not do today that I need to do?
If the answer is a feature that exists in OCA, install the OCA module. If the answer is Studio and visual workflow building without code, evaluate Enterprise. If the answer is "Odoo.sh won't accept my Community instance," get a managed host that will. If the answer is "I'm spending too much time managing my own server," managed hosting solves that without any edition change.
Most Community Edition limitations have practical solutions that don't require upgrading to Enterprise. The key is to identify the specific gap rather than upgrading in response to a vague sense that Community is holding you back.
Community Edition is not a starter tier. It is a serious ERP platform that runs production workloads for businesses of all sizes. The limitations are real but specific. Understanding them clearly is the first step to making the right decision about what to do next.