Spacebar

Open-source Discord-compatible chat, honestly reviewed. No marketing fluff, just what you actually get when you try to run it.

TL;DR

• What it is: An AGPL-3.0 reverse engineering and re-implementation of Discord’s full API stack — server, gateway, and client. You run your own Discord-compatible server that existing Discord bots and modified clients can connect to [README][1].
• Who it’s for: Privacy-conscious developers and communities who want data sovereignty over their Discord-style communication. Emphatically not for non-technical users [1][4].
• Current state: Alpha. The project itself warns “do not use as a daily driver.” Voice and video are broken. The official client is deprecated; the replacement alpha client hasn’t shipped a release in two years [2][3][4].
• Cost savings: The software is free. Hosting runs $10–50/month depending on community size. Discord is free — so the “savings” here are measured in privacy and control, not dollars [1].
• Key strength: Near-complete Discord API compatibility means your existing bots and workflows port over without rewriting anything [1][2].
• Key weakness: This is genuinely unfinished software. No voice. No video. Rough documentation. Client situation is a mess. Setup took a first-timer 3+ hours and required poking at SQL directly [3][4].

---

What is Spacebar

Spacebar (formerly Fosscord) is a free, open-source re-implementation of Discord’s entire stack — not just a “Discord-inspired” platform, but a ground-up reverse engineering of Discord’s actual REST API and WebSocket gateway protocol. The goal is a drop-in replacement you host yourself, where Discord bots work with minimal changes and Discord-compatible clients can connect to your instance instead of Discord’s servers [README][1].

The project is structured as multiple repositories: a server handling API, gateway, CDN, WebRTC, and admin dashboard; a web client; and documentation. The organization lives at github.com/spacebarchat and the main repo sits at 6,613 GitHub stars [merged profile][README].

The appeal is specific: if you run a Discord community and the core problems are Discord’s data practices, ToS enforcement, or the existential risk of Discord shutting down or banning your server, Spacebar theoretically lets you take that same toolset and infrastructure in-house. Your bots keep working. Your members don’t need to learn a new interface — the UI is intentionally Discord-identical [1][2].

The caveat you need to read before going further: the project self-describes as alpha and explicitly advises against using it as a daily driver. This isn’t false modesty — it reflects real gaps in functionality, especially around voice and video [3][4].

---

Why People Choose It

The honest answer from the community threads is: most people evaluate it, hit the limitations, and don’t choose it — yet.

The r/selfhosted post sharing Spacebar [2] drew commentary that captures the state accurately. One user who set it up wrote: “Technically it’s running. But all the settings are in the fucking SQL db, and I know fuck all about SQL other than drop tables is funny meme from xkcd.” The same user noted: “there is effectively no client. I mean, there are two official ones - the deprecated one, and the alpha one, and the alpha one has a total of 4 releases with the newest being two years ago. How do you deprecate a client when the server is still in alpha?” [4]

The Lemmy discussion [3] produced a comment that became the thread summary for many: “If only it didn’t looked like a 20 year old software” — applied to alternatives — and then a harder landing when someone linked to the official FAQ: “Currently there is no voice or video support in any Spacebar instance. This is a very difficult feature to get working, especially given that we must implement it the exact same way as Discord.com for client compatibility.” The reply: “Discuss without voice, might as well use IRC.” [3]

The ReviewNexa reviewer [1] is the most thorough advocate. After a 90-day deployment serving a 200+ member developer community, their conclusion is positive — but they’re explicitly a technical user who chose a $20/month DigitalOcean droplet and spent 45 minutes on initial setup. The profile they describe as a fit: developer communities, privacy-conscious organizations, gaming guilds worried about Discord ToS, educational institutions needing GDPR compliance [1].

What nobody in any of these threads is describing is a non-technical founder picking Spacebar to replace a paid team communication tool. That’s not who this is for right now.

---

Features

What’s working:

• Self-hostable backend with full Docker Compose setup [README][1]
• Discord-compatible REST API and WebSocket gateway (work in progress, but functional for core operations) [README][2]
• User accounts and authentication [README][2]
• Guilds (servers), text channels, messaging [README][2]
• Roles and permissions [README][2]
• Bot invites — existing Discord bots connect with minimal changes [README][1][2]
• Webhooks [README]
• Web front-end [README][2]
• Plugin system (cross-platform, described as secure) [README]
• Theme system with design editor [README]
• Configurable limits and settings [README]
• Admin dashboard [README]

What’s not working or incomplete:

• Voice and video: broken. The official FAQ is explicit — no voice or video support in any Spacebar instance. WebRTC reimplementation is unsolved and they’re actively looking for contributors who can help [3][4].
• Screen sharing: non-functional — listed as a known gap [2].
• E2EE: not implemented [2].
• Discord API reimplementation: incomplete — ongoing work [2].
• Client situation: unstable. The original web client is deprecated. The replacement alpha client shipped four releases, with the most recent two years ago [4].

Configuration reality: Settings live in the PostgreSQL database, not in a config file. For anyone without SQL fluency, this creates a barrier to customization that you don’t encounter with most self-hosted tools [4].

---

Pricing: SaaS vs Self-Hosted Math

Discord is free. This changes the cost calculus entirely compared to most tools on this site.

You’re not switching to Spacebar to save money — you’re switching to gain control. The self-hosting cost is:

• Software license: $0 (AGPL-3.0) [README]
• Minimum VPS: $10–20/month (2GB RAM, 2 CPU cores required for a small community) [1]
• At scale (200+ members with active voice use): $20–50/month [1]
• Your time: Significant. 45 minutes if you’re technical and everything goes right [1]. 3+ hours if you hit the SQL configuration wall [4].

The Slack or Teams comparison is more interesting. If your team is paying $7–12/user/month on Slack, and you’re 20 people, that’s $140–240/month. A $20 VPS with Spacebar drops that to $20/month — but only once voice is stable enough to be usable. Until then, you’d still need a voice solution alongside it.

The honest pitch for self-hosting Spacebar isn’t cost reduction. It’s: your data stays on your server, your community can’t be suspended or banned by a corporation, and you’re not feeding Discord’s ad and surveillance infrastructure [1][2].

---

Deployment Reality Check

The ReviewNexa reviewer [1] — who is a technical writer with experience deploying 50+ self-hosted solutions — spent 45 minutes on a fresh DigitalOcean droplet following the Docker Compose guide. Their minimum spec recommendation: 2GB RAM, 2 CPU cores, 20GB storage.

The more representative experience comes from the programming.dev thread [4], where a user spent 3 hours and described the documentation as “rough — if rough was falling 4 stories into a bed of poisonous cacti.” The specific blocker: settings configuration via SQL, with no clear documentation on which values to set and how.

What you actually need:

• A Linux VPS (Ubuntu 22.04 or similar)
• Docker and docker-compose
• A domain name with DNS pointing at your server
• A reverse proxy (Caddy or nginx) for HTTPS
• PostgreSQL (bundled in docker-compose)
• Redis (bundled)
• Basic SQL literacy for configuration
• Patience with documentation that’s still being written

What can go sideways:

• The client you deploy alongside the server is either deprecated or an alpha with a two-year-old last release. You’re recommending your community use software that’s visibly abandoned on the frontend side [4].
• Voice will not work. If any of your members expect it, you’ll be explaining why immediately [3].
• Docs are inconsistent. The structure has improved but there are gaps, and some guides assume context the reader doesn’t have [4].
• No one-click installers. No Yunohost package as of this writing. No Coolify template. This is manual Docker work [1].

Realistic time estimate for a confident Linux user: 45–90 minutes to a working text-only instance. For anyone newer to self-hosting: half a day, and you’ll likely need to ask for help in the Spacebar Discord or Matrix channel.

---

Pros and Cons

Pros

• Discord API compatibility. The core differentiator. Existing bots work. Members connecting via Discord clients (with instance modification) see familiar UI [1][2]. If you’re migrating a community with tooling built around Discord’s API, this is the only self-hosted project that preserves that.
• AGPL-3.0 license. Genuinely free and open source. You can audit the code, fork it, modify it. The license does require derivatives to be open source, which matters if you’re building a product on top [README].
• Decentralized design. No single point of failure by design. The project explicitly targets federation concerns [README].
• Plugin and theme system. Extensibility built into the architecture, not bolted on [README].
• 90-day real-world validation. At least one serious reviewer [1] ran a 200+ member community on it for three months and calls it viable for the right audience.
• Active community. Discord guild and Matrix channel for support. GitHub issues are labeled for onboarding contributors [README][2].

Cons

• Alpha software. Do not use as a daily driver. The project says this itself. This is not a production-ready platform [1][2][4].
• Voice and video: completely absent. For a Discord replacement, this is a fundamental missing feature. There is no timeline given in the public documentation [3][4].
• Client is in a worse state than the server. The alpha web client’s last release was two years ago. The deprecated client is what most people end up using [4].
• Documentation is rough. Multiple community members in separate threads independently describe it the same way. Configuration via SQL is underdocumented [4].
• Very small community relative to alternatives. 6,613 GitHub stars versus n8n’s 100K+, Matrix’s decade of adoption, or Rocket.Chat’s enterprise footprint [merged profile].
• No enterprise features. No SSO, no audit logs, no SCIM — not because they’re gated behind a commercial tier, but because they haven’t been built yet [README].
• AI contributions explicitly unwelcome. The project’s contribution policy rejects AI-generated code [2]. This is an ethos statement, but it’s worth noting as a signal about development pace.
• Settings in SQL, not config files. Makes ongoing configuration management harder than it needs to be [4].

---

Who Should Use This / Who Shouldn’t

Use Spacebar if:

• You’re a developer or technical team lead who wants data sovereignty over Discord-style communication and you’re comfortable with Docker, SQL, and Linux administration.
• You’re running a community where voice isn’t a requirement right now — text-only Discord functionality is sufficient for your use case.
• You’re a contributor looking to help build something interesting. The project has clear “good first issue” labels and explicit asks for WebRTC expertise [2].
• You’re doing a proof-of-concept deployment to evaluate long-term migration before the project matures.

Skip it if:

• Your community uses voice channels. At all. Voice doesn’t work [3][4].
• You’re a non-technical founder who needs something running reliably this week.
• You want software your members can just use without understanding it’s alpha.
• You’re evaluating this for a business-critical communication channel.
• Your tolerance for hitting documentation gaps and debugging SQL is low [4].

What to use instead:

• Matrix + Element: If you want genuinely production-ready self-hosted chat with voice support, federation, and active enterprise adoption, Matrix is the answer. Different UX from Discord, but it works.
• Rocket.Chat: Full-featured, production-ready, self-hostable team communication with voice and video. Not Discord-compatible, but actually finished software.
• Revolt: Another Discord-alternative with self-hosting support and a cleaner UI than most, without the “we reverse-engineered Discord’s API” complexity.

---

Alternatives Worth Considering

• Matrix + Element — The production-grade answer. Federated, E2EE, voice/video work, mobile apps are polished. Steep learning curve for migration but genuinely done. The UX diverges from Discord, which matters for communities with non-technical members.
• Revolt — Open-source Discord alternative with its own API (not Discord-compatible). Cleaner implementation, working voice/video, more active client development. Less compatibility for existing bots.
• Rocket.Chat — Enterprise-oriented self-hosted messaging. Full voice, video, screen sharing. More Slack-like than Discord-like. Free community edition, paid enterprise tier for SSO and compliance features.
• Zulip — Topic-threaded chat model, genuinely different from Discord but popular with developer teams. Self-hostable, production-ready, FOSS.
• Mumble — If voice is the entire point and text chat is secondary, Mumble is older than Discord and does voice better than most. No Discord API compatibility whatsoever.
• Discord itself — Free, works, has everything. The reason to leave is policy and data concerns, not price.

---

Bottom Line

Spacebar is an interesting technical project solving a hard problem — reverse-engineering Discord’s API to give communities a self-hosted escape route. The architecture is sound and the Discord-compatibility angle is genuinely unique. But it’s alpha software with broken voice, an abandoned-looking client, and documentation that sends new users directly into a SQL database they weren’t expecting.

If you’re a developer who wants to contribute to something with clear value, or you want to run a text-only community and have the patience to work through rough edges, it’s worth an afternoon. If you’re a founder looking for reliable team communication or a community manager whose members expect voice channels, this isn’t ready. Come back in 12–18 months and check if voice has shipped.

The self-hosted Discord space has real production-ready options — Matrix, Revolt, Rocket.Chat. Spacebar’s distinctive value (existing bot compatibility, familiar UI) will matter a great deal once it’s stable. It’s just not there yet.

---

Sources

1. ReviewNexa — “SpacebarChat Review 2026: The Ultimate Self-Hosted Discord Alternative That Puts Privacy First”. https://reviewnexa.com/spacebarchat-review/
2. r/selfhosted (Reddit) — “Spacebar – Reverse Engineered Discord-Compatible Chat Platform (Alpha)”. https://www.reddit.com/r/selfhosted/comments/1r1mjua/spacebar_reverse_engineered_discordcompatible/
3. Lemmy.World — “SpacebarChat - a selfhosted, Discord-compatible communication platform”. https://lemmy.world/post/20165821
4. programming.dev — “GitHub - spacebarchat/spacebarchat: 📬 Spacebar is a free open source selfhostable discord compatible communication platform”. https://programming.dev/post/45559495

Primary sources:

• GitHub organization and README: https://github.com/spacebarchat/spacebarchat (6,613 stars, AGPL-3.0 license)
• Official website: https://spacebar.chat
• Official documentation: https://docs.spacebar.chat