Skip to main content
Ready to deploy? Start Free Trial
The model

What "Bring Your Own Cloud" actually means

Most Odoo hosting bundles the platform and the servers into one bill. You rent both from the same vendor, and you never see the underlying cloud cost. BYOC splits those two things apart.

You open an account with a cloud provider — Hetzner, AWS, Google Cloud, or DigitalOcean — and connect it to CloudWady. From there, CloudWady provisions the server, installs Odoo, wires up backups and SSL, and keeps it running. The machines live in your account, under your name, in the region you chose. CloudWady is the control plane on top; your cloud provider is the landlord underneath.

The cloud bill comes from your provider

Because the resources sit in your account, your provider charges you directly for them — the same published per-hour and per-gigabyte rates anyone else pays. CloudWady never resells compute and never adds a margin on top of it. You pay one flat CloudWady platform fee for the deployment and management layer, and your cloud invoice arrives straight from the provider.

You keep the relationship

If you ever stop using CloudWady, the servers, the database, the filestore, and the cloud account stay exactly where they are — they were always yours. The data lives in the region you picked, operated under EU rules by syscoon GmbH in Germany when you choose an EU region. Nothing about the move is one-way.

How it works

Repo to live, in minutes

Why BYOC

Why it beats a fully managed host

Compared with renting both platform and servers from one vendor — the Odoo.sh model — BYOC changes three things that matter.

Get started

Deploy Odoo on your own cloud

Connect a cloud account, pick a region, and let CloudWady take your repo to a live Odoo instance in minutes — with the cloud bill coming straight from your provider, at their rates.