Fit
SimpleX Chat is worth evaluating when contact graph privacy is more important than familiar phone-number discovery.
signal alternative
When phone-number identity is the risk, compare the whole workflow.
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
Users must learn invitations, addresses, device-owned data, and operational recovery boundaries.
Migration path
Start with a pilot group, document connection rituals, then decide whether business addresses or relays are needed.
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. |