What does “Native Federation” mean, and how is it different from the previous federation model?
“Native Federation” means that federation is built directly into Rocket.Chat.
In earlier versions, federation relied on an external Matrix homeserver (such as Synapse) running separately from Rocket.Chat. This required additional services, separate configuration, and extra infrastructure.
With Native Federation:
The Matrix homeserver runs inside Rocket.Chat
No external Synapse server is required
No additional database or standalone components are needed
In short, Native Federation simplifies deployment and reduces operational complexity compared to the previous federation model.
Is Federation generally available (GA)?
Federation is currently in its final stability and performance tuning phase (Beta). It is suitable for evaluation and non-critical use cases. For mission-critical workloads, we recommend waiting until final stabilization is complete.
Does Federation require an external homeserver like Synapse?
No. Federation runs directly inside Rocket.Chat as an embedded Matrix homeserver. No external services or databases are required.
What version of the Matrix protocol is supported?
Rocket.Chat currently provides reliable compatibility with Matrix v1.1, with ongoing improvements for future versions.
Is Federation included in all plans?
No. Federation is an Enterprise feature and requires an active Enterprise license with the Federation add-on enabled.
What happens if my Enterprise license expires or Federation is disabled?
If the license expires or Federation is disabled:
Existing federated rooms become read-only.
Users can view message history.
New messages cannot be sent.
Invitations cannot be created or accepted.
Once the license is restored or Federation is re-enabled, normal operation resumes automatically.
Are external users “copied” into my workspace?
No. Federation synchronizes identities and membership events between homeservers. Remote users remain hosted on their own servers.
Do federated users count toward my license seats?
No. Only users created in your local workspace count toward your licensed seats.
Are end-to-end encrypted rooms supported?
End-to-end encryption for federated communication is not supported.
Users may be allowed to join encrypted rooms hosted on other Matrix servers, but Rocket.Chat cannot decrypt or index encrypted content exchanged there.
Are read receipts supported in federated rooms?
No. Read receipts are intentionally suppressed in federated rooms to prevent inconsistent indicators across servers.
Are voice and video calls supported in federated rooms?
No. Audio and video calling are currently not supported in federated rooms.
Can I change roles in a federated room?
Yes. Owners can assign or remove room-level roles (Owner, Moderator, Member).
Role changes are synchronized across participating servers.
Global server roles (such as Admin) do not override federated room-level roles.
What happens if the last Owner leaves a federated room?
The last remaining Owner cannot remove themselves or be removed until a new Owner is assigned.
Can I block specific external domains from federating with my workspace?
Yes. Administrators can configure a Domain Allow List to restrict federation to specific domains.