The plugin marketplace is how AiHummer grows beyond its built-in runtime. Its
catalog syncs from a CDN, installs are one click from the admin UI, and every
plugin runs host-native — there is no Docker anywhere in the model. Plugins
come in three tiers that differ in how they execute and what they can do.
The three tiers at a glance
Tier
What it is
How it runs
Credentials
Tier 1
Standalone host-native services (channels, voice)
Its own sandboxed systemd unit + port
Shared (workspace)
Tier 2
In-process tools/skills
Inside the gateway process
Personal or shared
Tier 3
Zero-code source types (OpenAPI, MCP)
Synthesized by the gateway, no code
Personal (per-user OAuth) or shared
Tier 1 — standalone host-native services
Tier-1 plugins are full services in their own right: channel connectors and voice
components such as the SIP, Bitrix24, Einstein and iOS-proxy plugins. Each one is
deployed as its own sandboxed systemd unit listening on its own port, and the
gateway talks to it over HTTP. This is the “host-native, not Docker” principle in
action — a plugin is a managed system service, not a container.
Channel connectors in the catalog: Community includes Telegram and MAX.
MAX (a new Russian messenger, channel max).
Bitrix24 (an
internal employee IM channel, not customer omnichannel), plus Discord, Slack,
Teams, Matrix, Signal, Email and WhatsApp are licence-gated — see the note below.
[!NOTE]
Community includes Telegram and MAX. Installing any other channel connector requires an active Starter,
Business or Enterprise licence; on Community the install request
returns HTTP 402 “upgrade required” (code plan_limit) — see
Licensing.
[!NOTE]
Tier-1 plugins are not bundled into the gateway binary. They are installed and
supervised as separate systemd services and reached by URL, which is why each
one has its own port.
Tier 2 — in-process tools/skills
Tier-2 plugins are tools/skills compiled into the gateway and run inside its
process. Because they execute in-process on behalf of the acting user, they can
use personal or shared credentials: the
personal mode attributes an action to a specific person (their credential and
turn attribution), the shared mode uses one workspace-wide credential.
[!NOTE]
Personal integrations to external accounts (Google, Microsoft, Todoist, Asana,
Jira, ClickUp, GitLab, Spotify, Fitbit, Oura, SmartThings and more) ship as
zero-code Tier 3 — per-user OAuth
integrations that each user connects to their own account.
Tier 3 — zero-code source types
Tier-3 plugins require no integration code at all. There are two source
types:
OpenAPI — point at any OpenAPI 3.x spec and AiHummer synthesizes one tool
per operation.
MCP — connect any MCP server over stdio or HTTP and expose its tools/list.
Both turn an existing service into agent tools without you writing or deploying
any code.
Through the OpenAPI mechanism with per-user OAuth, a large set of personal
integrations is already available — each user connects them to their own
account: Gmail, Google Calendar, Google Contacts, Google Tasks, Google Drive,
YouTube, Outlook Mail, Outlook Calendar, OneDrive, Microsoft To Do, Todoist,
Asana, Jira Cloud, ClickUp, GitLab, Fitbit, Oura Ring, Spotify, Samsung
SmartThings and more. See
Zero-code integrations for the full walkthrough.
The catalog and CDN
The marketplace catalog syncs from a CDN, so the list of installable plugins
is kept current without manual packaging on your side. From the admin UI you
browse the catalog, install with one click, and let each installation auto-update
on its own schedule.
Official and community
The catalog is split into two registries that don’t mix:
Official (first-party) — modules from AiHummer. The source is pinned and
trusted by default (verified against the pinned registry key); in the Web UI
these plugins carry an Official badge and rank first.
Community (third-party) — plugins from external developers published through
the personal cabinet («My plugins» →
upload → AI review → human moderation). They are added as a separate source
(community-catalog.json) that does not overwrite the official catalog; in
listings these plugins show without a badge and sort by download count.
Both registries use the same manifest contract and the same install path; they
differ in origin and trust anchor (see
Install & updates).
Where to next
Install & updates — the one-click
install lifecycle and sandboxed systemd units.
Plugin SDK — build your own plugin from a
single manifest.json.
Publishing a plugin — the official and
community registry, the two publishing modes.
The **plugin marketplace** is how AiHummer grows beyond its built-in runtime. Its
catalog syncs from a CDN, installs are one click from the admin UI, and every
plugin runs **host-native** — there is no Docker anywhere in the model. Plugins
come in **three tiers** that differ in how they execute and what they can do.
## The three tiers at a glance
| Tier | What it is | How it runs | Credentials |
|---|---|---|---|
| **Tier 1** | Standalone host-native services (channels, voice) | Its own sandboxed systemd unit + port | Shared (workspace) |
| **Tier 2** | In-process tools/skills | Inside the gateway process | Personal or shared |
| **Tier 3** | Zero-code source types (OpenAPI, MCP) | Synthesized by the gateway, no code | Personal (per-user OAuth) or shared |
## Tier 1 — standalone host-native services
Tier-1 plugins are full services in their own right: channel connectors and voice
components such as the SIP, Bitrix24, Einstein and iOS-proxy plugins. Each one is
deployed as **its own sandboxed systemd unit listening on its own port**, and the
gateway talks to it over HTTP. This is the "host-native, not Docker" principle in
action — a plugin is a managed system service, not a container.
**Channel connectors in the catalog:** Community includes Telegram and MAX.
- MAX (a new Russian messenger, channel `max`).
- Bitrix24 (an
internal employee IM channel, not customer omnichannel), plus Discord, Slack,
Teams, Matrix, Signal, Email and WhatsApp are licence-gated — see the note below.
> [!NOTE]
> Community includes Telegram and MAX. Installing any other channel connector requires an active **Starter**,
> **Business** or **Enterprise** licence; on Community the install request
> returns **HTTP 402 "upgrade required"** (code `plan_limit`) — see
> [Licensing](/en/v1.6/commercial/licensing/).
> [!NOTE]
> Tier-1 plugins are not bundled into the gateway binary. They are installed and
> supervised as separate systemd services and reached by URL, which is why each
> one has its own port.
## Tier 2 — in-process tools/skills
Tier-2 plugins are **tools/skills compiled into the gateway and run inside its
process**. Because they execute in-process on behalf of the acting user, they can
use [personal or shared credentials](/en/v1.6/access/personal-vs-shared/): the
personal mode attributes an action to a specific person (their credential and
turn attribution), the shared mode uses one workspace-wide credential.
> [!NOTE]
> Personal integrations to external accounts (Google, Microsoft, Todoist, Asana,
> Jira, ClickUp, GitLab, Spotify, Fitbit, Oura, SmartThings and more) ship as
> [zero-code Tier 3](/en/v1.6/marketplace/zero-code/) — per-user OAuth
> integrations that each user connects to their own account.
## Tier 3 — zero-code source types
Tier-3 plugins require **no integration code at all**. There are two source
types:
- **OpenAPI** — point at any OpenAPI 3.x spec and AiHummer synthesizes one tool
per operation.
- **MCP** — connect any MCP server over stdio or HTTP and expose its `tools/list`.
Both turn an existing service into agent tools without you writing or deploying
any code.
Through the OpenAPI mechanism with per-user OAuth, a large set of **personal
integrations** is already available — each user connects them to their own
account: Gmail, Google Calendar, Google Contacts, Google Tasks, Google Drive,
YouTube, Outlook Mail, Outlook Calendar, OneDrive, Microsoft To Do, Todoist,
Asana, Jira Cloud, ClickUp, GitLab, Fitbit, Oura Ring, Spotify, Samsung
SmartThings and more. See
[Zero-code integrations](/en/v1.6/marketplace/zero-code/) for the full walkthrough.
## The catalog and CDN
The marketplace catalog **syncs from a CDN**, so the list of installable plugins
is kept current without manual packaging on your side. From the admin UI you
browse the catalog, install with one click, and let each installation auto-update
on its own schedule.
## Official and community
The catalog is split into two registries that **don't mix**:
- **Official (first-party)** — modules from AiHummer. The source is pinned and
trusted by default (verified against the pinned registry key); in the Web UI
these plugins carry an **Official** badge and rank first.
- **Community (third-party)** — plugins from external developers published through
the [personal cabinet](/en/v1.6/marketplace/submit-plugin/) («My plugins» →
upload → AI review → human moderation). They are added as a **separate source**
(`community-catalog.json`) that does **not overwrite** the official catalog; in
listings these plugins show without a badge and sort by download count.
Both registries use the same manifest contract and the same install path; they
differ in **origin and trust anchor** (see
[Install & updates](/en/v1.6/marketplace/install-updates/#trust-model-and-the-pinned-key)).
## Where to next
- [Install & updates](/en/v1.6/marketplace/install-updates/) — the one-click
install lifecycle and sandboxed systemd units.
- [Plugin SDK](/en/v1.6/marketplace/sdk/) — build your own plugin from a
single `manifest.json`.
- [Publishing a plugin](/en/v1.6/marketplace/publishing/) — the official and
community registry, the two publishing modes.
- [Zero-code integrations](/en/v1.6/marketplace/zero-code/) — OpenAPI and MCP in
detail.