Message Easy Mode / Features
See the Control Plane doing the work
MEM 0.2.0 brings Matrix + Element deployment, diagnostics, recovery, public access, and platform services into one operator-facing Control Plane. These are real product screens, not recreated marketing mockups.
One place to see whether the platform is really ready
MEM brings chat servers, public access, platform services, and recovery coverage into one operator view. The important state is visible without turning the deployment into an opaque appliance.
Create Matrix + Element without hiding the decisions
MEM turns stack creation into a reviewable operator workflow. Choose the friendly identity, keep the technical stack identity explicit, and see the exact Matrix and Element runtime versions before anything is created.
- Matrix and Element are created as one managed stack.
- Public hosts and runtime versions are shown before creation.
- Long-running work is tracked durably by the Control Plane.
See what MEM checked, what it could not prove, and what to do next
A green badge should never be the whole diagnostic story. MEM separates passed checks, unavailable evidence, skipped checks, and recommended actions so operators can understand the boundary of what was actually verified.
- Structured server and runtime checks instead of a black-box success state.
- Unavailable evidence remains visible rather than being silently treated as healthy.
- Recommended actions lead directly into the next operator decision.
Recovery is a workflow you can inspect before you trust it
Backups stay in a catalog with integrity and provenance state, then feed into a durable restore workspace. MEM can restore into an isolated private environment first, verify Synapse health, retain evidence, and only then move toward a public restored server.
Explore backup and restore documentation
A real recovery inventory
Backup identity, integrity, origin, capture time, and restore entrypoints remain visible in one catalog.
Test recovery privately first
Validate the restored database and Synapse runtime before changing public routes or production resources.
Public access stays tied to the certificate and renewal state that makes it work
MEM treats domains, certificates, readiness, and renewal as one operator concern. The main platform domain and its production certificate are visible together instead of being scattered across unrelated tools.
- Main-domain identity and certificate readiness stay explicit.
- Certificate expiry and renewal state remain visible to the operator.
- Public-access changes stay reviewable rather than implicit.
The infrastructure underneath remains visible
Postgres, ingress, and TURN are still real services with real operational boundaries. MEM exposes service-specific runtime and verification state instead of flattening the platform into one generic container list.
- TURN runtime, container state, and functional health are separate signals.
- Ports, relay ranges, public host, and external-IP handling remain inspectable.
- Service checks and maintenance actions stay scoped to the service being operated.
More operator workflows
The visual tour is only part of the Control Plane
MEM also keeps federation, migration, Matrix users, and storage inside the same operator model. Those areas stay explicit without turning this page into a screenshot gallery of every screen.
Federation
Review stack federation posture and supported policy changes.
DocumentationMigration
Move existing deployments through staged evidence and target-side validation.
DocumentationMatrix users
Synchronize the Synapse inventory and manage supported account actions.
DocumentationStorage and media
Review Matrix media and recovery-related storage across managed stacks.
DocumentationThe outcome
Operate the machinery, then get back to the conversation
MEM manages the deployment and operator workflows around Matrix and Element. The people using the system still get the normal Element experience on the Matrix stack you control.
Open foundations
MEM operates the ecosystem instead of replacing it
Matrix, Element, Postgres, and ingress remain recognisable parts of the deployment. MEM adds the operator layer around them rather than turning those foundations into an invisible proprietary box.
Matrix / Synapse
The protocol and homeserver foundation behind the communication environment MEM operates.
Element
The Matrix client MEM deploys alongside Synapse for the normal end-user chat experience.
Postgres
The durable database foundation used by managed Matrix deployments and MEM platform services.
Nginx Proxy Manager
The current ingress foundation MEM integrates with for public routing and certificate-backed exposure.
Clear boundaries
Easier to operate does not have to mean harder to understand
MEM is a Docker-first operator path for smaller self-hosted Matrix deployments. The product is intentionally opinionated about where it helps and what remains part of the underlying ecosystem.
Not a hosted Matrix SaaS
MEM is for operators who want Matrix running on infrastructure they control, not a vendor-hosted communication service.
Not a replacement for Matrix or Element
MEM adds an operator layer around Synapse, Matrix, and Element rather than creating a competing protocol or client ecosystem.
Not a generic Docker control panel
The workflows are deliberately shaped around Matrix deployment, diagnostics, recovery, federation, migration, and lifecycle.
Not fake simplicity
MEM removes avoidable friction while keeping important state, failures, trust boundaries, and recovery decisions visible.