Run your internal messaging stack on infrastructure you control, so ownership, access, and retention stay with your organization.
Plexichat is a modular, high-performance messaging ecosystem. It is engineered to give organizations total control over their data infrastructure through hardware-rooted security and self-hosted sovereignty.
| Core Capability | Plexichat (Self-Hosted) | Standard SaaS / Cloud |
|---|---|---|
| Key Custody | ✓ Keys live with your infrastructure | ✗ Vendor-managed key custody |
| Data Location | ✓ Your database and storage | ✗ Vendor-controlled storage |
| Network Boundary | ✓ Private network or on-prem | ✗ Shared public cloud |
| Operational Control | ✓ Your logs, backups, and policies | ✗ Export-limited by vendor |
| Integration Model | ✓ Standard protocols and self-hosted APIs | ✗ Vendor-only integrations |
Plexichat ships as a coordinated stack with clear boundaries between API, gateway, and client services.
REST API for users, messages, servers, roles, and admin workflows.
Real-time event stream with opcode-based dispatch and intent filtering.
Browser UI that connects to the API and gateway with configurable base URLs.
WebRTC signaling with Mediasoup or Janus for scalable media delivery.
PostgreSQL for persistence, Redis for caching, and S3-compatible media storage.
Admin UI, audit visibility, and policy enforcement without external dependencies.
Plexichat keeps the encryption root inside your infrastructure, using TPM-backed keys when available or environment-managed keys for container deployments.
Deploy via Docker Compose or a manual Gunicorn service, and place the API behind your own reverse proxy with TLS.
Current repo snapshots from the Plexichat GitLab group.
Core FastAPI backend and real-time gateway services.
Web client that connects to the Plexichat API and Gateway.
We utilize a modified semantic versioning scheme to clearly communicate the state and maturity of each component in the ecosystem:
Stages:
- a (Alpha): Active development, core refactoring, breaking changes common.
- b (Beta): Feature complete, focusing on stability and performance.
- c (Candidate): Final validation, candidate for production release.
- r (Release): Stable, production-ready release.
Opcode-based event flow with intent filtering for predictable real-time performance.
PostgreSQL persistence, Redis caching, and S3-compatible media storage.
Token-based auth, multi-session tracking, and configurable security policies.
Health checks, telemetry endpoints, and admin dashboards for system control.
Built-in reporting flows, audit visibility, and configurable enforcement rules.
Media proxying and validation to reduce exposure to unsafe external content.