System Requirements
Minimum and recommended hardware, storage, network, and browser requirements for Kalytera VMS.
Plan from the camera streams
There is no single camera-count-to-hardware rule. Size the recording host from the aggregate incoming bit rate, retention period, concurrent viewers, export workload, and the analytics rules you enable. Validate the design with the actual camera profiles before production rollout.
| Resource | Planning guidance |
|---|---|
| CPU | Modern x64 processor. Add capacity for stream conversion, concurrent exports, and analytics. |
| Memory | Allow headroom for every active stream, live-view session, background job, and analytics model. |
| Application storage | Use an SSD for the operating system, database, and application. |
| Recording storage | Use dedicated storage with sustained write performance and enough capacity for the retention target. |
| Network | Use wired Ethernet, account for camera and viewer traffic, and keep operational headroom. |
Storage calculation
A practical decimal estimate is GB per day ≈ Mbps × 10.8 for each continuously recorded stream. Multiply by the number of retention days and cameras, then add operating headroom. For example, one 4 Mbps stream uses about 43.2 GB per day before filesystem and operational overhead.
Do not assume every stream is always copied byte-for-byte. Kalytera can use codec copy when the input and target are compatible, but processing and export paths may transcode. Measure the streams and build in capacity rather than treating a bitrate estimate as an exact result.
Network and browser path
- Camera traffic: Add the configured bit rates of all streams received by the recording host and reserve headroom for reconnects and secondary streams.
- Live viewing: Camera RTSP is handled by the Kalytera server and delivered to the browser through server-mediated WebRTC, with HLS available as a fallback. A viewer does not connect directly to the camera.
- Segmentation: Put cameras on a controlled VLAN and permit only the management and media paths the deployment needs.
- Remote access: Prefer a VPN or TLS reverse proxy. Do not expose the plain HTTP endpoint directly to the internet.
Use a current browser with WebRTC and Media Source support. Browser and codec behavior changes over time, so test the intended browser, camera codec, and network path together.
Analytics capacity
Analytics execute on the recording host. CPU inference is supported; optional execution providers and compatible hardware can improve throughput when included in the deployed build. Capacity depends on model, resolution, sampling rate, and simultaneous rules, so benchmark the production workload instead of relying on a fixed cameras-per-GPU figure.
Implemented camera adapters
Kalytera includes adapters for the following device families and standards. Actual functions still depend on the camera model, firmware, credentials, and enabled services.
- Hikvision — native and SDK integrations
- Dahua — native and SDK integrations
- TVT — SDK integration
- Axis
- Hanwha
- Uniview
- Mobotix
- ONVIF and generic RTSP for compatible devices