Clients
Concord has no reference client and no blessed implementation. These are separate teams building separate applications against the same specification — which is exactly the property that makes the protocol worth anything.
A community created in one client opens in the others. Your identity is a key rather than an account, so it travels with you, and if a client ever disappoints you the community does not go with it.
The full Discord-shaped client
Communities, channels, threads, roles, voice and video, custom emoji and themes, plus a Discord bridge and server import. Armada speaks Concord alongside NIP-29 and Buzz communities, so one key carries you across the ecosystem.
Privacy-first messenger, natively encrypted
A standalone Rust and Tauri messenger built on a Privacy by Principle philosophy: no KYC, no metadata collection, encrypted storage, optional Tor transport, and in-chat mini-apps. Vector co-authored Concord and ships the reference relay dictionary.
A lightweight web client
A Concord community app built on the applesauce Nostr toolkit — a compact, independent implementation that demonstrates how little you need to speak the protocol. Runs entirely in the browser with no backend.
Choosing
Armada is the one to pick if you are replacing Discord outright. It has the full feature surface — threads, voice and video, custom emoji and themes, a Discord bridge and server import — and it speaks other community protocols alongside Concord.
Vector is the one to pick if privacy is the requirement rather than the feature. It is a native application built around encrypted local storage and an optional Tor transport, from the team that co-authored the specification.
Accordion is the one to read if you are implementing Concord yourself. It runs entirely in the browser with no backend, and it demonstrates how little code the protocol actually requires.
Interoperability