Skip to Content
Features · Deployments and code

Push your Odoo code. We deploy it.

Push to GitHub, GitLab or Bitbucket and your branch deploys. Before each update, we copy your database. If anything fails, we put it back on its own.

Deploy on push Automatic rollback Environment variables Private submodules requirements.txt
skysize · builds OverviewBuildsSettings
Updatesuccess
production ·· 3m 12s
checkout 4s
requirements 38s
update 2m 21s
health check 9s
database copy kept for rollback ready
Connect your repository

From Git to a running Odoo

GitHub, GitLab and Bitbucket

Connect the one you use. Every push to a branch can build it. You don't have to move your code anywhere else.

WORKS ON Managed Your own server On-Premise Docs ↗

You choose what a push does

Each branch has its own setting. A push can make a new build with a fresh database, update the one that’s running, or do nothing at all.

WORKS ON Managed Your own server On-Premise Docs ↗

We can create the repository

Starting from zero? When you create a project, we can make the Git repository for you, under your own account.

WORKS ON Managed Your own server On-Premise Docs ↗

Start without Git, add it later

If you only need standard Odoo apps, create a project with no repository. The day you need custom code, add one. Your live database stays as it is.

WORKS ON Managed Your own server On-Premise Docs ↗

Stop a build

Pushed the wrong thing? Cancel a build that is waiting or running, right from the dashboard.

WORKS ON Managed Your own server On-Premise
Safety

Updates that can't leave you half done

Automatic rollback

Before your modules update, we copy the database. Then we check that Odoo starts and answers. If any step fails, we put back the copy and your old code. Your users keep working on the version that ran before.

WORKS ON Managed Your own server On-Premise Docs ↗

Only the modules you installed get updated

An update only touches the modules you already use. A new module in your code is never added behind your back. You add it in Odoo when you're ready.

WORKS ON Managed Your own server On-Premise Docs ↗

Skip the copy on very large databases

On a very big database, the copy takes most of the update time. Admins can turn it off. The dashboard records who did it and when, on every update that ran without it.

WORKS ON Managed Your own server On-Premise Docs ↗

Restart without a rebuild

Odoo acting strange? Restart it. Odoo starts again with fresh workers, and your code, database and files are left alone.

WORKS ON Managed Your own server On-Premise
Build configuration

Your code, built the way it needs

Environment variables for each environment

Set a different value for production, staging and development. Mark a value as sensitive and the dashboard hides it. To use a new value, restart the branch. There's no need for a full rebuild.

WORKS ON Managed Your own server On-Premise

Python packages from requirements.txt

Add a requirements.txt file to your code. We install what it lists on every deploy. The pip output has its own log, so you can see why a package failed.

WORKS ON Managed Your own server On-Premise Docs ↗

Public and private submodules

Pull modules in from other repositories, public or private. Each private one gets its own read-only key. If your Git account is connected, we add the key for you.

WORKS ON Managed Your own server On-Premise Docs ↗

Modules in subfolders

Keep your modules in folders if you like. Set the path once for the project, and every new branch starts with it.

WORKS ON Managed Your own server On-Premise Docs ↗

Community and Enterprise

Run Odoo Community or Odoo Enterprise, from version 16 to 19. On our cloud, the Enterprise code is ready for you.

WORKS ON Managed Your own server On-Premise Docs ↗

Your own Docker image

Need a system library, a font or a package pip can't install? Build your own image from the Odoo image and use it on your server.

WORKS ON Your own server On-Premise Docs ↗
Odoo builds

Odoo itself, kept up to date

Weekly Odoo updates

Every week, we rebuild Odoo from the newest official code for your version. Security and bug fixes reach you without any change to your code.

WORKS ON Managed Your own server On-Premise Docs ↗

On your own server, you decide when

On your own server or On-Premise, updates are up to you. You choose when production moves to a new Odoo build, and nothing changes until you do.

WORKS ON Your own server On-Premise

Automatic updates, every week

On our managed cloud, choose automatic, and we update production for you every week. You don't have to do a thing.

WORKS ON Managed Docs ↗

Or update by hand, within 30 days

Or choose manual, and you pick the moment. The dashboard shows which Odoo changes each update brings. If production goes 30 days without an update, we update it for you, so security fixes still reach it. We email you a week before.

WORKS ON Managed Docs ↗

A way back from a bad Odoo update

We check that Odoo answers on the new version before we switch. If it doesn't, we go back on our own. You can also pick an older build by hand.

WORKS ON Managed Docs ↗
Which product has what

Where each feature works

Deploy on push from GitHub, GitLab, Bitbucket
Automatic rollback on failed updates
Environment variables per environment
Private submodules
Odoo Enterprise code
Ready for you
Your Enterprise access
Your Enterprise access
New Odoo build every week
Who decides when production updates
Us every week, or you within 30 days
You
You
Your own Docker image
Built by former Odoo engineers ISO 27001 certified Support with a formal SLA
Questions

Frequently asked

Do new modules install on their own? +
No. New modules show up in Odoo’s Apps menu, and you install them when you want. After that, every update keeps them up to date.
What happens when an update fails? +
We put back the copy of your database we made before the update, and your old code with it. Odoo keeps running the version that worked.
Can I keep API keys out of my code? +
Yes. Put them in environment variables and mark them as sensitive. The dashboard hides the value, and developers only see the values for development.
Do I need Git to use Skysize? +
No. Start with standard Odoo and no repository. Add one later, and your live database stays as it is.
Which Odoo versions can I run? +
Odoo 16, 17, 18 and 19, in Community or Enterprise.

Want to see how your code would deploy?

Tell us how your repository is set up today. We'll show you how it would build and update on Skysize.