Write a plugin — we will show it to everyone running AiHummer

Publishing is free and we take no cut. The other way round: every published module adds a month to your AiHummer subscription. Community modules are given away free, and a reader can support the author through a link the author provides.

Any of our customers with an account area — there is no separate developer status to apply for. Build the module with the Plugin SDK, upload the artefact with its description in your account and send it for review.

An automated check first, then review by a person. We look at whether the module does what its description promises, whether it asks only for the access it needs to work, and whether it moves data somewhere nobody expects. After the review we sign the build — and it appears in everyone’s catalogue.

Yes, both. A module can be hidden for a while or pulled from the storefront for good — new installations stop. Versions live side by side: you ship an update as its own version with a list of changes and publish it right away or on a schedule.

For each module you can see how many times it was installed, how many servers use it right now and how many removed it. This is your module’s statistics, not information about other people’s installations: you do not see who installed it.

We build and sign the official one: it arrives with a core update and we support it. A community module is written by an outside author, submitted through the account area and put through automated checks and moderation; we sign it, but the author owns the code and its future. The card says which one you are looking at: “Official” or “Third-party”.

No. You pay for a plan, and the plan opens a set of channels and modules. Community opens one channel — Telegram. Starter opens five: Telegram, WhatsApp, MAX, VK, Avito. Business adds email and phone. Bitrix24 opens on Enterprise. The exact set for your plan is in the table on the pricing page.

The channel stops receiving and sending messages; the integration stops calling the outside service. Conversations, the agent’s memory and the module’s own settings stay where they were: switching off deletes nothing. Switch it back on and work resumes from the same point, with no re-setup.

If you install on your own server, it lives on your server: conversations, access keys and the agent’s memory sit in your database. Only what the work cannot happen without leaves it: the request text goes to the model you chose, the method call goes to the service you connected. In the AiHummer cloud the same data sits on a dedicated server in a Russian data centre.

Official ones arrive with a core update: your installation checks the signed catalogue and takes the new version. The version number is shown on the module card and on the versions page. Nothing has to be reinstalled, and an update does not reset your settings or conversations.

Three routes, and two of them need no programmer. First: connect the service through its OpenAPI description — the agent gets its methods as its own tools. Second: connect an MCP server. Third: write your own module with the Plugin SDK and publish it on the marketplace so everyone can use it.