Open-source project
spacebarchat/spacebarchat avatar
spacebarchat/spacebarchat

Spacebar Chat: an umbrella repository around four projects

📬 Spacebar is a free open source selfhostable discord compatible communication platform

6,728 stars230 forksUnknownAGPL-3.0

At a glance

What is it?
Spacebar's own repository holds branding, instances and a code of conduct, while the API, Gateway, CDN, WebRTC and admin dashboard live in a sibling server repository. The feature claims are confident here. Almost none of the configuration detail is.
Who is it for?
Adopt Spacebar if you want a self-hosted, Discord-compatible server and you are willing to assemble it from sibling repositories rather than download one thing. Do not adopt it on the strength of the feature list alone: decentralization, plugin security and the audit are all asserted here without a version, an auditor's name, or a configuration reference.
Can I use it commercially?
Yes, with strict conditions. AGPL-3.0 is a network copyleft licence: if people use a modified version over a network, for example as a hosted service, you must offer them its source code under the same licence.
Is it still maintained?
Yes. The repository last received commits 30 days ago.
What is it written in?
GitHub does not report a main language for this repository.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • spacebarchat/spacebarchat6,728 ★ · +18
Star history
Repository2026-09-232026-11-15
spacebarchat/spacebarchat6.7k6.7k

18 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

This repository is an umbrella, not the server

The top level of the tree holds almost nothing that runs:

text
branding/
instances/
SECURITY.md
CODE_OF_CONDUCT.md
LICENSE

Everything that does the work lives in sibling repositories, and the project names four of them in its own table. Server is described as the Spacebar API plus Gateway plus CDN server plus WebRTC plus admin dashboard. Client is described as compatible with Spacebar-server and with discord.com. Then there is Docs, and a landing page repository behind spacebar.chat. So a question about runtime behaviour, about what the client actually implements, or about how a voice call is negotiated is a question about another repository entirely, and this README answers none of it.

Discord compatibility is the load-bearing claim

The first property the project lists is Discord compatibility, glossed as being able to use your custom clients and bots with minimal changes. That single line is what separates this from any other self-hosted chat server, because it implies existing tooling keeps working rather than being rewritten. The repository table backs the claim from both ends: the client is described as compatible with discord.com, and the server is described as carrying the API and the Gateway, which is the pair a bot talks to. WebRTC and CDN are listed inside the same server project, so voice and media are in scope rather than bolted on later. What the README does not give you is a protocol version, a compatibility matrix, or a list of which Discord endpoints are implemented.

Decentralized is stated without a topology

Decentralization appears as a bullet with the gloss that there is no abuse of power and no single point of failure. Read strictly, that describes an operator running their own instance rather than a network of instances that talk to each other. Nothing in this repository describes an instance-to-instance protocol, a federation handshake, or a domain-squatting mechanism, and the Server repository is presented as something you host yourself rather than something you join. There is also a quieter consequence of the same bullet: a self-hosted instance with no central abuse desk shifts moderation entirely onto whoever runs it. The README does not say what moderation tooling ships with the server, so that question belongs on your list before an invite link goes out.

Configurable, extendable and themeable, with no reference to any of them

Three bullets promise knobs: configurable, described as being able to configure every aspect and limits to your needs; extendable, described as a secure and cross-platform plugin system; and themeable, described as a cross-platform theme system with a design editor. None of those words is followed by a file name, an environment variable, a manifest format, or a theme schema anywhere in this repository. That is consistent with the layout, since the code lives next door, but it means the evaluation questions people actually have (retention, rate limits, upload ceilings, who may install a plugin) have no answer here.

The security claim names no auditor and no date

The Secure bullet says the project is publicly audited and hosted FOSS software, offered as a transparent foundation in terms of security. The tree does contain a SECURITY.md at the top level, which is where a disclosure process would normally be described, and a CODE_OF_CONDUCT.md for community rules. But the README itself names no auditor, no audit date, no scope and no report, and the file list here contains no audit document. If your decision depends on the audit, the claim has to be traced to whoever performed it.

No releases to pin, and a copyright line that stops at 2024

The repository publishes no GitHub releases at all, and its primary language is not recorded, so there is no tagged version here to deploy and no changelog to diff between upgrades. The last push landed on 2026-10-16 and the repository is not archived, which is a working project rather than a finished one. Contributors are still the stated mechanism: the README says the project is only possible by volunteers, points at a contributing guide, and notes that issues are marked Good first issues for newcomers.

text
https://docs.spacebar.chat/contributing/
https://www.gnu.org/licenses/agpl-3.0.de.html

The license is AGPL-3.0, and the notice says you can redistribute and modify the program under the GNU Affero General Public License version 3, with no warranty.

Where a first-time user is actually sent

Setup guides and further information are pointed at docs.spacebar.chat, and support questions go to the project's Discord guild. That is the whole of the usage guidance in this repository, and there is no command, no compose file and no configuration snippet anywhere in the README. It matches what is present in the tree, but it means the first thing you must do is leave for the docs site and the server repository before anything can run:

text
https://docs.spacebar.chat
https://github.com/spacebarchat/server
https://github.com/spacebarchat/client

The one place this README is self-sufficient is the logo attribution, which credits the current logo and the original logo by name. Everything operational is delegated.

Editorial conclusion

Adopt Spacebar if you want a self-hosted, Discord-compatible server and you are willing to assemble it from sibling repositories rather than download one thing. Do not adopt it on the strength of the feature list alone: decentralization, plugin security and the audit are all asserted here without a version, an auditor's name, or a configuration reference. Before deploying, check the docs site for the real configuration surface, check whether the server repository publishes tagged releases, since this one publishes none, and confirm the audit claim against the SECURITY.md file and whoever performed it.

Frequently asked questions

What is Spacebar Chat?

It is a free, opensource selfhostable Discord-compatible chat, voice and video platform, licensed AGPL-3.0. The project describes it as decentralized, configurable, extendable through a plugin system and themeable through a design editor, with a separate admin dashboard in the server project.

How do I use Spacebar Chat?

Setup guides and further information are at docs.spacebar.chat, and support questions go to the project's Discord guild. This repository only holds branding, instances, a code of conduct and a security policy, so the running software has to be picked up from the separate server and client repositories.

Which repositories make up Spacebar Chat?

The server repository covers the Spacebar API, the Gateway, the CDN server, WebRTC and an admin dashboard. The client repository is described as compatible with Spacebar-server and with discord.com, and there are separate documentation and landing page repositories behind spacebar.chat.

Can I keep using my Discord bots with Spacebar Chat?

Discord compatibility is the first property the project lists, described as using your custom clients and bots with minimal changes. The README names no protocol version and no compatibility matrix, so check your own bots against the server repository before relying on it.

How do I contribute to Spacebar Chat?

The project says it is only possible by volunteers. The contributing guide lives at docs.spacebar.chat/contributing/, and issues are marked as Good first issues for people looking to get started.

Official sources

  1. Issues
  2. License: AGPL-3.0
  3. Project website
  4. README
  5. spacebarchat/spacebarchat on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/spacebarchat-spacebarchat.svg)](https://hysenlabs.com/projects/spacebarchat-spacebarchat)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/spacebarchat-spacebarchat.svg)](https://hysenlabs.com/projects/spacebarchat-spacebarchat)

Was this useful?