MatrixEasyMode / Roadmap / v0.1.1
v0.1.1: operational safety and control
The v0.1.1 roadmap moves MatrixEasyMode beyond the initial deployment foundation and further into responsible operation: federation visibility, recovery paths, emergency controls, safer credentials, scoped automation, and stronger admin protection.
The first public MatrixEasyMode release established the deployment foundation. v0.1.1 focuses on what happens after a Matrix + Element stack is already running: how operators understand it, recover it, secure it, and make responsible decisions when something fails.
This is not intended to hide Matrix complexity. MatrixEasyMode should reduce avoidable friction while exposing the details that matter: federation state, recovery paths, administrative access, automation boundaries, and emergency controls.
Operating principle
MatrixEasyMode aims to make Matrix easier to deploy without making it irresponsible to operate. Operators still need to understand the systems they are responsible for. The tooling should help them see failure modes earlier, recover more safely, and operate with more confidence.
Planned scope
What v0.1.1 is expected to focus on
The current scope is intentionally focused on operator-facing control surfaces rather than cosmetic dashboard work.
Federation visibility
Add clearer federation diagnostics so operators can understand whether their homeserver is reachable, discoverable, correctly routed, and behaving as expected with other Matrix servers.
Backup and recovery
Improve backup and restore confidence with clearer recovery paths for stack data, configuration, secrets, media, and identity-sensitive material, with documented expectations around what can and cannot be safely restored.
Emergency lockdown and recovery
Introduce emergency controls for disabling, isolating, or locking down parts of the stack while using recovery-key based access to reduce the risk of permanent operator lockout.
Safer first-login credentials
Support first-login password change flows so generated, temporary, or bootstrap credentials are not left in place longer than necessary.
Scoped API tokens
Provide a controlled way to create API tokens for external tooling, automation, and administrative integrations without relying on overpowered credentials.
Stronger admin account protection
Improve administrative safety around admin login visibility, MFA direction, password recovery, and stronger account workflows for operators responsible for the stack.
Intended operator outcomes
The purpose of this release is not feature count. The purpose is to make the system safer and clearer for the person responsible for operating it.
What this release is not trying to do
v0.1.1 is not about pretending Matrix is simple, removing operator responsibility, or hiding important operational state behind magic buttons. Some details need to remain visible because they affect recovery, security, federation, identity, and trust.
Scope may change
This roadmap describes the current direction for v0.1.1. Some items may move, split, or change as implementation work reveals better release boundaries. The priority is to ship useful, documented, operator-facing improvements rather than preserve a fixed checklist for its own sake.