Test on a copy of production before your users see it
Every project gets a live Odoo and test copies. Staging uses your real data, but email and scheduled actions are turned off first.
Three kinds of environment
Production
Your live Odoo. It's always on, it's never cleaned up, and it's backed up every day. One per project.
Staging
A copy of your production data, running the code of your staging branch. It stays up for as long as you need it. Rebuild it to get fresh data from production.
Development
A fresh Odoo with demo data, built from any branch you push. It's removed 24 hours after the build, so you can make as many as you like.
One branch, one environment
Each Git branch maps to its own environment, with its own database and its own settings. Changing a branch type takes one click.
Staging you can trust
Email and scheduled actions off, before Odoo starts
A copy of production could email your customers or sync your bank. So we turn off mail servers, scheduled actions and live connections before staging starts for the first time. If that fails, staging doesn't start.
Your branch, tested on real data
Staging copies production data, then runs your staging branch's code and updates its modules. If the code can't be applied, the build fails and nothing breaks.
Staging without Git
No custom code? Click New staging to get a copy of production. Try a new app, an import or a settings change there first.
See the next Odoo update early
Staging always runs the newest Odoo build. So it shows you what production will look like after its next update.
Development for every branch
A build for every push
Push a feature branch and get a fresh Odoo to try it on. Demo data is loaded, so there's something to click on.
Choose what installs and what’s tested
Install every module in your code, or only the ones you list. Run tests by tag, or just for the modules you picked.
Cleaned up for you
Development builds go away 24 hours after they're built. Nothing piles up.
Settings for each environment
Each environment can have its own env vars. Keys for live and test can be kept apart.
Access for contractors
Give a contractor the Developer role. They get full control of test branches, and no access to your live Odoo.
Addresses and domains
An address for every environment
Production, staging and development each get their own web address the moment they're built. You can share a link to test with right away.
Your own domain, with HTTPS
Add your domain to production. We get the HTTPS certificate and renew it for you. You can add more than one domain, and changes apply without a redeploy.
A DNS check when you add a domain
When you add a domain, we check its DNS first. If the record is wrong, you see what's wrong and what the record should be.
Cloudflare in front of your Odoo
Traffic goes through Cloudflare by default, for protection from attacks and faster loading far away. On paid plans, you can turn it off.
Every branch under your domain
On your own server, add one DNS record. Then every branch gets a name under your domain, with its own certificate made on your server.
Where each feature works
Frequently asked
Can staging send emails to my customers?
How many staging environments can I have?
Is my development data kept?
Can I use my root domain, like mycompany.com?
Can staging have its own domain?
Want to see how you'd test before going live?
Tell us how your team works today. We'll show you how production, staging and development would fit.