MEETER / DOCSTechnical reference for IT and developers. The business overview is in the company documentation.
Protocol · overview
Meeter protocol
The protocol describes how employees sign in with SIWE or a corporate ID, how guests use a signed invitation, and how clients exchange encrypted messages. This is the public overview; technical details are in contract v1.
Status: public beta; technical reference for IT. Updated 05.11.2026.
What the protocol provides
- Employee sign-in. SIWE or a corporate ID. No separate password or email.
- Guests. A signed invitation link; no wallet required.
- App permissions. A third-party app receives only the actions explicitly granted to it and cannot reuse your session as its own.
- Encrypted messages. The server relays encrypted envelopes and does not read the content.
- Rooms and media. Meetings and media use separate keys and admission rules.
- Explicit versions. Breaking changes ship in a new version instead of breaking current clients.
What the server sees
The server sees employee wallet addresses, guest roles, time, room composition and technical connection parameters. Message and media content in an encrypted room is not available to it. Metadata is data too: the protocol does not pretend the server is completely blind.
What to know
- The protocol and specification are a draft. The independent implementation is not complete.
- No external audit has been performed. Internal reviews do not replace an audit.
- Technical details are not hidden; they are separated from the public overview.
Documents
- Technical contract v1 — sign-in, permissions, messaging and versions.
- End-to-end encryption — what is protected and where the limits are.
- E2EE v1 — technical specification — keys, envelopes and media.
- OpenAPI v1 · AsyncAPI v1
- Security policy · Documentation