41-Plugin Telegram Bot Platform with SaaS Multi-Tenancy

The problem

The modern AI-augmented operator needs about 30 different small tools — agenda, task management, monitoring, deploy automation, content generation, image creation, AI code review. Buying 30 SaaS subscriptions is wasteful, building 30 dashboards is exhausting, and every tool wants its own login.

The interesting question: can a single Telegram bot be the unified surface for all of these, with tenant isolation, plugin packaging and a real billing path?

The approach

A monorepo with a thin runtime and 41 independent plugins:

Plugin SDK (`@tyber/plugin-sdk`) — defines `TyberPlugin`, `PluginContext` and a dependency-injection contract. Every plugin is an npm package, in or out of the monorepo.

Thin bot wrappers — the bot app itself contains 1-file modules that import a plugin and register it on the grammY composer. Zero business logic in the bot core.

Per-user credential vault — every plugin that talks to an external API (Jira, GitHub, ClickUp, Spotify, Cloudflare, etc.) reads credentials from a per-user encrypted vault, never from global env vars. New users go through a `/setup` wizard.

BullMQ queue for jobs that can take minutes (Claude CLI runs, browser automation). The bot stays responsive; the worker churns through jobs with retry and DLQ.

Static analysis as a CI gate — `gate-app-coverage.test` enforces that every plugin command goes through the SaaS gate, every callback follows the navigation pattern, and there's no `// Legacy` callback without a removal date.

External-plugin path — plugins can live in their own GitHub repo, depend on `@tyber/plugin-sdk` from GitHub Packages, and be installed from the Tyber.io app store. Plugins are products.

The outcome

41 plugins running in production, 905+ automated tests on the bot core, ~3,800 tests across the whole monorepo. CI completes in ~35 seconds for incremental changes thanks to Turbo cache. Multi-tenant from day one, no shared keys, no leaks across tenants.

The bot is the GTM surface: every plugin can be sold standalone, bundled, or given away. The deployment, billing and distribution problem is solved by Telegram itself.

Why it matters

Most "AI agent platforms" are demo-ware that crumbles when you ask for production guarantees. This one was built production-first: tests, queues, tenant isolation, graceful shutdown, deploy guards, observability. The plugin architecture means a feature ships in hours, not weeks. The cost of a new app is one plugin file plus a thin wrapper, not a new SaaS company.