VMS Core Engine
The foundation of Visylix. A high-performance stream processing engine handling 1M+ concurrent streams with zero-copy architecture, multi-protocol support, and flexible recording capabilities.
Push and Pull. Your Way.
Two ingestion modes to accommodate every camera, encoder, and deployment scenario. Visylix adapts to your infrastructure, not the other way around.
Push Mode
Cameras and encoders push streams directly to Visylix via RTMP, SRT, or WebRTC. Ideal for dynamic environments where devices initiate connections, such as mobile units, drones, and body-worn cameras.
- Auto-registration of new stream sources
- Dynamic bandwidth adaptation
- Reconnection with session persistence
- Source authentication and validation
Pull Mode
Visylix pulls streams from cameras and NVRs over RTSP or other protocols. Best for fixed installations where the VMS manages the connection lifecycle and camera inventory.
- Scheduled pull with retry policies
- ONVIF device discovery support
- Credential management per source
- Health monitoring and auto-reconnect
Multi-Protocol Streaming
Native support for six streaming protocols. Each protocol is purpose-built for specific latency, reliability, and compatibility requirements.
RTSP
PullIndustry-standard protocol for IP camera integration. Supports TCP and UDP transport with ONVIF compatibility.
RTMP
PushMature push-based protocol for encoders and broadcast equipment. Persistent TCP connections with low overhead.
WebRTC
Push / PullUltra-low-latency peer-to-peer streaming with custom DTLS and SRTP stack. Ideal for real-time monitoring and two-way communication.
SRT
Push / PullSecure, reliable transport over unpredictable networks. AES-128/256 encryption with forward error correction for WAN delivery.
LL-HLS
OutputApple Low-Latency HLS for web and mobile clients. Partial segments and preload hints minimize glass-to-glass delay.
HLS
OutputStandard HTTP Live Streaming for maximum compatibility across browsers, smart TVs, and set-top boxes at scale.
Four Recording Modes
Capture what matters, when it matters. From continuous 24/7 archival to intelligent event-triggered recording.
Continuous
24/7 recording with configurable retention policies. Frames are written directly from the ingestion pipeline with zero re-encoding overhead.
Schedule-Based
Define recording windows by day of week, time range, and camera group. Supports recurring and one-time schedules with timezone awareness.
Event-Triggered
Recording starts and stops based on AI detection events, external API triggers, or sensor input. Pre-event and post-event buffers capture complete context.
On-Demand
Users or API consumers trigger recording manually for specific streams. Supports duration-limited and indefinite capture with real-time status updates.
Three Storage Formats
Choose the right container format for your retention, playback, and distribution requirements.
Standard MPEG-4 Part 14 container for maximum playback compatibility. Moov atom is written progressively to prevent data loss on unexpected shutdown.
Long-term archival, export, and evidence management
Fragmented MP4 with independent segments for instant seek and parallel write. Each fragment is self-contained, enabling efficient cloud storage and CDN distribution.
Cloud-native storage, CDN delivery, and real-time playback
MPEG Transport Stream for high-resilience recording. Self-synchronizing packet structure ensures recoverability even after partial corruption or disk failure.
Critical infrastructure, disaster recovery, and broadcast workflows
Zero-Copy Streaming
Frames flow from ingestion to output without unnecessary memory copies, achieving maximum throughput with minimal CPU overhead.
Ingestion
Frames arrive via RTSP, RTMP, SRT, or WebRTC and are placed into shared memory buffers. No copy occurs during protocol demuxing.
Routing
The stream router maps each frame reference to subscribed consumers: recording, AI pipelines, and output protocols. Only pointers are forwarded.
Processing
AI models read frames directly from shared memory. Recording writes from the same buffer. No intermediate copies at any stage.
Delivery
Output protocols (WebRTC, HLS, LL-HLS) read the original frame data for packaging and delivery. The frame is released only when all consumers finish.
Explore More of Visylix
Learn how AI analytics, deployment options, and integration APIs build on top of the VMS Core Engine.