Do not buy Odoo hosting on price alone.
Use this checklist to turn vague “managed” claims into testable deliverables. Every serious Odoo host should answer these questions in writing. If they cannot, you are buying hope, not operations.
How to use this checklist
The direct answer: score providers on evidence — architecture diagrams, backup retention, restore logs, patch cadence, upgrade case studies — not on superlatives. Reject any offer that refuses a restore test or database export before contract signature.
This checklist applies to managed Community providers, specialist Odoo hosts, and internal teams evaluating whether to self-host. For DIY, you are the provider; every unanswered question is unpaid labour.
Infrastructure and security
- Edition and licence: Community or properly licensed Enterprise? Who verifies user counts?
- Region and data residency: Where do PostgreSQL and filestore physically live?
- HTTPS: Who renews certificates and how quickly?
- Isolation: Shared or dedicated resources? Noisy-neighbour risk?
- Access: Who holds root? Can you SSH or only use a portal?
- Security patching: OS, PostgreSQL, reverse proxy, Python dependencies — cadence and staging?
Backups, restores and portability
- Backup scope: PostgreSQL and matching filestore every time?
- Retention: Daily, weekly, monthly counts and off-server storage?
- Restore test: When was the last successful full restore drill?
- Export rights: Can you download a standard Odoo backup yourself?
- Exit: Notice period, DNS help, and data handover on termination?
Odoo’s deployment documentation recommends daily remote backups of database and filestore. Treat any provider that backs up only the database as incomplete. Read Odoo Community backup and restore to understand why.
Modules, staging and upgrades
- Custom modules: Supported? Who installs and reviews them?
- Staging: Is there a test copy refreshed from production?
- Major upgrades: Who tests custom and third-party addons?
- Odoo version policy: How fast do security fixes land?
- Mail and integrations: SMTP, API endpoints, IP allowlists — who maintains them?
Separate platform support from functional consulting. Configuration, migration, and bespoke development should have their own statement of work. See implementing Odoo without a partner for what you can still do yourself.
Pricing and accountability
- All-in pricing: Users, storage, backups, staging, upgrades — what is extra?
- Incident response: Hours, channels, and escalation when production is down?
- SLA: Measured uptime or best-effort language?
- Account ownership: Are admin accounts in your email domain?
Flat-fee Community hosting can simplify user growth economics; verify it still includes the backup and upgrade scope you need. Compare with the true cost of cheap Odoo hosting.
FAQ
What is the most important question to ask an Odoo host?
Show me a recent successful restore of PostgreSQL and filestore into an isolated environment.
Should I accept shared hosting for Odoo?
Only if you understand resource isolation, backup boundaries, and upgrade coordination with other tenants.
Do I need a partner and a host?
Not always. Simple Community projects can use managed hosting plus internal configuration. Complex migration or compliance may still need specialists.
Continue the hosting decision
Run the checklist before you sign.
Odin publishes flat-fee Community hosting with staging, backups, HTTPS and upgrades. Test our answers against this list.