Every Odoo branch, running on your own server

A self-hosted Odoo.sh alternative for every Git branch

Your team builds Odoo in branches and wants to show each one to a tester or a client, on your own server instead of Odoo's cloud. Sudoo.sh turns a branch into a running Odoo with its own https link in about two minutes, updates it on every push, pauses it when nobody uses it and backs it up every day.

curl -fsSL https://github.com/Sudoo-sh/sudoo.sh/releases/latest/download/sudoo-install.sh | sudo bash

Ubuntu or Debian. Installs Docker if needed, then prints the panel's link and a one-time setup code.

  • Community and Enterprise
  • Any Odoo version from 16.0
  • One Docker host
  • No open port needed
The panel's Instances page, drawn with sample data: server figures for processor, memory and disk, and one card per instance with its branch, Odoo version, edition, status and latest commit.

What it does

Odoo branch previews for tests and demos, each with its own link

The people who test and review receive a link; they install nothing and run no command. Everything is set up from the panel in the browser.

  • A live Odoo for every branch

    Pick a GitHub repository, a branch, any published Odoo version from 16.0, and Community or Enterprise. About two minutes later the instance is running.

  • Its own public link

    Every instance gets an https link that works from anywhere, through a free Cloudflare tunnel, even though the server accepts no incoming connections.

  • Updates itself from GitHub

    On every push the instance pulls the code, upgrades only the modules whose files changed and restarts. GitHub is polled every 2 minutes, or calls a webhook within seconds.

  • Pauses when idle, wakes on a visit

    An instance nobody opened for 6 hours is paused to free memory, and starts again by itself when someone opens its link.

  • Daily backups with restore

    Each instance used during the day is backed up once a day in Odoo's own format. Restore the latest in a minute or two, and undo the restore if needed.

  • Five roles, named permissions

    Super admin, administrator, maintainer, developer and viewer, checked on the server for every request, with every action in the audit log.

  • Second factors at sign-in

    An authenticator app or a code by e-mail, required for administrators or for everyone. Passwords follow NIST SP 800-63B and are stored only as scrypt hashes.

  • Live figures and charts

    Processor, memory, requests, errors and response times of the server and every instance, every 5 seconds, with an hour of history.

  • An API with signed requests

    CI pipelines and scripts create, update, restart and delete instances with an API token and an HMAC-SHA256 signature on every request.

See every feature in detail

How it works

Install the panel with one command, then share links

  1. Install on your server

    One command on Ubuntu or Debian installs Docker if needed, then the panel. It prints the panel's link and a one-time setup code for your first account.

  2. Create an instance from a branch

    Choose a repository, a branch, the Odoo version and the edition. The name, database, ports and passwords are generated for you.

  3. Share the link

    The instance has its own https link. Push to the branch and it updates itself; leave it alone and it pauses until the next visit.

Secure by default, and honest about the limits

The panel is built to be reached only through the connectors it opens itself. Instances are for showing Odoo, not for real data: each one opens with the Odoo login admin / admin.

What is and is not protected

  • Nothing listens on a public address

    The web app, the backend, the gateway and Odoo listen on 127.0.0.1 only. The way in is the Cloudflare connectors the server opened itself.

  • No default accounts

    The first account is created with a one-time setup code printed on the server.

  • Passwords never stored

    Only a salted, peppered scrypt hash. 12 to 128 characters, common passwords and sequences refused, sign-in locked after repeated failures.

  • Secrets encrypted

    GitHub deploy keys and Odoo master passwords are encrypted with AES-256-GCM. Each private repository gets its own read-only deploy key.

  • Strict browser rules

    Signed, HttpOnly, Secure, SameSite=Strict session cookie, CSRF token and same-origin check on every change, strict Content-Security-Policy, HSTS.

  • Checked input, no shell

    Every value from a browser or API client is checked against an allow-list, and external commands run without a shell.

Questions

Frequently asked questions

What is Sudoo.sh?

A panel you install on your own Linux server. It turns every branch of your Odoo repository into a running Odoo with its own https link, the way Odoo.sh does in Odoo's cloud, and you use it from a browser.

Is it affiliated with Odoo S.A.?

No. Sudoo.sh is an independent project. Odoo and Odoo.sh are trademarks of Odoo S.A.

Can I host production databases with it?

No. Sudoo.sh is for development, demos, tests and training. Every instance opens with the Odoo login admin / admin, and anyone with an instance's link can sign in with it.

What does the server need?

Linux (Ubuntu or Debian recommended), at least 2 GB of memory (about 1 to 1.5 GB per running instance), 20 GB of free disk and outgoing access to GitHub, Docker Hub and Cloudflare. No incoming port is needed with the default exposure plugin.

Does it include Odoo Enterprise?

No. Enterprise add-ons are Odoo's proprietary modules; each server needs its own copy, from a folder or a git repository. Community instances work without them.

Do the public links stay the same?

With the default free Cloudflare quick tunnels, links change when the server or a connector restarts, and the panel always shows the current ones. For fixed links, use the host-ports plugin or write an exposure plugin for a named tunnel on your own domain.

What does it cost?

The panel is free for personal and other noncommercial use under the PolyForm Noncommercial License 1.0.0. Companies that use it for their business need a commercial licence from the author.

Run your Odoo branches on your own server

Any Odoo version from 16.0, Community or Enterprise. Daily backups with one-click restore, five roles, second factors and auto-pause are included. One command installs the panel, and the same command updates it later, keeping instances, accounts and settings.

curl -fsSL https://github.com/Sudoo-sh/sudoo.sh/releases/latest/download/sudoo-install.sh | sudo bash