Managed Odoo hosting
Odoo you can change without holding your breath.
Every customer gets their own Odoo, their own database, and a staging copy they can break freely — cloned from production and stripped of anything that could email a real customer.
Odoo 16 · 17 · 18 · 19 — Community and Enterprise
own storage volume
never shared or oversold
restic snapshots
websockets configured
Environments
Three copies. One of them is allowed to break.
Production, staging and development, each a real stack with its own database, its own domain and its own resources.
Staging starts as a copy of production
Real data, real volume of records, the same modules — because a test on an empty database tells you nothing about a migration.
Then it is neutralized before it ever starts
Outgoing and incoming mail servers deleted, queued mail cancelled, every scheduled action disabled, payment providers switched off. Odoo stays stopped until that is verified.
Refresh it whenever it drifts
One click re-clones from production and neutralizes again. Nothing in staging is precious.
Why the neutralization matters
The failure everyone has seen once: a staging copy quietly sends three months of invoice reminders to real customers overnight. That cannot happen here — a staging instance has nothing to send with, and no cron left running to send it.
Your code
Your addons come from Git, not from a support ticket.
Link a repository once. Private repos authenticate with a token that is stored server-side and never shown again.
A branch per environment
Creating staging forks production's branch, so staging runs staging code. Merge when it works; the environments never quietly share a checkout.
Update on your schedule
Pull the latest commit and restart Odoo from the panel. Commit history for every linked repository is right there next to the instance it runs on.
Enterprise-ready
Odoo Enterprise, OCA modules and your own private repositories run side by side on the same instance.
Backups
Backed up to two places, in two hands.
Database and filestore together, encrypted before they leave the server, written to every destination you configure.
Amazon S3
Or any S3-compatible store — Wasabi, Backblaze B2, your own MinIO.
Google Drive
Including a Drive you own, so one copy is somewhere we cannot reach.
SFTP
Any server you have SSH access to, keyed and unattended.
Each customer has their own encryption key
One customer's key cannot decrypt another's snapshots, and a copy of yours belongs off this server. Retention is set per plan, and old snapshots expire on their own.
Monitoring
You hear about it before your users do.
CPU, memory, disk and database connections are sampled continuously, whether or not anyone has the panel open.
Email when something crosses 80%
A metric has to stay over the line for several readings before it alerts, and stays quiet afterwards until it recovers — so the alerts remain worth reading.
Logs without SSH
Odoo's own log and the container's output, per environment, in the panel. When something is wrong the log is the first thing you want, not the last thing you find.
Access
Support that doesn't start with "what's your password?"
Open a session as any user of the instance, see exactly what they see, fix it, leave.
No password is asked for, or changed
The instance is handed a signed link that names one user, lasts sixty seconds, and works exactly once. Nobody's credentials move, and nothing is reset behind their back.
Every use is on the record
Who opened a session, as whom, from where, and when — kept inside your own database, along with every attempt that was refused.
Plans
One fee for the management. The server stays yours.
You open the cloud account and pay your provider directly, at their price. We add nothing to it.
One Odoo you rely on, and somewhere safe to try changes first.
- Instances2
- Staging environmentIncluded
- Git addonsYes
- Backup retention14 days
- Monitoring and alertsYes
Several environments, several servers, and code moving between them.
- InstancesUnlimited
- Staging + developmentUnlimited
- ServersUnlimited
- Backup destinationsS3 · Drive · SFTP
- Backup retention30 days
Server billed by your cloud provider · Migration and Odoo Enterprise licensing quoted separately
Questions
Before you ask.
Can you move our existing Odoo across?
Yes — a database dump and filestore is all we need. We restore it into a staging environment first so you can check it before anything points at it.
Which Odoo versions do you run?
16, 17, 18 and 19, Community or Enterprise. Each instance runs its own version, so one customer upgrading does not move anyone else.
Do we get our data if we leave?
Always, and without asking. A backup is a standard Odoo database dump plus the filestore — restorable on any Odoo, including your own laptop.
Who can log into our Odoo?
Your users, with their own passwords. We can open an audited support session as one of your users; every such session is recorded inside your database where you can read it.
What happens when an instance runs out of memory?
You get an email before it does. Each instance has hard memory and CPU limits, so a runaway report on one instance cannot take down another.
Can we keep a backup copy ourselves?
Yes. Point one destination at your own Google Drive, S3 bucket or SFTP server and every backup lands there too.
Get started
Let's look at your Odoo.
Tell us the version you run, roughly how many users, and what hurts. We will tell you what we would do about it.