Your EU based
Odoo hosting platform

Where your data is hosted

Your Odoo database, its filestore and every backup taken of it sit with a single infrastructure provider, Hetzner, in their German and Finnish datacenters. There is no hyperscaler behind that: no AWS, no Google Cloud, no Azure, and therefore no US parent company holding your production data.

This matters more than the usual "EU region available" claim. Most platforms in this market are management layers on top of a hyperscaler, which means an EU region on paper and a US corporate chain underneath it. Shoovels runs on European infrastructure end to end.

The audit trail

The project audit log covers the whole project, production and every staging copy, in one trail. Each entry names who acted, what changed and when, and it can be filtered down to a person, an action or a period when you are answering a specific question.

It matters most in the arrangement where one company holds access to another company's data. Trust carries that for a while. A written record carries it permanently, and it protects the person with access as much as the person whose data it is.

It also handles the ordinary version of the same problem. Someone left in March and nobody is sure what they still had. A permission was granted for one afternoon and never taken back. The answer is written down either way.

Backups, retention and recovery

Every environment is backed up automatically every day, production and staging alike, and you can take your own at any moment.

Production backups are kept with no time limit, for as long as the project exists. Staging backups are retained for one month, which is the useful life of a test copy and keeps you from paying storage on copies nobody will ever restore.

On top of the daily backups, restore points run throughout the day, so recovery is to a moment you choose rather than to last night. A backup is taken automatically before any restore runs, so the recovery itself is reversible.

Who else is on your server

No other Shoovels customer runs on your server. A project is provisioned onto its own machine and stays there: production and its staging copies live together, and nobody else's Odoo joins them.

By default that machine is a Hetzner cloud server dedicated to your project. If a compliance review asks for single tenancy down to the hardware, or your workload needs consistent performance, you can move to Hetzner high performance dedicated hardware for €50 more per worker per month.

Access control, and who decides

Access is granted per project, not per instance. Everyone on a project's list can open production and every staging copy under it. Three roles carry different weight:

• Viewer sees instances, metrics and logs, and changes nothing.
• User operates: backups, Login-As, staging rebuilds, instance administration.
• Admin adds the ability to invite people and manage their roles.

No project role touches money. Creating a project, changing resources and cancelling are organization-level actions, held separately on purpose so that the person who can restart an instance is not automatically the person who can change your bill.

Taking your data out, and deletion

You can package and download a copy of any instance whenever you want, with or without the filestore, and neutralised if it is going somewhere outside production. There is no export request and no waiting on us.

When a project is cancelled it ends at the period end, a snapshot is taken, and the instance is deprovisioned fourteen days later after a warning. That window is a safety margin against a cancellation someone regrets, not a retention claim on your data.

Subprocessors

One infrastructure subprocessor, Hetzner, handles your Odoo databases, filestores and backups. Alongside it a small number of service subprocessors handle payments, transactional email and error monitoring. They are named individually in the processing agreement, with what each one receives.