Plugins

Odoo panel plugins for what differs between servers

Your server has no open port, your Enterprise add-ons sit in a git repository, or your team signs in with second factors. Sudoo.sh keeps one core and makes each of these choices an Odoo panel plugin, picked per server, so you change a setting instead of the code.

Every plugin that ships with the panel is published by Sudoo.sh Official

Built-in plugins that ship with the panel

Eight plugin types, each with at least one plugin included and free. Most are chosen on the Settings page and apply after restarting the panel; the exposure and the storage are set in the server's .env.

For developers

Write a plugin for your own setup

A plugin is a Python class that implements one of the interfaces, registered under its group's entry point. Install it into the panel's environment, name it in the setting, and reinstall.

For example, an exposure plugin can give every instance an address on a wildcard domain served by a reverse proxy you already run, or use a Cloudflare named tunnel on your own domain, so links never change. The interface of each plugin type, and the rules a plugin must follow, are in the documentation.

Read how to write a plugin

# pyproject.toml of your package
[project.entry-points."sudoo.exposure"]
wildcard-domain = "my_exposure.wildcard:WildcardDomain"

# then, on the server: EXPOSURE=wildcard-domain

Sudoo.sh 2.0

Coming

Planned: a REST API plugin and an MCP server for AI assistants

Two free plugins from Sudoo.sh are planned for 2.0. They are not available yet. The panel's own web app keeps its API in the core; these change how other systems, and AI assistants, get in.

  • REST API for other systems

    Coming

    How CI pipelines, scripts and dashboards use the panel.

    • com.sudoo.api API tokens with a signature on every request, as built into the panel today, plus a role and expiry per token, signed outbound webhooks and an OpenAPI document. Free.

    Publisher: Sudoo.sh Official

  • MCP server for AI assistants

    Coming

    Working with the panel by asking an AI assistant in plain words.

    • com.sudoo.mcp Ask an assistant to create a demo of a branch with the data of an existing backup, check how its jobs are going or read an instance's logs. It needs the REST API plugin. Free.

    Publisher: Sudoo.sh Official

What you could ask an AI assistant

The MCP server for AI assistants would let an assistant that speaks the Model Context Protocol work with your panel. Every tool it calls is an action the panel already has, with the same permissions as in the web app. For example:

  • “Create a demo of branch feature/pos with the data of last night's backup of sales-main.”
  • “Is the update of the training instance still running, or did it fail?”
  • “Show me the last errors in the logs of the demo instance.”

Safety rules it is planned with

  • The assistant only gets the tools that its token's permissions allow, and the panel checks the permission again on every call.
  • Tools are marked read-only or destructive, so the assistant's app asks you before anything changes.
  • Creating an instance can be planned first, as a dry run that changes nothing.
  • Restoring a backup, rolling back and deleting take two steps with a single-use confirmation code. Deleting is off by default.
  • A backup of the current state is always taken before a restore or a deletion.
  • Tokens expire, work only on the panel's /mcp address and can be limited to your own addresses.
  • Every call is in the audit log as mcp:<token name>, and passwords never appear in results.

Details are in the plan for plugins in 2.0.

Marketplace

Coming

A reviewed plugin marketplace, planned

The marketplace at marketplace.sudoo.sh is not open yet: nothing can be bought or installed from it today. Everything in this part of the page describes the plan. It is meant to be one place to find free and paid plugins, from Sudoo.sh and from other developers, and install them from the panel. Developers would publish through developers.sudoo.sh, set their own prices and keep 70% of each sale.

Until it opens, plugins are Python packages you install yourself. Follow progress on GitHub.

Coming

How plugin review and publishing would work

Every version of every plugin goes through the same steps. Only published versions are listed or can be downloaded.

  1. Automated checks

    Seconds after the developer uploads a package, the hub checks its manifest, size, file paths, required plugins and forbidden files. A failed check goes back to the developer with the report.

  2. Review on a test panel

    A Sudoo.sh reviewer installs the plugin on a review panel with sample Odoo data, tries its settings and checks that it does what its listing says and asks only for the permissions it needs.

  3. Signed and published

    Once approved, the hub signs the package with its Ed25519 key and lists it. Panels check that signature before installing.

A plugin version pulled from the marketplace is no longer offered; copies already installed keep working but get no updates. The marketplace never builds from a repository: it reviews the exact package that people install.

Coming

Publisher badges: Official and Verified

A badge next to the publisher's name says what Sudoo.sh knows about who made a plugin. It is not a rating of the plugin.

Official
The Sudoo.sh mark and the word Official. Made by Sudoo.sh itself, from its own publisher account: the plugins that ship with the panel and the planned REST API plugin and MCP server for AI assistants.
Verified
A green tick next to the publisher's name. Sudoo.sh confirmed who the publisher is, person or company, through an identity check and a verified domain or e-mail. The badge can be taken away.
No badge
A registered developer whose identity Sudoo.sh has not confirmed yet. Their plugins still go through the same checks and review.

Coming

A paid plugin is bought for one server, on a plan its publisher offers. Prices have not been set; the amounts below are an example of how each plan reads.

  • Monthly

    $10 a month

    A subscription that renews every month until you cancel it.

  • Yearly

    $100 a year · $8.33 a month · save 17%

    A subscription that renews every year. Next to the yearly price you see what it costs per month and how much it saves against paying monthly.

  • One time

    $249 once · never expires

    Paid once for a lifetime licence on one server. It never expires and has no renewals; it ends only if you unlink the server from your account.

  • Fixed term

    $27 for 90 days

    Paid once for a set number of days, for example 90. It does not renew; buy it again to extend it.

Example only: with a plugin at $10 a month and $100 a year, the yearly plan works out at $8.33 a month, so it saves 17%. The marketplace and the panel work out these figures for every plan, so a one-time licence and a subscription can be compared before you choose. Checkout happens on app.sudoo.sh.

  1. To buy a paid plugin, you link your server to your account on app.sudoo.sh with a one-time code that a super admin types in the panel. Free plugins never need this.
  2. You choose the plugin and its plan in the panel, which opens the checkout on app.sudoo.sh. You pay there, signed in with the account the server is linked to; the panel never sees your card, and installs the plugin once the payment goes through.
  3. Seven days and one day before a subscription or term ends, you get an e-mail reminder, and the panel shows a notice to its super admins.
  4. When it ends without renewal, a grace period starts, 7 days by default, and the plugin keeps working.
  5. After the grace period the panel backs up every instance the plugin touches and its own data, then switches the plugin off. Its data and settings are kept; nothing is deleted.
  6. Renewing switches the plugin back on by itself. Uninstalling is always a separate action that you choose.

Coming

Plugins made for your country

Some plugins only make sense in some countries, such as tax, e-invoicing or payroll rules.

  • A publisher names the countries a plugin is made for, such as an e-invoicing or payroll plugin for Egypt or Saudi Arabia, the languages it speaks and the Odoo versions it supports.
  • The marketplace shows a Local label with those countries, and its country filter lists only the plugins made for the country you choose.
  • A plugin that names no country is made for everywhere. Recommendations leave out plugins made only for other countries.

Coming

Plugin recommendations, and what they keep

Recommendations help you find plugins that fit your server. They are only for you, and you can turn them off.

  • Signed in on app.sudoo.sh, the marketplace and your panel show a short list of plugins recommended for your server, each with its reason, such as "Because you use Sample mailer" or "Made for your country".
  • They come from the plugins your server already runs, its Sudoo.sh and Odoo versions, your account's country and plugins that are popular or from verified publishers.
  • Personalised recommendations are on by default. While they are on, Sudoo.sh keeps your searches, the plugin pages you open, installs, removals and purchases, with your server's versions and your country, for 365 days.
  • Turn them off in your account settings on app.sudoo.sh at any time: what was kept is deleted and nothing more is kept. Visitors who are not signed in see no recommendations, and nobody else sees yours.

Manage them under settings on app.sudoo.sh. The privacy policy covers your account data.

Use the built-in plugins today

Free Cloudflare tunnels with no open port, Enterprise from a folder or git, GitHub webhooks or polling, authenticator apps and SMTP mail all ship with the panel. One command on Ubuntu or Debian installs it.

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