Who this is for
This kind of platform is a fit when several of the following apply:
- You handle sensitive internal communication
- You need self-hosted or controlled infrastructure
- An open protocol matters for portability
- Users authenticate against an existing identity provider
- You expect a documented migration and operating model
- Purely SaaS-operated messaging is not acceptable
The platform in layers
A typical deployment combines these open components. Reverse proxies, TURN, monitoring, logging, and a federation boundary are added where the deployment model requires them.
-
Users / Clients
Desktop and mobile Matrix clients connect to the platform; no proprietary client is required.
-
Identity Provider
Your existing identity system authenticates users, for example a Keycloak instance or another OIDC provider.
-
Matrix Authentication Service
Sits between the identity provider and the homeserver and implements the OAuth2/OIDC login flows.
-
Synapse
The Matrix homeserver: it manages accounts, rooms, and message history.
-
PostgreSQL
The database that stores the homeserver's data.
-
Storage / Backup
Media storage; backup and recovery requirements depend on the operating setup.
Deployment models
Hosting location, ownership and operational responsibility are scoped with the customer.
Customer infrastructure
Deployed into servers, VMs, or an environment controlled by your organization.
Hosting location
The location and any hosting provider are identified for the actual deployment before location commitments are made.
Handover
AstraNET deploys and documents the environment so your team can operate it.
Identity integration
Integration with an existing identity system can be scoped per project; provider compatibility depends on the chosen configuration.
- Single sign-on via OIDC
- Matrix Authentication Service between identity provider and homeserver
- Keycloak as an example of a compatible identity provider
Operations
Deployment is the beginning of the lifecycle. What happens afterwards is defined by the agreed operating model.
- Upgrade and version management requirements
- Backup and recovery requirements for the operating setup
- Monitoring, capacity planning, and log handling requirements
- Vulnerability response and change responsibilities
- Handover documentation for your internal team
- Service levels agreed per operating model
Open source and portability
Matrix is an open protocol, and this platform is built from open-source components.
Open source does not mean operations are free. Running a communication platform is ongoing operational work, regardless of license. What open protocols and open-source components provide is portability: documented formats, public documentation, and the ability to keep the stack running with a different operator or an internal team.
The value AstraNET provides on top of these components is architecture, automation, integration, operational readiness, maintenance, support, and accountability — not the software license itself.
Need a controlled Matrix deployment?
Send us your expected user count, identity environment, hosting preference, availability requirements, and integration requirements.