Cially

Open-source Discord server analytics, honestly reviewed. No marketing fluff, just what you get when you run it yourself.

TL;DR

• What it is: A self-hosted Discord analytics dashboard — detailed server stats (message activity, member growth, per-user engagement) running on your own server, not through a third-party bot subscription [4].
• Who it’s for: Discord community managers and server admins who want in-depth analytics without sending activity data through a commercial bot service. 207 GitHub stars — this is a small, early-stage project, not an established platform [merged profile].
• Cost savings: Analytics features on MEE6, Carl-bot, and similar bots typically start around $5.99–11.95/mo. Cially is free to self-host; your only cost is the VPS it runs on, roughly $4–8/mo [website].
• Key strength: Privacy-first. Your community’s activity metadata stays in your own PocketBase database. The project explicitly avoids storing message content [website][4].
• Key weakness: 207 stars, version 2.0 still in beta, minimal third-party reviews, and a license (CC BY-NC-ND 2.0) that is more restrictive than what most people mean when they say “open source” [README][merged profile].

---

What is Cially

Cially is a self-hosted analytics dashboard for Discord servers. A Discord bot listens to server events and writes them to a PocketBase database. A Next.js web app then reads that data to show you charts, trends, and user-level stats. When the dashboard needs a human-readable name for a user or channel, it calls the bot in real time to resolve the ID.

The GitHub README describes it as “a powerful, open-source dashboard designed to provide in-depth insights, real-time analytics, and detailed statistics for your Discord server” [merged profile]. The website homepage is more direct: “Discord Analytics Made Simple” [website].

The tech stack — Discord bot + Next.js + PocketBase — is worth understanding before you commit to deploying it. PocketBase is a single binary with an embedded SQLite database, which means no PostgreSQL to provision or manage. That’s a deliberate choice that keeps infrastructure overhead low. The trade-off is that all three components (bot, web app, database) need to run simultaneously and communicate with each other. This is not a single-container deployment [README].

The project shipped v1.0 as its first stable release and is now in version 2.0 Beta [README][4]. The developer invites contributions and accepts donations via Ko-fi — this is a one-person or small-team effort built and maintained in spare time [README].

One point requires upfront clarity: the license. The README and website use the word “open source,” but the actual license is CC BY-NC-ND 2.0 — Creative Commons Attribution-NonCommercial-NoDerivs. “ND” means no derivatives for redistribution; “NC” means no commercial use. You can read the code, run it for your own community, and share the unmodified software. You cannot fork it to build your own product on top of it, and you cannot use it in a commercial context. That is not what the Open Source Initiative defines as open source [README].

---

Why people choose it

The developer’s v1.0 announcement on r/selfhosted [4] captures the motivation: “Most Discord analytics tools are either too vague, closed-source, or come with a price tag. Cially gives you full control and transparency with zero vendor lock-in.”

That is the core argument, and it holds up. Discord’s native Server Insights panel is free but limited to servers with 500+ members, shows only high-level trends, and gives you no user-level data. Third-party bots (MEE6, Carl-bot, Statbot) fill that gap but require you to authorize a third party to read your server’s events — and to trust that their pricing model, their data retention policy, and their business as a whole remain stable indefinitely.

The self-hosting argument is about data sovereignty as much as cost. The Cially website states: “Cially never stores message content or other sensitive information unless you explicitly choose to modify the code” [website]. What it stores is metadata: who sent messages (by Discord user ID), in which channel, at what time — enough to build engagement trends without touching content. That data lives in PocketBase on your VPS, not in a SaaS vendor’s database [website][4].

To be fair: third-party reviews of Cially specifically are nearly nonexistent. AlternativeTo lists it alongside general Discord bot alternatives [3], which slightly misframes the comparison — MEE6 and Carl-bot are moderation bots that include some analytics, while Cially is purely analytics. The most substantive first-hand source available is the developer’s own Reddit launch post [4]. Independent in-depth reviews do not exist yet. Keep that in mind when weighing claims.

---

Features

Based on the README, website, and the v1.0 release notes [4]:

Core analytics dashboard:

• Basic server data (member count, growth over time)
• Message analytics (volume trends, activity by channel)
• Growth metrics (member join and leave trends)
• Activity insights (hourly trends, most active periods)
• UI and customization options [README]

User Search Page (added in v1.0):

• Per-user join and leave history
• Average message length per user
• Invites created by a user
• Most active text channel per user
• Total messages sent and account creation date [4]

Infrastructure:

• Docker-based deployment [README][4]
• REST API used internally for bot-to-web communication [merged profile]
• PocketBase backend — single binary, SQLite-based, no external database required [README]

Gaps worth noting:

• No voice channel analytics
• No role-based or permission-level breakdowns
• No data export (CSV, JSON) mentioned
• No scheduled reports or alerting
• No cross-channel or cross-period comparison features
• No mention of retention analysis

The feature set is intentionally narrow. This is an analytics tool, not a moderation suite. For reaction roles, moderation logs, giveaways, or leveling systems, you still need a separate bot [3].

---

Pricing: SaaS vs self-hosted math

Cially: Free to self-host. There is no cloud-managed version, no tiers, and no per-seat pricing [website][README]. The license prohibits commercial offerings, so this will not change.

What you are replacing:

• MEE6 Premium: $5.99/mo (single server) — analytics leaderboards and activity features are paywalled [3]
• Carl-bot Pro: $5/mo — extended logging and analytics features require paid tier [3]
• Discord native Server Insights: Free, 500+ member requirement, top-level only, no user-level data, no export

Cially self-hosted:

• Software: $0
• VPS (Hetzner, Contabo, DigitalOcean): $4–8/mo for a minimal instance
• Total: $4–8/mo

If you are currently paying $6–12/mo to a bot service for analytics, the raw savings are $60–150/year. That is modest in absolute terms. The more durable value for most community managers is data ownership — you do not need to worry about a bot service changing its pricing, changing data retention policies, or shutting down [website][4].

---

Deployment reality check

Cially is three components that must all run simultaneously: the Discord bot, the Next.js web app, and PocketBase. Docker is the supported and tested deployment path [README][4].

What you actually need:

• A Linux VPS (low-end is fine — PocketBase is SQLite-backed, memory requirements are modest)
• Docker and docker-compose
• A domain name and reverse proxy (Caddy or nginx) if you want HTTPS access from outside your local network
• A Discord application with a bot token configured in the Discord Developer Portal, with the Message Content Intent enabled (this is a privileged intent requiring manual activation)

The v1.0 announcement was candid about the history: “Docker support is finally working! Huge shoutout to hxck on GitHub for the help!” — meaning Docker was broken or incomplete before v1.0 [4]. The README was also rewritten for the v1.0 release specifically to lower the barrier for non-technical users [4].

What can go sideways:

• If the bot goes offline, the web dashboard continues to display data but loses the ability to resolve user IDs and channel IDs to human-readable names in real time. You may see raw IDs in the interface instead of names.
• Discord’s Message Content Intent is privileged and must be enabled in the developer portal. Skipping this step breaks the bot silently — it connects successfully but doesn’t log messages.
• Version 2.0 is Beta [README]. If you deploy v1.0 (stable) today, the upgrade path to v2.0 may require manual steps — migration documentation was not verified from available sources.
• PocketBase is a single SQLite file. There is no built-in backup tooling. If your VPS goes down without backups, your historical analytics data is gone. This needs to be handled by your own cron job or VPS snapshot policy.
• At 207 stars, community troubleshooting resources are thin. Support goes through the developer’s Discord server [README], which means response time depends entirely on the maintainer’s availability.

XDA’s roundup of self-hosted services worth reconsidering [2] makes a point that applies here: when you run your own stack, you are the IT department. Updates can break things at inconvenient moments, and debugging a three-component system is more work than debugging one.

Realistic time estimate: A developer comfortable with Docker: 1–2 hours to a working instance. A community manager who has never touched a Linux server: one full afternoon, closely following the README. The Discord Intent setup alone surprises many first-timers.

---

Pros and cons

Pros

• Data ownership. Server activity metadata lives in your PocketBase database, on your hardware. No third party sees your community’s patterns [website][4].
• No message content stored. The project actively avoids logging message content by default — only metadata [website]. This is a meaningful privacy distinction.
• Free. No tiers, no limits, no subscription. The cost ceiling is your VPS [website][README].
• PocketBase backend. Single binary, embedded SQLite — no Postgres provisioning, no complex database maintenance [README].
• Per-user analytics. The User Search Page surfaces per-user stats (joins, leaves, message counts, most active channel) that Discord’s native Insights do not provide [4].
• Actively developed. v1.0 shipped stable, v2.0 is in active beta development [README][4].

Cons

• Very small project. 207 GitHub stars. The project’s health depends on the maintainer’s continued interest [merged profile].
• Not OSI open source. CC BY-NC-ND 2.0 bars commercial use and derivative works. You can self-host it; you cannot build a product on top of it or use it commercially [README].
• No managed cloud option. Self-host or nothing. There is no paid cloud version for people who want the features without the infrastructure [website].
• Three-component architecture. Bot, web app, and PocketBase all need to stay running and in sync. More failure surface than a single-container tool [README].
• Feature set is genuinely narrow. No voice analytics, no exports, no alerting, no role breakdowns. This does less than it might appear from the description.
• Version 2.0 is Beta. Current development is pre-release. Stability is not guaranteed [README].
• Minimal community resources. No third-party guides, no YouTube tutorials, no Stack Overflow answers. The only troubleshooting path is the developer’s Discord server [README].
• Commercial use prohibited. If you manage a Discord community for a business, agency, or client, verify whether your use case is commercial under the license terms [README].

---

Who should use this / who shouldn’t

Use Cially if:

• You manage a hobbyist or creator Discord community and want real, per-user analytics without paying a monthly bot subscription.
• Data sovereignty genuinely matters — you don’t want your community’s activity patterns flowing through MEE6’s or Carl-bot’s servers.
• You’re comfortable running Docker on a VPS and can handle a three-component setup.
• You want the User Search Page specifically — Discord gives you nothing like it natively.

Skip it (use Discord native Insights) if:

• Your server has 500+ members and top-level trends are all you need — Discord’s built-in Insights is free and requires zero infrastructure.
• You don’t want to maintain a self-hosted stack. If a bot update at 2am is not your problem, keep it that way.

Skip it (use MEE6 or Carl-bot) if:

• You want analytics bundled with moderation, leveling, and other bot features under a single subscription.
• You need commercial use rights — the license prohibits this.
• You want a support team, not a developer Discord.

Skip it entirely if:

• You’re building a product or service that includes Discord analytics. CC BY-NC-ND 2.0 bars commercial use and derivative works. You’d need to build your own solution or find a project with an MIT or Apache 2.0 license [README].

---

Alternatives worth considering

From the AlternativeTo listing [3] and the broader Discord analytics space:

• MEE6 — The largest all-in-one Discord bot. Analytics (leaderboards, activity) are part of its premium tier. Closed source, proprietary SaaS. If you already pay for MEE6 for other features, the analytics may be sufficient [3].
• Carl-bot — Extensive logging and some analytics, freemium model. Larger user base, more documentation, better community support than Cially [3].
• YAGPDB — Open source (MIT), general-purpose bot with solid logging. Less analytics-focused than Cially but a more established project with genuine OSI-compliant open source licensing [3].
• Discord Server Insights (native) — Free, no setup, available to 500+ member servers. Top-level only, no user-level data, no history export.
• Statbot — A dedicated Discord analytics bot (not listed in the provided alternatives but a direct category competitor). SaaS model with free and paid tiers, no self-hosting. Specific pricing not available from provided sources; worth researching independently.
• Pro Bot — Free, proprietary, multi-purpose bot with some stats features. No self-hosting option [3].

For most community managers, the real choice is Cially (self-hosted, free, your data) vs. a bot analytics tier ($6–12/mo, their servers). The decision comes down to how much the data sovereignty argument is worth to you and how comfortable you are with Docker.

---

Bottom line

Cially does one specific thing: it gives Discord community managers detailed server analytics in a self-hosted dashboard that keeps their data off third-party servers. For a technically capable community manager who is already frustrated paying a bot subscription for analytics, the value proposition is clear. The privacy claim is honest, PocketBase is a sensible backend choice, and the User Search Page offers real insight that Discord doesn’t surface natively.

The limits are equally real. At 207 stars and with version 2.0 still in beta, this is a small project carrying meaningful infrastructure trust. The license prohibits commercial use in ways that matter if you’re running a business Discord. And a three-component architecture means more to maintain than the “simple dashboard” framing implies. If you’re technical, privacy-minded, and managing a non-commercial community, Cially is worth an afternoon. If you need commercial use rights, enterprise support, or a single-click deployment, look at the alternatives.

---

Sources

2. Dhruv Bhutani, XDA Developers — “4 self-hosted services I regret trying to rely on” (Sep 13, 2025). https://www.xda-developers.com/4-self-hosted-services-i-regret-trying-to-rely-on/
3. AlternativeTo — “Cially Alternatives: Top 7 Discord Bots & Similar Apps” (updated May 18, 2025). https://alternativeto.net/software/cially/
4. HomeworkExtreme9516 (Cially developer), r/selfhosted — “Cially v1.0 is out! We are out of BETA - The Best Discord Insights Tool”. reddit.com. https://www.reddit.com/r/selfhosted/comments/1kprwph/cially_v10_is_out_we_are_out_of_beta_the_best/

Primary sources:

• GitHub repository and README: https://github.com/cially/cially (207 stars, CC BY-NC-ND 2.0 license)
• Official website: https://cially.org
• Documentation: https://cially.org/guide/1-introduction/features/