Create and operate chat servers

A chat server in MEM is one managed Matrix homeserver with an Element web client. MEM calls this pair a Runtime Stack or simply a stack.

Outcome

After following this section, you can:

• create a new Matrix + Element stack on an installed MEM platform;
• verify public and internal readiness;
• create the first Matrix administrator and later users;
• inspect services, routes, storage, TURN, federation, and operation history;
• run routine checks and create a backup before risky work;
• remove the active runtime without assuming that retained data was erased.

What belongs to one stack

MEM creates and records a stack-scoped Matrix identity, Synapse configuration, Element configuration, Matrix and Element containers, a PostgreSQL database and role, filesystem storage, Nginx Proxy Manager routes, secrets, readiness evidence, and operation history.

Platform services such as PostgreSQL, Nginx Proxy Manager, and coturn are shared. Matrix users, rooms, messages, media, federation policy, and most runtime evidence belong to the individual stack.

[!IMPORTANT] Matrix accounts are not MEM Control Plane accounts. A Platform Owner signs in to administer MEM. A Matrix user signs in to Element or another Matrix client.

Recommended first-server sequence

1. Create a chat server.
2. Read the stack workspace and status.
3. Synchronize and create Matrix users.
4. Open Element and sign in with the first Matrix administrator.
5. Review Network and domains, Voice and video, and Federation.
6. Establish a daily operating routine.

Guides in this section

• Create a chat server
• Use the stack workspace
• Manage Matrix users
• Reset passwords and manage account lifecycle
• Inspect network and domains
• Configure voice and video TURN
• Manage federation
• Understand storage and media
• Run daily operations safely
• Remove a chat server
• Troubleshoot a chat server

Backup, restore, migration, and full diagnostics have their own bounded workflows. Use the stack workspace links to enter those workflows rather than treating them as ordinary container operations.