simplex-chat.space

Unofficial hosted planner

Plan a SimpleX Chat rollout without exposing the graph you are trying to protect.

Map invitations, addresses, self-hosted SMP relays, business support, and device-owned data before a team moves sensitive conversations to SimpleX Chat.

View pricing plans Open planner preview Source notes
Unofficial boundary AGPL-3.0 source v6.5.5 release noted
Abstract private relay planner with encrypted message queues across devices and relay nodes.

Usable preview

Rollout risk preview

{
  "status": "ready_for_input",
  "output": "Enter rollout assumptions to preview privacy and relay planning risks."
}

Full export is gated behind pricing and paid access.

Product thesis

Deploy private conversations with a relay plan you can defend.

SimpleX Chat changes the usual messaging assumptions: no global user identifiers, device-owned data, one-time invitations, optional business addresses, and relay choices that need operational thinking.

01

Map contacts

Plan one-time links, optional addresses, groups, customer conversations, and who can invite whom.

02

Choose relays

Decide when preset relays are enough and when a self-hosted SMP relay needs DNS, TLS, Tor, and monitoring.

03

Protect devices

Document passphrases, local database care, device loss, profile ownership, and support boundaries.

04

Gate exports

Preview the plan freely; full exports and policy packs route through pricing before API access.

Trust data ledger

Real source facts, clearly separated from sample output.

15,639GitHub stars collected June 29, 2026
901GitHub forks from the upstream repo
v6.5.5Latest GitHub release observed
AGPL-3.0Code license; upstream graphics not reused
This site uses source facts from the upstream project and deterministic sample planner output. It does not claim SimpleX Chat Ltd endorsement, user counts, revenue, or official download status.

Decision matrix

What the planner checks before a rollout.

AreaQuestionPlanner output
IdentifiersHow will users connect without phone numbers, handles, or global IDs?Invitation, address, and group workflow map.
RelaysDo preset servers satisfy the pilot, or does the team need self-hosted SMP relays?Relay posture, domain checklist, and operations tasks.
Data ownershipWho owns backups, device loss, passphrases, and profile recovery guidance?Device-owned data policy and support script.
Business supportDoes customer support need business addresses, broadcasts, or bot handoff?Support conversation model and moderation checklist.

Popular workflows

Pick the page that matches the decision in front of you.

FAQ and limits

Check non-affiliation, payment, privacy, self-hosting, and data-handling answers.