Live Console
From going live to the post-mortem
Everything spread across several tools, in one place. RTMP ingest feeds the media server, producing HLS multi-bitrate playback and slice replays; browsers can go live over WHIP/WebRTC. Staff issue short-lived tickets bound to a session so viewers join by link without logging in, and tickets are never persisted. Danmaku, gifts, co-hosting, AI replies and a digital human are managed inside the same session with a shared interaction publisher for staff and viewers.
Distribution channels are OAuth-ready, the data wall shows the live session, and admin, viewer H5, anchor PC clients plus a desktop shell share one permission model. Replays are governed by lifecycle rules (day-based deletion aligned with database records) and anomalies can raise alerts. Production artefacts ship without default passwords; pushing across the public internet, watching on a phone with a ticket and landing three danmaku messages were all verified.
Core capabilities
- RTMP ingest to media server, HLS multi-bitrate and slice replay
- Browser broadcasting over WHIP / WebRTC
- Ticket-based login-free viewing, tickets never persisted
- Danmaku, gifts, co-hosting, digital human and AI replies in one session
- OAuth-ready distribution channels
- Live data wall
- Admin, viewer H5, anchor PC and desktop shell
- Replay lifecycle governance and alerting
Who uses it
- Brand live shows across sessions
- Internal training with ticketed staff viewing
- Exhibitions and launches with multiple cameras
- Store-level broadcasts with head-office oversight
Delivery models
Multi-tenant SaaS · self-hosted media · on-premises · source licence
Tech stack
Java 17 + Spring Boot（RuoYi 扩展）· Vue3 ×3 · Electron · MySQL / Redis / RabbitMQ · MediaMTX