One core.
Four editions.

Distribution point for the MF Core Matrix homeserver: source code, configured builds and hardened OS images. Every edition ships the same core — a single static Go binary — as a configuration profile, never a fork.

~85 MB RSS under sustained load 1 static binary + PostgreSQL content encrypted at rest interop verified against Synapse room versions 10 / 11 / 12

The core

MF Core homeserver

The engine behind every edition, and the configuration running the matrix.family production homeserver. What is on record from production and the shared test cluster:

Small and steady

measured, not promised

~85 MB RSS flat through a mixed-workload load run, no leak trend
~290 operations per second on one node with zero errors
recovery drills on record: database restart under load, process kill, federation partition with queue catch-up

Interop as a discipline

verified against the reference stack

Complement conformance runs with a tracked baseline diff
federated cross-signing with key rotation, verified by an external SDK regression lane — including production
redactions (MSC2176), bundled aggregations (MSC2675), knock, server ACLs in both directions

Secure by default

privacy is a configuration default

message content encrypted at rest in the database
invite-token registration out of the box
delegated authentication (MSC3861) proven with matrix-authentication-service

The line

Editions are profiles, not forks

One codebase, one release train, one test surface. A fix lands in every edition in the same release.

Community

general-purpose Matrix

open federation, standard Matrix clients
source and configured builds from this site
runs matrix.family in production

Home

a homeserver at home

one-command install or a ready OS image
PostgreSQL provisioned and tuned automatically
automatic TLS, scheduled backups, unattended security updates
optional closed federation for a family circle

Enterprise

organisational control

SSO via delegated authentication (LDAP/AD through the IdP)
audit logs, retention policies, SIEM-ready structured logs
closed or allowlisted federation
air-gapped installs with an offline update mirror

Numeric

closed number network

identity is a number — no federation, by definition
hosted network on our infrastructure or a private one on yours
paired with a dedicated phone-style client

Numeric edition

A closed network where your address is a number

Numbers are standard Matrix IDs under the hood (@527752:…), so E2EE, calls and device verification are inherited from the core — while the client shows a dialer, contacts and a call log. Networks never interconnect: the hosted network and every private deployment are separate universes.

Diagram: hosted numeric network and a private customer network with no interconnect between them

52-77-52

mirrored — premium

777-000

repeating — premium

36-41-98

standard pool

10-02

private network, short plan

Mockup of the phone-style Numeric client with a dial pad and an E2EE call to number 52-77-52

server profile — numeric, closed

# numeric-closed.yaml (profile excerpt)
federation:
  enabled: false          # no 8448, no keys, no inbound PDUs
registration:
  mode: number_pool
  number_length: 6
  reserved_ranges: ["000000-000999"]
directory:
  lookup: exact_number
  visibility: opt_in      # hosted mode; complete in private mode

what a number is underneath

# the client shows: 52-77-52
# the protocol sees a standard Matrix ID:
@527752:numeric.example

# so everything is inherited from the core:
#  - E2EE direct messages and calls (TURN inside the network)
#  - cross-signing and device verification
#  - push via self-hosted UnifiedPush - no third-party push

Delivery

MF OS — a hardened image, not a fifth product

Home, Enterprise and private Numeric deployments ship as an Ubuntu-based image with everything unrelated to the server removed. Two update sources, both accountable: Ubuntu's security repository for the OS, signed MF Core releases for the server.

surface of a private numeric deployment

$ ss -tln
State   Local Address:Port
LISTEN  0.0.0.0:443    # clients (TLS)
LISTEN  0.0.0.0:3478   # TURN
# that is the whole exposed surface

update policy

$ cat /etc/apt/apt.conf.d/50unattended-upgrades
Unattended-Upgrade::Allowed-Origins {
    "Ubuntu jammy-security";  # OS: Ubuntu only
};
# mf-core binary: signed releases from core.matrix.family
# air-gapped variant: offline mirror of both sources

At a glance

Feature × edition

The full matrix lives in the product line documentation.

Capability	Community	Home	Enterprise	Numeric
Open federation	yes	optional	allowlist	no — by design
Registration	token / open	token	SSO / IdP	number pool
E2EE + cross-signing	yes	yes	yes	yes
Audit / retention	basic	basic	full	full
OS image delivery	optional	primary	primary	primary (private)
Air-gapped install	no	no	yes	yes (private)
Phone-style client	—	—	—	primary

One core.Four editions.