Glossary
Federated Messaging
A model where independent messaging servers, each run by a different operator, interconnect over a shared protocol so users on one server can message users on another, the way email works across providers.
General definition
Federated messaging is an architecture in which many independently operated servers speak a common protocol and route messages to one another, so a user on one server can talk to a user on a completely different server. It is the opposite of a closed, single-operator silo. Email is the classic federated system, and XMPP and Matrix bring the same idea to real-time chat.
- Each operator controls its own server, users and data
- Servers exchange messages over a shared, open protocol
- Identities are usually addressed like user@domain
- No single company owns the whole network
Federation trades some central control for openness, reach and resilience. It also raises questions of trust, spam control and cross-domain security that closed apps handle internally, which is why deployments choose deliberately whether and with whom to federate.
In the Ethora ecosystem
Ethora is built on XMPP, the most widely deployed open messaging standard, which is inherently federatable. An Ethora deployment can therefore run as an isolated, self-contained instance for full data control, or interconnect outward where a federated model fits the use case. The Chat SDK exposes messaging without you having to operate federation by hand.
For regulated and enterprise buyers the point is choice: run a private, self-hosted server with no external federation for maximum isolation, or connect deliberately. You own the server, the users and the data either way.
