KantNo support tickets. Just the project, in the open.
Kant doesn't run a helpdesk. The Discord server is where the actual work happens — protocol decisions, relay operations, and the roadmap discussed by the people building and running it.
Protocol & design
Discussion of the X3DH handshake, ratchet behavior, group key handling, and anything that touches the wire format.
Relay operations
Running your own relay, TLS termination, monitoring, and the operational surface — health checks, metrics, registry behavior.
Self-hosting help
Deployment questions for the app, relay, and push-proxy across Docker, bare metal, or desktop/Android builds.
Roadmap & direction
Where the project is headed, what's still placeholder (like the admin plane), and what the community wants prioritized.
Come argue about the ratchet with us.
Whether you're evaluating Kant for a team, running your own relay, or just curious how a serverless messenger actually works end to end — this is the room.
Join the DiscordFree for the use it was built for
The community build is free for personal, academic, journalism, and security research use. It stays that way — the corporate bundle (admin plane, governance tooling) is a separate, paid layer on top, not a paywall on the messenger itself.
Source is open
Read the code, run your own relay, or just verify the claims on this site against the implementation directly.
View source on GitHub