[Concord](https://concord.im) is live. It's the production implementation of the Rising Sun communication protocol — and the first place real users can experience the model: consent-based history, spatial identity, E2E encryption with perfect forward secrecy.
What Concord Is
Concord is messaging where:
- >You own your history. Receipts are cryptographic and opt-in. There is no provider with a copy of your conversations.
- >Identity is spatial, not platform-issued. Your identity derives from a memory arrangement only you can reconstruct — the same primitive that powers [Password Palace](/portfolio/password-palace).
- >Forward secrecy is the default. Compromise a session and you don't compromise the past.
- >Multi-party coordination is cryptographic. Group threads, multi-sig actions, conditional reveals — composed from the same primitives as the rest of the portfolio.
"An internet for humans and people alike"
The tagline is deliberate. Concord is built for human-to-human conversation, but the protocol doesn't care whether the other party is a person or an AI agent. Agents using the Concord protocol carry verifiable identity through [Entity Identity](/portfolio/entity-identity), and the conversation history is owned the same way.
Why It Took This Long
The Rising Sun protocol was first sketched 18 months ago. Shipping a production implementation meant landing the cryptographic primitives (ZKFS, Entity Identity, perfect forward secrecy session handling), the identity layer (spatial memory + ZK proofs), and the UX that doesn't make any of that visible. Concord is that landing.
Try It
[concord.im](https://concord.im) is open for beta. Bring a peer, install the client, derive your spatial identity, send a message that no one but the two of you can ever read again.