Plugins in 2.0 (planned)
Plans, not features
Nothing on this page exists yet
This page describes what is planned for Sudoo.sh 2.0. The plan is a draft under review: details will change, and none of it can be installed or used today. For the plugins the panel has now, read Plugins.
What exists today
The panel already has plugins. They are Python packages that register classes under entry points, and a setting chooses which one runs. Eight plugin types ship with the panel:
| Plugin type | Setting | Built-in plugins |
|---|---|---|
| Exposure | EXPOSURE | cloudflare-quick, host-ports |
| Add-on source | ENTERPRISE_SOURCE | folder, git (and none) |
| Update trigger | UPDATE_TRIGGERS | polling, github-webhook |
| Storage | STORAGE | sqlite |
| Authenticator | AUTH | local |
| Second factor | SECOND_FACTORS | email, totp |
| Mailer | MAILER | smtp, none |
| Rate limiter | RATE_LIMITER | memory |
A plugin you write yourself is installed into the panel's environment: add it to the panel's pyproject.toml, lock, choose it in a setting and run install.sh; see Writing a plugin. Everything in the sections below is in addition to this, and only planned.
What 2.0 plans to add
Plugin packages
A plugin would become a package with a manifest that describes it: its identifier, version, the panel versions it supports, its type, the entry points it registers, the settings it adds to the Settings page and the permissions it needs (for example outgoing network access). The manifest would let the panel show a plugin's settings and check that it fits before installing it.
Installing from the panel
Administrators would install, enable, disable, update and remove plugins from the panel itself, instead of changing the panel's dependencies and installing it again. The planned life of a plugin:
| Step | What would happen |
|---|---|
| Install | The package is downloaded and its signature checked before anything else |
| Enable | Its entry points are loaded and its settings appear |
| Disable | It stops running; its data is kept |
| Update | A new version goes through the same signature check |
| Remove | Its files and registrations are removed |
Signed packages
Every package listed in the planned marketplace would be signed, and the panel would verify the signature against a public key shipped with each release. An unsigned or modified package would be refused at install and never loaded.
New extension points
Beyond the eight plugin types above, the draft lists new places where plugins could hook in:
| Planned group | Purpose |
|---|---|
| Web pages | Add pages to the web app |
| API routes | Add endpoints under the panel's API |
| Background tasks | Register recurring work |
| Instance hooks | Act when an instance is created, started, stopped or deleted |
| Dashboard widgets | Add cards or charts to the Instances page |
| Notifications | Send alerts to chat or other channels |
| Backup destinations | Store backups somewhere other than the server |
| Themes | Override colours and the logo |
| API access | Let other systems into the panel's API, and tell them when something happens |
| MCP server for AI assistants | Let AI assistants use the panel's operations through the Model Context Protocol |
Some built-ins as separate plugins
Some of today's built-in plugins (for example the Cloudflare exposure, the GitHub webhook trigger, the second factors and the SMTP mailer) would move into their own packages, while the ones every server needs (local sign-in, SQLite storage, the memory rate limiter, host-ports, folder and polling) would stay in the core.
The API for other systems as a plugin
Today the panel's API serves two kinds of callers: its own web app, with the session of the person signed in, and other systems (CI pipelines, scripts, dashboards) with an API token and a signature on every request. The plan keeps the first in the core, because the panel cannot work without it, and moves the second into a free plugin, REST API for other systems (com.sudoo.api), installed and enabled by default so that upgrading does not break anything that uses a token today.
| Part | Today | Planned in the plugin |
|---|---|---|
| API tokens and signed requests | Built in | Moved unchanged: token stored as a hash, signing secret encrypted, HMAC-SHA256 signature, 5-minute window, each nonce once |
| What a token may do | read acts as a Viewer, write as an Administrator | A role per token, never above the role of the person who created it and checked on every call; an optional expiry date, allowed addresses and instance names |
| Outbound webhooks | None | The panel calls your address when a job finishes, an instance is created or deleted, or an update fails; each call signed with the webhook's own secret; private addresses refused by default |
| OpenAPI document | None | GET /api/v1/openapi.json, generated from the panel's own list of endpoints |
Without the plugin the panel works as before for people; it only refuses requests that carry a token.
MCP server for AI assistants (new)
A second free plugin, MCP server for AI assistants (com.sudoo.mcp), is planned to let an AI assistant that speaks the Model Context Protocol work with the panel. It needs the REST API plugin above, asks for the permissions network.inbound, instances.read and instances.write, and is published by Sudoo.sh itself, so it carries the Official badge.
The use case it is planned for: you ask in plain words, for example "create a demo instance of branch feature/pos with the data of yesterday's backup of sales-main", and the assistant calls the panel's tools: it lists the backups, shows the plan, creates the instance from the backup and waits for the job. You can also ask it how a job is going or to read an instance's logs. Starting an instance from a backup is a panel feature ("Start from a backup" on the New instance page); the plugin would make it reachable from an assistant.
| Topic | Plan |
|---|---|
| Connection | An endpoint /mcp on the panel (Streamable HTTP), and a small bridge program, sudoo-mcp, for assistants that start servers on your own computer; the bridge signs every request like any API call |
| Sign-in | A token from the API plugin with its own mcp scope: accepted only on /mcp, with an expiry of at most 90 days, and optionally limited to your own addresses |
| Tools | List and read instances, versions, backups, jobs and logs; plan and create an instance (optionally from a backup); restore a backup; back up, start, pause, restart, update; wait for a job |
| Permissions | Each tool needs the same permission as in the web app; the assistant only sees the tools the token may use, and the panel checks again on every call |
The safety rules planned for it:
- Tools are marked read-only or destructive, so the assistant's app asks the person 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 an instance is off unless a setting turns it on.
- A backup of the current state is always taken before a restore or a deletion.
- Limits on changes per hour and on jobs running at once.
- Passwords never appear in results.
- Every call is in the audit log as
mcp:<token name>.
Publishing: every version reviewed
Plugins would reach the marketplace only through Sudoo.sh. Every version of every plugin, from Sudoo.sh or from another developer, would go through the same steps before anyone can install it:
| Step | What would happen |
|---|---|
| Automated checks | Seconds after upload, the hub checks the manifest, the package size and structure, file paths, required plugins and forbidden files. A failure goes back to the developer with the report |
| Test on a review panel | The package is installed on a disposable review panel with sample Odoo data, its settings tried, then removed |
| Review | A Sudoo.sh reviewer checks that it does what its listing says, asks only for the permissions it needs and sends no data off the server without saying so |
| Publish | The hub signs the package and lists the version. Panels check the signature before installing |
A version that fails a check or the review goes back to the developer with changes requested, and can be resubmitted. A published version can be withdrawn; copies already installed keep working but get no updates.
Publisher badges
| Badge | Meaning |
|---|---|
| Official | Made by Sudoo.sh itself, from its own publisher account: the plugins that ship with the panel, the REST API plugin and the MCP server for AI assistants |
| Verified | Sudoo.sh confirmed who the publisher is, person or company: an identity check, a verified domain or e-mail, a signed developer agreement, a working support channel and at least one reviewed plugin. The badge can be taken away |
| None | A registered developer whose identity is not confirmed yet. Their plugins go through the same checks and review |
Paid plugins as subscriptions
Free plugins would install without an account. A paid plugin would be bought for one panel, which needs that panel to be linked to an account on app.sudoo.sh: the account gives a one-time code, and a super admin types it in the panel under Settings → Marketplace. Only verified developers could sell plugins.
| Plan | Billing |
|---|---|
| Monthly | A subscription that renews every month until cancelled |
| Yearly | A subscription that renews every year until cancelled |
| Fixed term | Paid once for a set period, for example three months; it does not renew |
What would happen around the end of a subscription or term:
- Reminders by e-mail 7 days and 1 day before it ends, and a notice in the panel for its super admins.
- When it ends without renewal, a grace period starts (7 days by default) and the plugin keeps working.
- 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.
- Renewing switches the plugin back on by itself. Uninstalling is always a separate action a super admin chooses.
A panel that cannot reach the hub keeps its paid plugins until the end of the last grace period it knows about.
A marketplace and a plugin SDK
A catalogue of plugins at marketplace.sudoo.sh, a portal for plugin authors at developers.sudoo.sh, and a plugin SDK documented on this site. These are planned properties; their pages say what is available.
Follow the work
Releases and their notes are published on GitHub. This page will be replaced by real documentation for each part as it ships.