Community vs Commerce Editions
RustPBX is distributed as two build flavours that share the same codebase and the same config.toml format:
- Community — the default build. Core SIP proxy/PBX, the console, and the community addons. No license keys are required or read.
- Commerce (Enterprise) — the commercial build shipped from the Miuda registry. It adds the commercial addons plus the
[licenses]configuration and license verification againsthttps://miuda.ai/api/verify.
This page explains what each edition includes and how licensing differs. For the exact license-key format, see License Activation.
1. Build flavours
The difference is a Cargo feature flag, commerce, which is only meaningful when RustPBX is compiled with it:
| Community | Commerce (Enterprise) | |
|---|---|---|
| Core SIP proxy / PBX / console | Yes | Yes |
| Community addons (ACME, Archive, Transcript, Queue, Observability) | Yes | Yes |
| Commercial addons (Voicemail Pro, IVR Editor, Wholesale, …) | Not compiled in | Compiled in |
Reads the [licenses] section of config.toml | No — the section is ignored | Yes |
Verifies keys against https://miuda.ai/api/verify | No | Yes |
| Product support | Community / GitHub | Commercial support channels |
Without the commerce feature the [licenses] block in config.toml is not recognised at all, and the internal addon gate is hard-wired to “allowed”. Licensing is a Commerce-edition behaviour.
The Commerce build is published to the commercial registry as docker.cnb.cool/miuda.ai/rustpbx:latest. The community image is ghcr.io/restsend/rustpbx:latest. See Basic Setup for the pull and run commands.
2. Addons by category
Addons declare themselves as either Community or Commercial. The commercial ones are the parts of the product that require a license key.
| Addon ID | Addon | Category | Notes |
|---|---|---|---|
ivr_editor | IVR Editor | Commercial | Visual IVR flow editor |
voicemail | Voicemail Pro | Commercial | Published list price in the addon metadata: $499/year |
wholesale | Wholesale | Commercial | Published list price in the addon metadata: $4999/year |
acme | ACME | Community | Automatic TLS certificates |
archive | Archive | Community | Recording archiving |
transcript | Transcript | Community | Offline ASR |
queue | Queue | Community | Call queues |
observability | Observability | Community | /metrics and /healthz (Prometheus) |
cc | Contact Center (CC) | Defaults to Community in the code | Shipped behind its own feature flag; see the note below |
Contact Center licensing
The Contact Center addon (cc) is compiled behind a separate contact-center Cargo feature rather than the commerce feature, and in the current source its category is the default (Community) rather than Commercial. The docs elsewhere group CC with the commercial addons. Treat CC as a contact-sales conversation rather than assuming a specific self-service license rule, and confirm with sales before relying on it.
Addon IDs are the strings you use in [licenses.addons]. Use the ID exactly as shown in Console → Addons — a mismatch means the addon will not find its key and will be treated as unlicensed.
3. How licensing differs
In the Commerce edition each commercial addon is bound to a named license key:
[licenses.addons]maps an addon ID to a key name.[licenses.keys]maps that key name to the actual license key string.
Several addons can share one key, which is the normal case for an Enterprise plan: a single key covers every addon the plan includes, and the plan’s scope decides which addons it is valid for. A key whose scope does not include a given addon will be rejected for that addon.
At startup the Commerce build verifies each configured commercial addon and records a per-addon license status (valid/expired, plan, expiry, scope). That status is what the console shows on the Addons → Licenses tab. Verification results are cached in memory, so a running process does not re-contact the license server on every call.
The Community edition has none of this: every compiled addon simply runs.
Implementation references (for operators who want to confirm against the source):
LicenseConfigis only compiled for thecommercefeature —src/config.rs:557-560andsrc/config.rs:684-689.commerceenables the Voicemail and IVR Editor addons;wholesaleandcontact-centerare separate features —Cargo.toml[features].- Addon category overrides:
src/addons/ivr_editor/mod.rs:47-48,src/addons/voicemail/mod.rs:190-191,src/addons/wholesale/mod.rs:89-90.
4. Which edition should you run?
- Evaluating, lab, or community deployment — use the community image. Add a license only if you need a commercial addon.
- Production with Voicemail Pro, IVR Editor, or Wholesale — use the commercial image and activate a key. See License Activation.
- Not sure yet — start a 7-day free trial and activate the key against the commercial image.
Continue to Free Trial to get a key, or jump straight to License Activation.