Everything your Odoo project needs, from push to production

Built around the branch-per-environment workflow, with the operational tools that keep a production Odoo healthy for years.

Ship

From a git push to a running Odoo, with a staging copy of production in between.

  • GitHub push-to-deploy

    Connect a repository and every branch becomes a running Odoo with its own URL. Each push builds it again.

    • A webhook starts a build on every push
    • Build status reported on your GitHub commits
    • Rebuild or revert to an earlier build in one click

  • Development, staging, production

    Three stages, like you know them. Drag a branch from one stage to the next, or merge it, right from the Branches page.

    • Development builds get fresh demo data and run your tests
    • Staging tests on real data
    • Production keeps its database across releases

  • Staging copies of production

    Staging builds start from a neutralized copy of production: emails are caught and scheduled actions are off.

    • Test a release against yesterday's data
    • Restore any production backup into staging
    • Modules with a bumped version are updated

  • Odoo 14 to 20

    Community or Enterprise, on every version from 14.0 to 20.0, built from the official Odoo images.

    • Enterprise apps provided by the platform
    • Register your own subscription code inside Odoo
    • Test another major version on any development branch

  • Custom domains, automatic HTTPS

    Point your domain at any branch and a certificate is issued for it automatically. The dashboard shows each step.

    • Any stage, several domains per branch
    • Primary domain becomes Odoo's base URL
    • Extra platform addresses without DNS work

  • Import an existing database

    Moving in? Upload a backup from Odoo's database manager or a PostgreSQL dump into staging or production.

    • Large uploads in resumable chunks
    • Production is backed up first and put back if the import fails
    • Neutralized on staging

Operate

The tools you reach for when something needs a closer look, right in the browser.

  • Web shell and SSH

    A terminal inside the build, with Odoo shell, Python and SQL consoles. Or SSH in with the keys from your GitHub account.

    • Tabs and split panes in the browser
    • odoo-update and odoosh-restart included
    • SSH firewall for production and staging

  • Online editor

    Edit, commit and push from a code editor in the browser, with terminals and git next to your files.

    • Odoo and Enterprise sources read-only alongside
    • Restart Odoo or update a module in place
    • Consoles stay connected on restart

  • Logs for every phase

    Install, update, pip and server logs per build, plus slow SQL queries, streamed live to the dashboard.

    • Follow a build as it happens
    • Search and download logs
    • lnav, grep and ncdu in the shell

  • Monitoring

    CPU, memory, requests, response times, storage and emails graphed per branch, with releases marked on the timeline.

    • See what changed after a deploy
    • Built-in code profiler
    • Storage split by database, files and user data

  • Mail catcher

    Emails from development and staging never reach a real person. Read them in the Mails tab instead.

    • HTML, plain text or raw source
    • Production sends for real
    • SPF and DKIM checks for your own domain

  • Auto-sleep of idle environments

    Development and staging builds nobody visits go to sleep, and wake up on the next visit. Production never sleeps.

    • Wakes in about 10 to 30 seconds
    • Never while a shell or build is active
    • Delay adjustable per project

  • Collaborators and roles

    Invite your team as admins, testers or developers, with access to each stage that matches the role.

    • Audit logs of every action
    • Email and in-app notifications
    • Public build pages for your clients

Protect

Backups you can trust, alerts when production is down, and upgrades without surprises.

  • Daily backups, tested

    Production is backed up every day and kept for about three months. Each week the newest backup is restored as a test.

    • 7 daily, 4 weekly and 3 monthly backups
    • A backup before every module update, rolled back if it fails
    • Download a standard Odoo backup any time

  • Encrypted offsite copies

    When offsite storage is set up, backups are encrypted on the server, then copied to storage in another location. The provider only sees ciphertext.

    • Same retention as local backups
    • Upload status on every backup
    • Restore straight from the offsite copy

  • Uptime and status page

    Every server is checked once a minute. The project's Status page shows uptime over the past day, week and month.

    • Incident history with durations
    • Backup and offsite status at a glance
    • Deploys and restores don't count as downtime

  • Downtime alerts

    When production stops answering, you get a notification and an email, and another one when it's back.

    • Opened after 3 failed checks in a row
    • Each collaborator chooses their alerts
    • Counted per month for reporting

  • Upgrade assistant

    Test a major upgrade on staging with a copy of production, port your code, then upgrade production when ready.

    • OpenUpgrade for Community
    • Odoo's upgrade service for Enterprise
    • A banner six months before end of support

See it on your own repository

Every feature is included in every plan. You only choose the capacity.

Start now · Read the FAQ