What’s the best hosting option for your Odoo?

Why do you need to focus on your needs first?

The right hosting depends on your overall needs and how you use Odoo. Before choosing any Odoo hosting option, you need to be able to answer five questions.

Do you have specific compliance needs?

• Sensitive information handling, like medical records or government-related information

• ISO certifications such as ISO 27001 and ISO 22301 that define system security and business continuity

• Data stored in specific countries or, on the contrary, data should not travel in certain countries.

How much will you customise Odoo? 

• Standard apps only

• A few custom modules

• Or a heavily customised database with its own apps and integrations.

How heavy is your load? 

• How many users must be working at the same time

• Transaction volumes (e.g.: Orders, Invoices, deliveries etc.)

• Size of data syncs and reporting queries.

Who will run it? 

• In-house IT or DevOps team capable of taking on the work

• External provider to manage and simplify hosting for you

• Granular control over hosting but managed by outside experts.

What are your backup and recovery requirements?

• Backup requirements (Hourly, Daily, Weekly)

• Internal or external recovery process.

After this assessment, it will be much easier to select the best solution for you.

Comparing Odoo hosting options side-by-side

We compared the top three Odoo hosting options (Odoo.sh, on-premise, and Shoovels managed hosting) feature by feature so you can make the best decision.

Why Odoo.sh is a great fit for basic needs?

Odoo.sh is Odoo’s own cloud platform, built for companies that want to customise Odoo without managing servers themselves. Odoo runs and monitors the infrastructure, while your developers push custom code through GitHub and changes are tested and deployed automatically.

Pros

• Managed infrastructure: Odoo runs and monitors the servers and configures mail and DNS

• GitHub integration for CI/CD: Every commit is automatically tested before deployment

• Staging with production data: Staging branches are built from a copy of the production database

• Developer tools: Includes Shell and SSH access, live logs and unlimited development branches

• Daily backups: Production is backed up daily to three data centres (not EU only), and backups are kept for up to three months

• Usage-based pricing: Hosting is billed based on worker numbers, GB of storage and number of stagings

• Certification: ISO 27001.

Cons

• Shared servers by default: Projects run on servers shared with other Odoo.sh customers, and a dedicated server costs an extra 400€/month

• Limited self-service: Only some features are available

• Rollback: It is possible to roll back to a previous release but the process is cumbersome and might be buggy

• Fixed hosting region: The region is set when the project is created and can’t be changed, and Odoo doesn’t contractually guarantee the provider or location

• Restricted server configuration: System packages and PostgreSQL extensions can’t be installed

• Time limits on scheduled actions: Scheduled actions that exceed the time limit are stopped and can be disabled

• Staging retention: Staging builds aren’t backed up and are removed after 30 days

• Legacy support surcharge: Odoo adds a 25% surcharge once an Odoo version is 3.5 years old.

What is the key benefit of on-premise hosting?

With on-premise hosting, your IT team runs Odoo on servers you control, either in your building or in a private or public cloud. Your team is responsible for installation, backups, monitoring and deployments.

Pros

• Full control: You choose the hardware, configuration and data location

• Scalability: Hardware and workers can be added as needed, and reports can run on a database replica

• Data sovereignty: Data stays on infrastructure you control

• Local integrations: Odoo can connect directly to local hardware and legacy systems on your network

• Development flexibility: Any system dependency can be installed, with as many staging instances as needed

• Edition support: On-premise works with both Odoo Community and Enterprise.

Cons

• Technical responsibility: Your team runs, patches, secures the infrastructure and is responsible for certification (if you want to have one)

• Features you need to build yourself: Log in as any user, recovery to any point in time, self-service and rollback after a bad release

• Monitoring: Server monitoring and alerting have to be set up and run in-house

• Backups: You define your policy. Standard Odoo backups are slow on large databases, so dedicated backup tools are needed

• Staffing: Setup, updates and incident response require in-house DevOps staff

• Total cost: Costs include hardware, staff time, maintenance and tooling.

Why Shoovels by much. is the easiest solution?

Shoovels is a managed Odoo hosting platform run fully in-house by much. Consulting. Every project runs on its own server in EU data centres. We take care of the servers, and your team manages deployments, staging, backups and logs from one self-service dashboard. We can also help you with this, if needed: basically, you decide how much involvement you want to have.

Pros

• Fully managed: Updates, monitoring and maintenance are handled in-house by the engineers who build and support your Odoo

• EU-only residency: All data is hosted and processed in EU data centres, with one European infrastructure subprocessor and no US cloud provider in the chain

• No shared servers: Each project runs on its own container, and no other customer’s Odoo runs on it

• Recovery to any point in time: Restore points run throughout the day, so you can restore your system to an exact moment instead of last night’s backup

• Rollback window: One-click rollback covers the last three releases

• Backup retention: Every environment is backed up daily and on demand, and production backups are kept for as long as the project exists

• Log in as any user: You can switch into any user’s view from the dashboard to reproduce bugs, test permissions, and troubleshoot issues

• Deploys with live status and rollback: Code is deployed from GitHub with live pipeline status, failed deployments roll back automatically, and any of the last three releases can be restored in one click

• One-click management: You can start/stop and maintain instances, toggle maintenance mode, view logs, and run system tasks from the dashboard

• Audit trail: A project-wide log records who changed what and when, across production and every staging copy

• Role-based access rights: Roles (viewer, user, admin) are set per project, and billing changes are restricted to the organisation level

• Data exports on demand: You can download a copy of any instance at any time, with or without the filestore

• Edition support: You can bring your Odoo Enterprise key or run Odoo Community

• Certification: ISO 27001.

Cons

• Single region: Data is hosted in the EU only, on Hetzner servers in Germany and Finland. No other regions are offered

• Staging backup retention: Staging backups are kept for one month.

→ Talk to our experts about Shoovels by much.

So which hosting option is the best for your Odoo?

This is a key summary based on needs:

Odoo hosting FAQs

What is the difference between shared and dedicated Odoo hosting?

With shared hosting, your Odoo runs on the same servers as other customers’ databases. With dedicated hosting, the server runs only your Odoo. Odoo.sh projects are shared by default, and a dedicated server costs an extra 400€/month. Shoovels runs every project on its own server.

Can I switch Odoo hosting options later?

Yes. Your database and file store can be exported and restored on another platform, whether you’re moving from Odoo.sh, on-premise, or Shoovels. Testing the move on a staging copy first keeps downtime to a minimum.