Odoo Deployment
Run Odoo anywhere, with backups that restore.
We deploy Odoo on Odoo.sh, a cloud VPS or servers in your own building, and set it up the way production needs: Docker images, a tuned PostgreSQL, Nginx with TLS, sized workers, daily off-site backups with tested restores, and alerts on disk, memory and failed jobs.
- Odoo.sh
- Cloud VPS
- On-premise
- Docker
- Tested restores
- Server regions near your users
- Odoo versions we deploy
- Off-site backups of database and files
- Reply time on business days
The production stack
Six things production Odoo cannot skip.
A fresh install is not a production system. This is the checklist we work through on every server, whether it runs on Odoo.sh, AWS or a rack in your office.
Docker images
Odoo, your custom modules and pinned Python dependencies built into one image, so staging and production run exactly the same code.
PostgreSQL tuning
Memory, connections and autovacuum set for your database size, with slow-query logging switched on from day one.
Workers, Nginx and TLS
Odoo workers and memory limits sized to your users, Nginx in front for websockets and caching, and TLS certificates that renew themselves.
Backups and tested restores
Nightly database and filestore backups, encrypted and kept off-site, then restored to a test server on a schedule, because an untested backup is not a backup.
Monitoring and alerts
Uptime checks, disk, CPU and memory, failed scheduled actions and certificate expiry, with alerts sent to your team and ours.
Hardening and access
Firewall rules, key-only SSH, the database manager locked down, a strong master password and staff access over VPN where needed.
Pick the right home
Odoo.sh, cloud or on-premise: we'll tell you which fits.
Odoo.sh is excellent when you run Enterprise and want Odoo to manage the platform, with staging branches built in, and we recommend it when it fits. A cloud VPS gives you root access, any system package and room for Odoo Community. On-premise suits sites with unreliable internet or data that must stay in the building. We compare all three against your users, modules and budget, in writing.
- Odoo.sh for Enterprise on a managed platform
- Cloud VPS for full control and Community
- On-premise when data must stay on site
- A written comparison before you commit
Size
Users, apps, database and filestore measured first.
Build
Image, database and proxy set up on staging.
Cut over
A rehearsed switch with a rollback point ready.
Watch
Monitoring and backup checks from day one.
Typical jobs
Where a deployment project usually starts.
Moving off Odoo Online
Custom modules and third-party apps need Odoo.sh or your own server. We move the database and files, set up the new host and switch your domain in a planned window.
Fixing a fragile self-hosted server
An old install with no backups, no TLS and a disk close to full: we image it, stabilize it, then rebuild it cleanly on Docker with monitoring.
On-premise for a factory
A local server keeps production running when the internet drops, with encrypted backups copied off-site every night.
By industry
Hosting choices shaped by where your people work.
Connectivity, data sensitivity and peak loads differ by sector, and they decide where Odoo should run.
- ManufacturingOn-site or hybrid servers for shop floors with weak internet.
- Retail & E-commerceHeadroom for sale days, and a POS that keeps selling offline.
- Hospitals & ClinicsRestricted access and encrypted backups for patient records.
- PharmaceuticalsSeparate staging and strict change control for validated systems.
- Freight & LogisticsServers close to teams spread across ports and time zones.
- Professional ServicesLean cloud hosting sized for small teams that grow.
- EducationCapacity planned ahead of enrollment and term billing.
- HotelsStable POS for outlets and restaurants across properties.
How we deploy
From sizing to a monitored go-live.
1. Assess
We look at users, apps, custom modules, database size and where your people sit.
2. Recommend
You get a written comparison of Odoo.sh, cloud and on-premise with the monthly running cost of each.
3. Build staging
The full stack goes up on staging first, and your team tests it with a copy of real data.
4. Cut over
A rehearsed switch in a quiet window, with the old server kept as a rollback point.
5. Run and review
Backups, restore tests and alerts run from day one, and we review capacity as usage grows.
Toolbox
The infrastructure under your Odoo.
- Odoo.sh
- Docker
- Docker Compose
- PostgreSQL
- Nginx
- Let's Encrypt
- Debian
- AWS
- DigitalOcean
- Terraform
- Prometheus
- Grafana
- restic
- WireGuard
Our terms
Commitments, not uptime slogans.
We do not quote uptime percentages we cannot guarantee. These are the things every deployment we manage includes, rather than sells as extras.
Book a hosting review- Restores on a schedule, not assumed
- Certificates on every domain, auto-renewed
- Managed hosting fee, scaled to users and data
- Support in English and Thai
- Ways to host: Odoo.sh, cloud, on-premise
FAQ
Questions clients ask first
Should we host Odoo on Odoo.sh, a cloud VPS or on-premise?
Odoo.sh suits companies on Odoo Enterprise that want Odoo to run the platform, with staging branches built in. A cloud VPS gives full control, any system package and the option of Odoo Community. On-premise makes sense when the internet is unreliable or data must stay on site, and we compare all three for your case in writing.
Can we run Odoo Community on Odoo.sh?
No. Odoo.sh is only available with an Odoo Enterprise subscription. Community runs well on a cloud VPS or your own server, and we deploy it there with the same Docker setup, backups and monitoring.
Can we install custom modules on Odoo Online?
No. Odoo Online, the SaaS edition, does not accept custom Python modules or third-party apps; changes are limited to what Studio can do. If you need custom code, we move your database to Odoo.sh or your own server with all your data intact.
How do you handle Odoo backups?
The database and filestore are backed up daily, encrypted and kept away from the production server. We restore a recent backup to a test server on a schedule and check that users can log in and reports run, because an untested backup is not a backup.
How big a server does Odoo need?
It depends on concurrent users, apps, custom modules and database size rather than on named users. Odoo's own guideline is roughly one worker for every six concurrent users, and we size CPU, memory and PostgreSQL from that, then adjust from monitoring data as usage grows.
Can you move our existing Odoo to a new server?
Yes. We copy the database and filestore to the new host, test everything on staging, then switch over in a planned window. The old server stays untouched as a rollback point until you sign off.
Get started
Tell us where Odoo runs today.
Share your edition, user count, custom modules and current host. We reply within one business day, and after a short call you get a written hosting recommendation with the running cost of each option.
- Reply within one business day
- Written comparison of hosting options
- Backups, TLS and monitoring included
Prefer to talk first? Call us or WhatsApp us.