Deploy Odoo on Hetzner

Why Hetzner for Odoo

Cheapest EU compute

Hetzner's CX shared-vCPU and CCX dedicated-vCPU servers are priced in euros and consistently undercut the major hyperscalers for equivalent CPU and RAM. Because CloudWady is BYOC, that euro price is exactly what you pay — the invoice is between you and Hetzner, and CloudWady never sits in the middle of the cloud bill.

Strong EU data residency

Hetzner runs data centres in Germany (Falkenstein, Nuremberg) and Finland (Helsinki), so your Odoo database and filestore stay on EU soil under EU jurisdiction. For partners with GDPR obligations, that is a clean residency story — and the CloudWady control plane that orchestrates the deploy is operated from Germany by syscoon GmbH.

Repo to live in ~10 minutes

Connect your Hetzner account, point CloudWady at your Git repository, and CloudWady provisions the server, installs Odoo, pulls your addons, and brings the instance up — typically in around ten minutes for a fresh small instance. There's no infrastructure to wire by hand.

What you control

Because the server lives in your Hetzner project, you keep the things a managed platform usually hides. The box is yours; CloudWady is the control plane on top of it.

• The Hetzner account and billing — the server is created in your project and the invoice comes from Hetzner directly, at Hetzner's price.
• The region — pick Falkenstein, Nuremberg or Helsinki to match your data-residency needs.
• SSH and the server itself — root on the box, terminal access, and full visibility into the OS.
• The database and filestore — your Postgres data and attachments stay on infrastructure you own.
• Backups — stored in your chosen object store (for example Hetzner Storage Box) under keys you hold.

Typical Hetzner sizing for Odoo

Odoo's footprint depends mostly on concurrent users and the number of background workers. As a starting point, these CX/CCX shapes map cleanly to common Odoo workloads — scale up later from the dashboard without rebuilding.

• Small — a CX-class server (roughly 2 vCPU / 4–8 GB RAM) suits a single small tenant, light user counts, or a staging environment.
• Medium — a CX/CCX server (roughly 4 vCPU / 16 GB RAM) handles a busier production tenant with several workers and a moderate user base.
• Large — a dedicated-vCPU CCX server (8+ vCPU / 32 GB RAM and up) is the right call for heavy concurrency, large filestores, or consolidating multiple tenants on one box.

These are guidelines, not hard limits — sizing is a slider, and CloudWady makes resizing a dashboard action rather than a migration.

Keep reading

• Back to the BYOC hub — how bring-your-own-cloud works across Hetzner, DigitalOcean, AWS and your existing servers.
• CloudWady vs Odoo.sh — the full pricing and capability comparison, with the BYOC cost math laid out.