Everything your Odoo needs, from push to production

Deploy

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

• Pull request previews

  Every pull request gets its own development environment on a fresh database, with a GitHub check and a comment linking to it.

  • Pull requests from forks wait for an admin's approval
  • Fork previews isolated from your team's environments
  • Removed with its database when the pull request closes

• 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

• Apps catalog of OCA modules

  Search thousands of the Odoo Community Association's modules for your Odoo version and add them to a development branch without touching git.

  • One commit adds the modules and their Python requirements
  • The OCA repositories they depend on are offered too
  • Test on development, then merge to production

• 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? Bring a backup from Odoo.sh, Odoo Online or any host: upload it, paste a download link, or fetch it from a running Odoo's database manager.

  • The Odoo version and custom modules are checked first
  • Production is backed up first and put back if the import fails
  • Neutralized on staging

Your own server

Keep Odoo on a server you own, and let us monitor, back up, secure and install it.

• Link any server in one command

  Run one command as root on your server, at AWS, Hetzner, DigitalOcean, Linode or in your own rack, and it shows up in the dashboard with the Odoo instances it runs.

  • A restricted key that only runs our small, readable agent
  • The server's SSH host key is pinned on the first connection
  • Finds Odoo run by systemd, init scripts or Docker

• Install Odoo on your server

  Odoo 17, 18, 19 or 20, Community or Enterprise, in a few clicks. The installer prepares the server by itself and adds your domain with HTTPS as soon as its DNS points there.

  • Native or Docker, picked for your server
  • Swap, disk clean-up and free ports handled for you
  • Followed live, refunded in full if it fails

• Server monitoring and alerts

  Every 5 minutes: load, memory, disks, each Odoo instance and each domain with its certificate. You're alerted when something goes down or fills up.

  • Instance down, disk over 85% and certificate expiry alerts
  • Restart, stop and start Odoo from the dashboard
  • Live logs of every instance

• Backups of your server's Odoo

  Daily backups of each database in Odoo's own zip format, checked, copied offsite encrypted, and restored as a test every week.

  • Configuration and custom addons too, secrets redacted
  • Stored off the server, downloadable any time
  • A failed backup or restore test alerts you

• Security audit and guided fixes

  A daily, read-only audit of the server and each Odoo: open database manager, exposed ports, SSH settings, pending updates, HTTPS. Graded from A to F.

  • How to fix each finding, with the commands
  • Guided fixes with a dry run and automatic rollback
  • Alerts for new critical findings

• Recorded web terminal

  A root shell on your server, in the browser, for its owner only: a fresh sign-in, plus your two-factor code when two-factor is on.

  • Every session recorded and kept 90 days
  • One session at a time, closed when idle
  • Turn it off, or never install it

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

• Jupyter notebooks

  Open JupyterLab on any build with env ready to use, like odoo shell. Nothing runs until you open one.

  • Every cell recorded like a shell command
  • Saved with the build
  • Production notebooks for project admins only

• 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

• Explain this failure, with AI

  A failed build, restore, backup or Odoo install gets a plain-English explanation from Claude: what failed, the likely cause and the steps to fix it.

  • Secrets removed from the log before anything is sent
  • A short summary in failure emails, when turned on
  • Still stuck? Hand it to support in one click

• 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

• Performance advisor

  A daily score with prioritized recommendations for production: slow requests and SQL, missing indexes, scheduled actions, workers and memory.

  • Index and clean-up suggestions you can apply
  • Worker sizing with the math shown
  • Read-only analysis with strict time limits

• 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

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

• A private network per environment

  Production, staging, each development branch and each pull request preview run on separate private networks, each stage with its own database role.

  • A fork's preview can't reach production or staging
  • Builds can't reach the platform's internal services
  • Locked-down containers with process limits

• 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

  A readiness report of every installed module, a test upgrade on a copy of production with smoke checks, then production when you're ready.

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

• Maintenance windows

  Choose when production may restart. Pushes can wait for the window, and platform rebuilds and restarts always do, then run in order.

  • Deploy now or hold until the window
  • Your time zone, Asia/Dubai by default
  • Downtime inside the window isn't an incident

• Two-factor sign-in

  Authenticator-app codes with one-time recovery codes for password accounts, and a platform switch that makes two-factor mandatory.

  • Works with any authenticator app
  • The secret is never sent to a QR service
  • An email on every change to your sign-in

• Public status page

  Platform health per region, with 90 days of uptime, incident history, email updates and an Atom feed.

  • Double opt-in email subscriptions
  • Follow the regions and components you care about
  • Aggregates only, never one customer's data

Teams & partners

Your company, your clients and your partners, each with the access and the reports that fit them.

• Team accounts for companies

  Create an organization, invite your people as owners, admins, billing or members, and pay for projects and servers as the company.

  • Its own card, billing details and invoices
  • Invitations by email, valid for 7 days
  • Access tokens limited to one organization

• 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

• Client portal and support plans

  Clients whose Odoo we manage get their own view: status, uptime, backups and monthly reports, with support requests answered within their plan's response time.

  • Client admins and read-only viewers
  • Restart requests approved in one click
  • Never logs, shells or other clients' data

• Partner and reseller program

  Odoo partners bring their clients with a discount or a commission, and a partner portal to buy hosting and create projects for them.

  • Referral links with 90-day attribution
  • Monthly commission statements
  • Optional white-label header

• Monthly reports

  On the 1st of each month, project admins get last month's report: uptime and incidents, deploys, backups and restore tests, storage growth and a health score.

  • Month-to-date report on demand
  • Each person can opt out
  • The same reports in the client portal

Tools & help

Your terminal, your scripts, your phone and your chat tools, with help when you need it.

• kv, the command-line tool

  Status, rebuilds, live logs, backups and database dumps from your terminal or CI. Sign in through your browser and kv gets a scoped token of its own.

  • Knows the branch of your Git checkout
  • Switch between personal and organization workspaces
  • Your linked servers and Odoo installs too

• API and access tokens

  Script the platform and trigger rebuilds from CI with personal access tokens, scoped to reading, builds, backups or admin, and documented in the API reference.

  • Shown once, stored only as a hash
  • Narrowed to some projects if you like
  • Never more than your own access

• An app with push notifications

  Install the dashboard on your phone's home screen or your computer, and get failed builds and backups, a linked server going down and support replies as push notifications.

  • Choose which events reach your devices
  • Never logs or message text, only a title and a link
  • Works with the dashboard closed

• Chat notifications

  Builds, deploys, backup failures and downtime posted to Slack, Discord, Microsoft Teams or a signed webhook.

  • Chosen per project by its admins
  • HMAC-signed JSON for your own tools
  • Webhook URLs stored encrypted

• Help chat, then a human

  The help chat answers from our documentation and cites its sources. Not enough? Talk to a human and the team gets the whole conversation.

  • Team replies in the chat and by email
  • Secrets you paste are redacted
  • Step-by-step guides for every feature

• Your data, portable

  Download any backup as a standard Odoo backup, and export your account or a project's data whenever you want.

  • A signed download link, usable once
  • Never includes secrets
  • Standard formats: Odoo zip and JSON

See it on your own repository

Every feature is included in every plan. On our cloud you only choose the capacity; on your server you pay per server.

Start now · Read the FAQ