All 4 communication components (composing under bp-relay) got role- in-Catalyst banners pointing at PLATFORM-TECH-STACK §4.5: - stalwart: JMAP/IMAP/SMTP self-hosted email. - livekit: WebRTC SFU for video/audio/data; pairs with STUNner. - stunner: K8s-native TURN/STUN for WebRTC NAT traversal. - matrix: Matrix protocol via Synapse server. Banner explicitly disambiguates "Synapse" as the chat-server implementation, NOT the deprecated OpenOva product noun (retired in favor of bp-axon). All 4 are explicitly Application Blueprints, NOT Catalyst control plane. VALIDATION-LOG: Pass 13 entry added. Refs #37 |
||
|---|---|---|
| .. | ||
| README.md | ||
Matrix/Synapse
Decentralized chat and messaging using the Matrix protocol (Synapse server implementation). Application Blueprint (see docs/PLATFORM-TECH-STACK.md §4.5 — Communication). Used by bp-relay for team chat with end-to-end encryption and federation.
"Synapse" here refers to the Matrix server implementation (the chat backend), NOT the deprecated OpenOva product noun (which has been retired in favor of
bp-axonfor the SaaS LLM gateway).
Category: Communication | Type: Application Blueprint
Overview
Matrix (via the Synapse server) provides self-hosted, federated chat and messaging with end-to-end encryption. Supports team collaboration, incident communication, and integration with external Matrix networks.
Key Features
- End-to-end encrypted messaging
- Federation with external Matrix servers
- Room-based team collaboration
- Bridge support (Slack, IRC, Discord)
- Webhook integrations for alerting
Integration
| Component | Integration |
|---|---|
| Keycloak | SSO via OIDC |
| CNPG | PostgreSQL backend |
| Grafana | Alert notifications via Matrix |
| Stalwart | Email notifications |
Used By
- OpenOva Relay - Team messaging component
Deployment
apiVersion: kustomize.toolkit.fluxcd.io/v1
kind: Kustomization
metadata:
name: matrix
namespace: flux-system
spec:
interval: 10m
path: ./platform/matrix
prune: true
Part of OpenOva