01Implemented
Camera wall and focus view
Automatic, 1, 4, 9 and 16-camera grids, staggered stream starts, main/sub-stream selection and a protected HD focus view.
VENTEX / OPEN TECHNOLOGY
VX / VIGIL / 2.10Free technology · open-source release in preparation
Video infrastructure that stays on site.
VIGIL is VENTEX's local video-security line: multiple IP cameras, live views, control, recordings and system diagnostics in one controllable Windows interface—with no external video cloud required.
0116cameras / 4 × 4
022.10qualified product line
03LOCALprocessing path
04WINWindows 10 / 11
Version 2.10.0 · public release in preparation
The software and its reviewed development state are real. A publicly accessible source repository, a project-wide open-source licence and public release distribution are not yet available in the reviewed state.
Local control is an architectural decision.
Many camera setups fragment into vendor apps, cloud accounts and disconnected live views. VIGIL combines generic RTSP/ONVIF functions and deliberately bounded Tapo controls in one local operating surface.
The current line is not a design study. It contains a native Windows application, reproducible packaging, hardware-independent regression tests and separate qualification on real cameras.
What the current product line actually supports.
02Implemented
Adaptive stream control
Four load profiles respond to decoder CPU, render latency, frame drops, learned source FPS and stream instability without prematurely degrading focus streams.
03Implemented
RTSP, ONVIF and Tapo
RTSP live video, ONVIF PTZ and presets, plus firmware-aware Tapo functions with separated device control.
04Implemented
Recording and schedules
Parallel recording, schedules, a local library and safety-oriented recording guards.
05Implemented
Health and diagnostics
Offline detection, performance diagnostics, an event log and sanitised diagnostic bundles for traceable troubleshooting.
06
Public distribution
The Windows build is reproducible. Code signing, automatic updates and formal public release distribution remain the next hardening steps.
SYSTEM ARCHITECTURE
Video path, control path and interface remain separated.
VIGIL isolates failure-prone native decoder work from the UI process. The interface can respond to stream faults without mixing camera control and product state into a single monolith.
Camera and network boundary
RTSP video, ONVIF commands and vendor-specific control are treated as separate interfaces.
Isolated decoder processes
FFmpeg/OpenCV runs outside the UI process; reconnect generations constrain stale worker state.
Shared-memory transport
Triple-buffered BGR frames and versioned descriptors replace continuous JPEG transport.
Controller-based interface
Streams, grid, PTZ, navigation, diagnostics and workspace have clearly separated responsibilities.
From source to a dependable view.
- 01
Connect sources
Register cameras and DVR/NVR channels locally, configuring streams separately from supported controls.
- 02
Stabilise the wall
Start streams in stages, learn real source rates and evaluate load only after a stable warm-up.
- 03
Focus and control
Focus a relevant camera in HD, zoom locally or execute permitted PTZ/preset actions.
- 04
Record and review
Organise recordings locally and review health, performance and event signals together.
SECURITY BOUNDARIES
Local-first does not mean unlimited trust.
VIGIL reduces cloud dependencies, but it does not replace network segmentation or secure camera configuration. The site therefore states what the application controls—and what remains outside its boundary.
Credentials
Camera passwords are stored through Windows Credential Manager and not persisted as part of RTSP URLs.
Device compatibility
PTZ, spotlight and other functions remain model- and firmware-dependent; vendor paths are not presented as universal.
Local network
The application does not automatically control VLANs, camera firmware, routers or physical access to the recording system.
Disclosure
An announced open-source direction is not the same as a public repository with a granted licence. That boundary remains visible until source and licence publication.
Shipped, being hardened and not yet claimed.
This status is based on the reviewed 2.10.0 source archive and its release, build and test documentation.
- Multi-camera grid up to 4 × 4
- Adaptive load and stream profiles
- Recording, PTZ, health and diagnostics
- Reproducible Windows installer build
- Broader hardware and firmware qualification
- Public packaging and release channel
- Authenticode signing
- Public source repository
- Project-wide open-source licence
- Automatic update system
- No blanket device compatibility guarantee
A publicly traceable foundation.
VX / VIGIL / 2.10- Client
- Python 3.11+ · PySide6
- Video
- RTSP · FFmpeg/OpenCV · D3D11 best effort
- Control
- ONVIF · Tapo · local digital zoom
- Internal transport
- Isolated processes · shared memory
- Quality
- Compile · Ruff · Pytest · Windows CI · live qualification
- Availability
- Public source, licence and release publication pending
VENTEX VIGIL questions
Short answers with the same status and claim boundaries as the technical product state.
VIGIL is intended as free open-source technology. The reviewed state still lacks a publicly accessible source repository, a project-wide open-source licence and an officially distributed release.
No. The fundamental path is designed around camera, local network and VIGIL. Vendor-dependent camera functions or remote access to the local network may have separate external dependencies.
The core supports RTSP sources plus ONVIF and Tapo integrations. Exact capabilities depend on model, firmware, network and exposed streams.
The current site claims neither certification nor blanket suitability for regulated or evidentiary video systems. That decision requires a separate requirements and operational review.