Loading page
Hosting, off-site backup storage, monitoring and the tooling that makes a custom module maintainable. Each one with the reason, because the reason is the useful part.
No affiliate links are configured
Odoo hosting
Odoo’s own hosting, with staging branches and backups handled for you. The default answer for an installation that does not want to run a server.
Where we would put a customer who wants Odoo managed and has no sysadmin.
No link — we are not in this programme
Cloud servers
A plain virtual server for an on-premise-style install you control. Cheaper than managed hosting and you own the patching.
For an installation with somebody in-house who is comfortable with Linux.
No link — we are not in this programme
Backup and recovery
Storage with its own credentials, somewhere the Odoo server cannot reach — which is the whole point of a backup copy.
The off-site copy the health check asks about. A backup on the same machine survives a mistake, not the machine.
No link — we are not in this programme
Monitoring
Tells you your Odoo is down, and tells you before a certificate expires rather than after.
Pairs with Database Health Monitor, which watches the inside rather than the outside.
No link — we are not in this programme
Development tools
Collects tracebacks from a running instance so a recurring error is a ticket rather than an anecdote.
For an installation with custom modules under active development.
No link — we are not in this programme
Off-site backups, health monitoring and audit logging are modules in our own catalogue. A hosting recommendation is worth having; so is knowing which parts you do not need to buy from somebody else.
Looking for written guidance instead? The insights section is where the longer explanations live.