An open communication protocol — not a company, not a platform, not a data broker.
Six properties that define what Matrix is and why it matters.
Matrix is an open standard for real-time communication — not a product owned by a company. Anyone can run a server, build a client, or contribute to the spec. No central authority. No gatekeeper.
Like email, Matrix servers talk to each other. A user on Badlands can message a user on matrix.org. You're not locked into one provider — your identity works across the entire network.
Messages are encrypted before they leave your device. Even server operators cannot read encrypted conversations — that's not policy, it's math. Keys live on your devices, not on the server.
Platforms monetize users. Matrix empowers operators. Badlands runs its own hardware — no tracking, no ads, no investors to answer to. We're accountable to the people using it, not to a board.
Your Matrix address works like an email address — it's yours. If Badlands ever shuts down, you migrate to another homeserver and keep your contacts and rooms. No platform lock-in.
The Matrix specification, Synapse homeserver, Element clients — all open source. The code is auditable, forkable, and not dependent on any single organization's continued existence.
The mechanics behind federated, encrypted communication.
Your account lives on a homeserver — in this case, Badlands. Your address becomes @you:badlands.pw. No email required. No phone. Just a username and password.
When you join a room with users from other servers, your homeserver and theirs exchange encrypted room events directly over HTTPS. The servers verify each other using signed cryptographic keys — no central coordinator needed.
In E2EE rooms, your client encrypts the message using session keys before it ever reaches the server. The server forwards ciphertext. Only devices holding the right keys — devices you've verified — can decrypt it.
Modern platforms demand identity verification, behavioral profiling, and ongoing data extraction. They grow by making themselves indispensable and then monetizing the dependency. We rejected that model entirely.
Matrix gives us a protocol — not a product. Infrastructure we control, not infrastructure we rent from a company that can change the terms, raise the price, or decide our community doesn't belong. When we run Synapse, we run the full stack. There's no upstream platform that can deplatform us.
The protocol is also designed for permanence. Rooms exist across multiple servers simultaneously. If any one server goes offline, the room survives on the others. No single point of failure. No single point of control.
Protocol over platform. Privacy over convenience. Infrastructure over dependency. That's why we're here.
What's out there beyond Badlands.
Synapse (Python) is the reference Matrix homeserver — battle-tested and feature-complete. Dendrite (Go) is a lighter alternative still maturing. Badlands runs Synapse via the Element Server Suite (ESS) Helm chart on K3s.
Element (web, iOS, Android), Element X (next-gen), Cinny (web), FluffyChat (mobile), Schildichat, Fractal (GNOME), Nheko (desktop). All connect to the same homeserver. You pick the interface.
Matrix can bridge to Discord, Slack, Telegram, IRC, WhatsApp, and more via Mautrix and other bridge servers. You can run a Matrix room that mirrors a Discord channel — useful for gradual community migrations.
Matrix supports voice and video calls via Element Call, powered by LiveKit SFU. Badlands runs its own LiveKit instance — calls never route through a third party. Group calls and 1:1 both supported.
Matrix has a growing bot ecosystem via Maubot, NioBot, and the matrix-bot-sdk. Bots live in rooms like any other user and respond to commands or events. The API is fully open and documented.
The Matrix network has millions of users across thousands of homeservers. Public rooms on matrix.org cover gaming, tech, privacy, open source, and more — all reachable from your Badlands account.
Registration is open. No email. No verification. 60 seconds.
