Matrix
Before you install
Section titled “Before you install”These answers used to sit on this app’s store listing. They moved here on 2026-08-17: a shopper deciding whether to install is not reading six hundred words of Q&A, and the listing page is the pitch. The knowledge is no less true for being off the storefront: it is the part you want before you commit, which is what a guide is for.
Do I need object storage?
Section titled “Do I need object storage?”No. Synapse keeps media on the stack’s own volume. Bind the optional s3 plug and the s3-media-offload job moves media into a bucket, with the volume kept as a cache. SHC ships no S3 server of its own, so the bucket lives at a hosted provider behind an s3 connection. See Object storage for apps.
Can I change the server name later?
Section titled “Can I change the server name later?”No, and that is Matrix rather than this package. Your server name is written into every user id and every event the homeserver creates, so pick the domain you intend to keep before the first account exists.
Do I have to use Keycloak?
Section titled “Do I have to use Keycloak?”No. MAS registers and authenticates accounts perfectly well on its own. If you do bind Keycloak you can also make it the only login path, and the package states plainly that doing so leaves no local escape hatch: an unreachable identity provider locks out everyone including admins, and the way back is a host-side variable change.
Does it federate?
Section titled “Does it federate?”Synapse federates like any homeserver. Whether the rest of the network can reach yours is a matter of what you choose to publish at the edge, so a homeserver meant to stay inside the estate stays inside it.
Where do errors go?
Section titled “Where do errors go?”Nowhere, unless you attach the error tracker in this catalogue. Bind it and the package seals a per-deployment ingest key for this homeserver alone, which is also the revocation handle. With nothing bound, no reporting block is written at all.