Telegram groups → managed communities.

Once a Telegram community grows past a few thousand members, it stops being a chat group and starts being a small operation — moderation queues, spam waves, raids, growth tracking, role assignments, broadcasts. Telegram's native admin tools cap out around 'pin a message.' Existing bots solved one problem at a time; nobody had built the operational layer that 24/7 communities actually need.

We treated Telegram as the substrate, not the product. Skelda is a multi-tenant ops layer: each community gets a bot for in-chat enforcement plus a web dashboard for analytics, RBAC, and configuration. We built the anti-spam engine first because it's the hardest and most visible — sub-second latency, classifier-based, with fallback heuristics. RBAC was next, because once a community has a mod team, ownership of permissions is non-negotiable.

Skelda now runs in 1,000+ communities covering more than 4M members. Spam is removed in under a second, with zero manual triage in steady state. Mod teams have proper RBAC instead of 'admin or nothing.' Owners can see growth, retention, and engagement in a dashboard rather than guessing. Raids that used to take down communities are auto-detected and locked down in seconds.