Fit
SimpleX Chat is relevant when teams want communication without a shared namespace or reusable public identity.
matrix alternative
If federated IDs are too visible, plan the alternative with eyes open.
Use the planner to turn upstream SimpleX Chat concepts into a concrete rollout, support, relay, and data-boundary decision.
Unofficial boundary
AGPL-3.0 source
v6.5.5 release noted
Workflow
What this page helps decide.
Tradeoff
Matrix-style federation can be easier to discover and administer; SimpleX changes discovery and recovery assumptions.
Planner output
The paid export maps invite flows, relay posture, group controls, and user-support scripts for a pilot.
Decision matrix
What the planner checks before a rollout.
| Area | Question | Planner output |
|---|---|---|
| Identifiers | How will users connect without phone numbers, handles, or global IDs? | Invitation, address, and group workflow map. |
| Relays | Do preset servers satisfy the pilot, or does the team need self-hosted SMP relays? | Relay posture, domain checklist, and operations tasks. |
| Data ownership | Who owns backups, device loss, passphrases, and profile recovery guidance? | Device-owned data policy and support script. |
| Business support | Does customer support need business addresses, broadcasts, or bot handoff? | Support conversation model and moderation checklist. |