SpawnLabs
Home/Work/Skelda
Community Operations

Turning Telegram groups into managed communities

Telegram gives you a group chat. Skelda gives you the operations layer — automated protection, group management, analytics, and team access control — all from one dashboard.

Telegram BotWeb DashboardAnti-SpamAnalyticsGroup ManagementTeam Access
Visit Live Site

Overview

Telegram gives you a group chat. Not a managed community.

Large Telegram communities — crypto projects, gaming groups, tech channels — need more than chat. They need spam defense, growth analytics, scheduled announcements, team coordination, and audit logs. Telegram's native tools cover almost none of this.

Skelda was built to close that gap. SpawnLabs designed and shipped a complete community operations layer: a bot engine handling protection and management inside Telegram, and a web dashboard giving admins full visibility and control — analytics, team access, content rules, and group management in one place.

The Challenge

Four problems, zero native solutions

Communities at scale hit the same walls. Spam and raids erode trust faster than admins can react. There's no way to understand growth trends, peak activity, or member engagement. Announcements and recurring messages require manual effort every time. And when multiple admins are involved, there's no access control, no audit trail, and no shared visibility.

Existing bots addressed fragments — a spam filter here, a welcome message there — but nothing connected these into a coherent operations layer. Admins were stitching together three or four bots, losing context between them, and still flying blind on what was actually happening in their communities.

Strategic Response

Treat community management as an operations problem

The core decision was to build one system covering all four pillars: protection, analytics, group management, and team operations. Not four separate bots — one unified platform where every capability feeds into the same dashboard and the same data layer.

This meant moving configuration and visibility out of Telegram's chat interface entirely. Admins shouldn't memorize bot commands or parse log files. They need a proper control surface — a web dashboard where protection rules, growth metrics, scheduled messages, and team permissions are visible and adjustable in one place.

What Was Built

One bot, one dashboard, full community operations

The bot engine runs inside Telegram — handling real-time spam detection with smart filters and NSFW image detection, enforcing flood limits, maintaining a known spammers database, managing service messages, and executing automated actions before damage spreads. It also powers the management layer: scheduled announcements, custom commands, user lookup, and whitelist management.

The web dashboard gives admins a visual control surface for everything. Group analytics — growth curves, active user counts, optimal posting schedules. Protection configuration — banned words, spam filters, content rules. Management tools — scheduled messages, announcements, user search. And team operations — role-based access control, advanced logging, and full audit trails across every action.

Behind both surfaces, a custom backend handles real-time event ingestion from Telegram's API, rule evaluation, action execution, and data aggregation for the analytics pipeline. No third-party moderation frameworks — every layer purpose-built for this use case.

Key Capabilities

What the system enables

Automated Protection Layer

Anti-spam, anti-flood, banned word filters, NSFW image detection, known spammers database, and smart filters — all running in real time, enforcing rules before damage spreads.

Group Analytics & Insights

Member growth tracking, active user metrics, message volume trends, and optimal posting schedule analysis — turning raw group activity into actionable data.

Group Management Tools

Scheduled and automated messages, announcements, custom bot commands, whitelist management, and user lookup — replacing manual coordination with structured workflows.

Team Access & Audit Logging

Role-based access control for admin teams, advanced action logging, and full audit trails — so every moderation decision is tracked and every team member has the right level of access.

Web-Based Control Dashboard

Every setting, every metric, every log — accessible from the browser. No chat commands, no config files. Admins authenticate with their existing Telegram identity.

Service Message Management

Automated handling of join/leave notifications, pinned messages, and system events — keeping the chat clean and focused on real community activity.

Product UI

Dashboard screenshots

Skelda dashboard overview — member stats, activity chart, protection breakdown, and latest actions
Protection settings — anti-spam, flood detection, banned words, and content filtering configuration
Group analytics — message activity, daily active users, engagement rate, and protection statistics
Activity insights — peak hours, activity calendar heatmap, and member growth trends

Dashboard overview, protection configuration, group analytics, and activity insights.

How It's Built

The stack behind it

Bot Engine

Telegram Bot APIReal-time event processingPattern detectionAutomated actions

Backend & Data

Custom API layerEvent-driven architectureDatabase designAnalytics pipeline

Web Dashboard

Server-rendered appTelegram auth integrationReal-time updatesResponsive design

Infrastructure

Cloud hostingCI/CD pipelineAutomated deploymentsMonitoring

Impact

Live and protecting

100k+
Messages processed daily
<1s
Threat response time
1,000+
Communities protected
100%
Automated enforcement

Every threat action — spam removal, flood blocking, raid defense — is fully automated. No manual moderation required. Admins configure the rules; the system enforces them in real time across all protected communities.

Running a community that's outgrowing group chat?

When your Telegram group needs protection, analytics, management tools, and team coordination — but all you have is a chat window — the answer isn't more admins. It's infrastructure.