Docs / Alliance (cross-org)

Alliance: what it is

Link independent mustr instances so events and tournaments cross Discord servers, without sharing a bot or a database.

Alliance is how two or more allied orgs — each running their own separate mustr instance, on their own Discord server, with their own bot — connect so announcements, events, and tournaments can cross between them. It's built for orgs that want to collaborate without merging: nobody hands over their bot token, nobody's roster moves into someone else's database.

How it's built

Every allied org keeps its own instance, database, and Discord bot. Instances federate by sending small, sanitized messages to each other over HTTPS, authenticated by a scoped alliance token — not by sharing credentials. When Org A shares an event, A's own bot posts it in A's own server, and A's instance sends the event details to Org B's instance, which posts it in B's own server through B's own bot, labeled "via Org A." The bots never talk to each other directly, and no bot token is ever shared with an ally.

What can be shared

• Test broadcasts — a one-off message to confirm the pipe works.
• Events — an event marked "share with alliance" posts to every ally's Discord too, cancellation included.
• Tournaments — a shared tournament lets allied orgs field their own entrants and follow live standings, while one org still runs the actual bracket. See shared tournaments.

Trust boundary

Anything an ally sends is treated as fully untrusted on arrival: text is stripped of live @everyone/@here/role-mention tokens before it's ever posted to your Discord, so a compromised or careless ally can never ping your members. Every inbound message is also isolated per-ally with a short timeout, so one dead or slow ally's instance never holds up anything else.

Getting started

Pairing with an ally is a one-step connect code — see pairing with an ally.