Transparent operations, no hidden dependencies
Documentation written to be followed top-to-bottom. One installer, one Ansible role, one update format.
- CPU
- x86_64 or ARM64, 8+ cores per media node
- RAM
- 16 GB+ per media node, 32 GB+ for the AI scribe node
- GPU
- Optional, accelerates the AI scribe (CUDA or ROCm)
- OS
- Ubuntu 22.04 / 24.04 LTS; other Linux distributions on request
- Network
- 100 Mbps+ per node, public UDP ports for WebRTC
- Storage
- S3-compatible object storage or a local volume for recordings
Five steps, one business day
- 01Prepare the servers
Allocate virtual or physical machines for media nodes and the AI node. Install the base OS, apply network rules, reserve IPs.
- 02Download the installer
A single tarball installer with images for every component. Transfer into an isolated network over your secure channel.
- 03Run the Ansible role
One command provisions the media server, signaling, database, monitoring, and the AI scribe. Secure defaults out of the box.
- 04Connect the directory
Hook up LDAP / Active Directory, configure role policies, import groups. Verify with a test user.
- 05Acceptance testing
Smoke-test rooms, verify SIP connections, generate a test transcript with the AI scribe, review the monitoring panel.
What needs to be open
- TCP 443
- HTTPS — web client, API, signaling
- UDP 7881 / 50000–60000
- WebRTC — media
- UDP 3478 / TCP 3478
- STUN / TURN
- TCP 5060 / UDP 5060
- SIP signaling
- TCP 9090
- Monitoring (internal network)
Common questions from administrators
Yes. Media nodes update via rolling restarts with traffic drained first. Core services use blue/green or canary strategies.
Scheduled backups of the database (PostgreSQL) and the recording store. The installer ships ready-made scripts for cron / systemd timers.
No. Once installed, the platform runs entirely inside your closed network. Updates and new model images arrive as a tarball.
LDAP / Active Directory works out of the box. SAML and OIDC are planned for upcoming releases.
SIP endpoints register as regular SIP clients. Each device type gets a codec profile in the admin panel. Outbound calls to gateways and external conferencing servers are routed by dial plan: numeric prefix to the right trunk.
Meeting recordings live in your internal S3-compatible object storage or on a local volume — data never leaves your perimeter. The path and retention are set at deployment time in the Ansible config.