Push your repo. Get a live Odoo. Keep the keys.
Connect a Git repo, pick a branch, and CloudWady builds and deploys it on your own cloud in minutes — with SSH and a real shell on servers you own.
Your repo is the source of truth
Point CloudWady at the Git repository you already use. It clones the branch, installs the addons declared in your manifests, and brings Odoo up against your chosen database. Custom modules, OCA dependencies, and pinned versions all come along — copied verbatim, no rewrites.
Push a commit and redeploy from the dashboard. The build runs, the new code goes live, and the previous state stays recorded so you can step back if a change misbehaves. The repo stays yours; CloudWady only reads what it needs to build and deploy.
Dev, staging, and prod — with a way back
Promote a branch from development to staging to production along the same pipeline, and roll a bad deploy back without rebuilding from scratch.
Development
Spin up a development instance from any branch to test work-in-progress code against real data, without touching what your users are on.
Staging
Promote to a staging environment that mirrors production to validate a release end-to-end before anyone in production sees it.
Production
Ship the validated branch to production on the same pipeline. No copy-paste between consoles, no hand-built release steps to forget.
Rollback
If a deploy goes wrong, roll back to the previous known-good state from the dashboard. The bad change is reversible, not a fire drill.
A real server, not a sandbox
Because the instance runs on your own cloud, you get the access you'd expect from a machine you own — SSH, a code editor, and a terminal, not a curated subset of them.
SSH and shell
Open a terminal on the server straight from the dashboard, or connect over SSH directly. Tail logs, run the Odoo shell, inspect the database — the machine answers to you because it's yours.
Code editor
Edit configuration and module files in-browser when you need a quick fix, then commit it back to the repo. The dashboard surfaces the files instead of hiding them behind an opaque editor.
Servers you own
The instance lives in your cloud account, in the region you chose. You're not borrowing capacity on shared infrastructure — you have full reach into the box, and you can leave with everything on it.
Stop maintaining deployment scripts
The work between "code in a repo" and "Odoo on a public URL" is the part nobody wants to own: writing the Docker setup, configuring Nginx, issuing and renewing SSL certificates, wiring backups, restarting workers. CloudWady handles that plumbing so you don't keep a pile of bespoke shell scripts alive across projects.
No manual Docker, Nginx, or SSL
The container build, reverse proxy, and TLS certificates are provisioned and renewed automatically when the instance is deployed. You don't hand-edit an Nginx config or babysit a cert that expired over a weekend — it's set up once and kept current.
You still own the box
Automating the plumbing doesn't lock you out of it. Because everything runs on your own server, the generated config, the containers, and the certificates are all right there for you to inspect over SSH. The difference is you no longer have to build and maintain them by hand.
Ship from your repo today
Connect a repository, pick a branch, and watch CloudWady take it to a live Odoo instance on your own cloud — with the shell access you'd expect from a server you own.