About this server
Private, encrypted messaging
under your control
matrix.wyer.io is a self-hosted Matrix homeserver providing end-to-end encrypted
messaging, voice, and video calls — without surveillance, data mining, or third-party
access. Accounts are invite-only and reviewed by an admin before activation.
Built for people who take their privacy seriously.
Who is this for
This server is not a public service. Access is limited to trusted individuals.
People who value privacy
You want a messaging platform where no corporation analyzes your conversations to serve you ads or build a behavioral profile.
Security-conscious users
You want full end-to-end encryption, verified device identity, and a server whose operator you actually know and trust.
Trusted contacts
Accounts are granted by invitation only. If you were given this address, you already have a relationship with the person running this server.
Why request an account
What sets this server apart from consumer messaging platforms.
All messages are encrypted on your device before transmission. The server stores only ciphertext — no one, including the server operator, can read your conversations.
No third-party infrastructure. The server, database, media store, and call relay all run on hardware under direct control. Your data never leaves this stack.
No advertising, no analytics pipelines, no profile building. Access logs are retained only for security purposes and are never shared with any external party.
Every account is manually reviewed and approved by an admin. This keeps the server small, trusted, and free from spam and abuse.
Encrypted real-time calls via a self-hosted media relay. Peer-to-peer when possible; routed through infrastructure under the same direct control when a relay is required.
Use Element X on iOS or Android, Element Desktop on Windows or macOS, or Element Web in your browser. All clients support full E2EE and device cross-signing.
Matrix is an open protocol with a public specification. There is no proprietary lock-in. The encryption primitives are published, audited, and independently verifiable.
Encryption keys can be securely backed up to the server with a passphrase only you know. If you lose a device, your message history remains recoverable without compromise.
System architecture
How your messages travel from device to device.
Internet
Your device
Element client
Reverse proxy
TLS termination
Core services
Homeserver
Matrix protocol
Call relay
Media server
SFU for calls
How end-to-end encryption works
Messages are encrypted before they leave your device. The server never holds plaintext.
Sender
Message encrypted
with recipient key
Double Ratchet / Olm
Encrypted in transit
Recipient
Decrypted only
on recipient device
matrix.wyer.io stores and routes ciphertext only — the server has no access to message content, media files, or call audio and video.
Device verification & cross-signing
How you confirm that the person you're talking to is actually them.
1
Each device generates a unique key pair
When you sign in on a new device, that device creates its own cryptographic identity. Keys never leave the device that created them.
2
Cross-signing links your devices together
You sign each new device with a master key, creating a verifiable chain of trust across all your devices. Other users verify your master key once — not each device separately.
3
Verify contacts with emoji or QR code
A short interactive verification confirms that neither side is being intercepted. Once verified, all future messages are protected against impersonation.
4
Verified sessions are marked in the client
Element displays a shield icon next to verified contacts and sessions. Unverified devices appear with a warning, giving you full visibility of your security posture at all times.
What data this server stores
A transparent breakdown of what exists on the server and what does not.
Message ciphertext
Encrypted message payloads are stored so they can be delivered to offline devices. The content is unreadable without the recipient's private key, which never leaves their device.
Account and device metadata
Your username, display name, and the list of devices associated with your account are stored. Device names are set by you and visible to your contacts.
Encrypted media
Images, files, and voice messages uploaded in E2EE rooms are stored encrypted. The server cannot read or preview their content.
Message content — not accessible
Plaintext message content is never stored. Decryption only happens on your device using keys that exist exclusively on your device.
No advertising or analytics data
No third-party tracking, no analytics SDKs, no advertising identifiers. Nothing about your activity is collected or sold.
No call content
Voice and video call media is end-to-end encrypted and is never stored on the server. The relay handles encrypted packets only.
How it compares
matrix.wyer.io versus common messaging platforms.
| Feature |
matrix.wyer.io |
WhatsApp |
Telegram |
Signal |
| End-to-end encrypted by default |
|
|
|
|
| No corporate data access |
|
|
|
|
| Self-hosted / no third-party servers |
|
|
|
|
| Open protocol / auditable encryption |
|
Partial |
|
|
| No phone number required |
|
|
|
|
| Encrypted voice & video calls |
|
|
Partial |
|
| You know who runs the server |
|
|
|
|
Server security
Layers of protection running continuously to keep the server and its users safe.
The attack surface is kept minimal. Only the services that need to be publicly reachable are exposed. All internal infrastructure is isolated and inaccessible from the internet.
Repeated authentication failures trigger automatic IP blocks. Access attempts are logged and reviewed. Patterns consistent with scanning or brute-force attacks are blocked without manual intervention.
Resource usage, service health, and authentication events are monitored continuously. Anomalies and login events generate immediate alerts, ensuring nothing goes unnoticed.
OS security patches are applied on a regular cadence. Application updates are tested before deployment. No component is updated blindly — every change is intentional.
Each component runs in its own isolated container with only the access it needs. A compromise of one service does not grant access to others.
Credentials, tokens, and shared secrets are managed through environment variables, never hardcoded or committed to version control. Signing keys are excluded from all backups and repositories.
At a glance
Key properties of this server.
Ready to get started?
Request an account. Admin review typically takes less than 24 hours.
Request an account
Back to home