# How to integrate AI video analytics with NVR and NAS storage > AI video analytics NVR and NAS integration connects an AI detection platform to the storage layer where security footage is recorded and retained — enabling real-time analysis of live streams, forensi Canonical URL: https://safetyscope.eu/integrations/ai-video-analytics-nvr-nas-storage _Published: 2026-02-23 · Updated: 2026-04-02_ AI video analytics NVR and NAS integration connects an AI detection platform to the storage layer where security footage is recorded and retained — enabling real-time analysis of live streams, forensic search of recorded footage, AI-triggered selective recording, and automated retention policy enforcement. The storage integration determines what footage can be retrieved for investigation, how efficiently storage capacity is used, and whether the AI platform can access historical footage for re-analysis. This guide covers the architecture patterns, storage sizing, and the specific technical problems that surface when connecting analytics to on-premises recording infrastructure. ## What this integration achieves Connecting AI [video analytics](/glossary/video-analytics-software) to [NVR](/glossary/nvr-vs-dvr-vs-nas-security) or NAS storage enables the analytics platform to access both live streams for real-time detection and recorded footage for [forensic search](/learn/ai-video-forensic-investigation) and re-analysis. It also enables AI-triggered selective recording — storing AI-flagged event clips at higher quality or longer retention than continuous background recording — which is the single most effective storage optimisation available in AI video deployments. Without proper storage integration, the analytics platform can only process live streams. It cannot search historical footage by metadata query, cannot retrieve clips for incident investigation, and cannot enforce [retention policies](/glossary/video-retention-policy) automatically. The deployment works as a real-time alerting system but loses its forensic investigation capability — which for many organisations is the higher-value use case. ## How it works — architecture overview ### Live stream vs recorded footage access AI analytics platforms access live streams via [RTSP](/integrations/rtsp-ip-camera-stream-integration) — either directly from the camera or through the NVR's stream forwarding function. This is straightforward and well-documented in the RTSP integration guide. Recorded footage access is different: it requires the NVR to expose a retrieval API or RTSP playback stream that allows the analytics platform to request footage by time range. Not all NVRs support this capability — and those that do implement it differently. Verify recorded footage access with the specific NVR model and firmware version before specifying it for a deployment. ### NVR as camera manager vs NVR as storage only Two distinct deployment patterns exist. In the first, the NVR manages camera connections (handles authentication, stream negotiation, and recording) and the AI platform connects to the NVR's stream output rather than directly to cameras. This simplifies camera credential management — credentials are configured once on the NVR rather than on both the NVR and the AI platform — but adds a dependency: if the NVR fails, the AI platform loses camera access along with recording. In the second pattern, the AI platform connects directly to cameras via RTSP, and the NVR records independently. This provides resilience — if either system fails, the other continues operating — but requires managing camera credentials in two systems. ### NAS-based storage architecture NAS devices provide raw storage capacity without the camera management functions of an NVR. In a NAS architecture, a VMS or the AI analytics platform itself manages camera connections and writes footage directly to NAS shares via SMB or NFS protocols. This pattern is common in larger deployments where the NAS provides expandable storage capacity that exceeds what a standalone NVR can offer. It requires the analytics platform or VMS to support direct-to-NAS recording — verify this capability before specifying. ### Selective recording and tiered retention AI analytics can trigger high-quality clip recording of detected events while background continuous recording runs at lower quality or reduced frame rate. A tiered retention policy stores AI-flagged clips for 90 days (because they contain confirmed detections worth retaining for investigation) and continuous background footage for 14 days (sufficient to cover the typical incident discovery window). This combination optimises storage use without sacrificing evidence quality — and the storage savings are substantial: AI-triggered recording typically uses 5–20% of the storage required for continuous full-quality recording, depending on site activity level. ## Requirements and prerequisites **NVR RTSP stream output:** The NVR must expose RTSP streams for connected cameras that the AI platform can ingest. Most modern NVRs support this — verify the specific model and firmware version. Some manufacturers restrict RTSP access to their own ecosystem. **NVR channel capacity and throughput:** Verify the NVR supports the required camera count and total stream throughput. An NVR rated for 16 channels at 1080p may not support 16 channels at 4K — check the total throughput specification, not just the channel count. **NAS share accessibility:** For NAS-based architectures, the NAS must expose SMB or NFS shares accessible from the analytics platform or VMS. Network configuration, authentication, and share permissions must be configured before deployment. **Storage capacity calculated and verified:** Use the bandwidth and [storage calculator](/learn/bandwidth-storage-calculator-ai-video) to determine the total storage requirement based on camera count, resolution, compression, recording hours, and retention period. Specify storage at 1.5× the calculated requirement to accommodate growth. **RAID configuration:** Configure RAID 5 or RAID 6 on the NVR or NAS for data resilience. RAID 0 (striping without parity) provides no protection against drive failure — a single drive failure loses all footage. For critical installations, RAID 6 provides dual-parity protection. **Retention policy defined:** Define the retention policy before deployment — continuous footage retention period, AI-flagged clip retention period, and the automated deletion schedule. Do not defer this to post-deployment configuration. ## Common integration challenges and how to solve them ### NVR RTSP streams not accessible to third-party platforms Some NVR manufacturers restrict RTSP stream access to their own ecosystem — the NVR records camera streams but does not expose them for third-party consumption. The symptom is an RTSP connection that is refused or returns an authentication error despite correct credentials. This is a firmware-level restriction, not a configuration issue. Solution: verify RTSP accessibility with the specific NVR model and firmware version before specifying it for a deployment. Test in a lab environment if possible. Prefer NVRs with documented RTSP support for third-party integrations. If locked to a proprietary ecosystem, consider connecting the AI platform directly to cameras via RTSP and using the NVR only for recording. ### Storage throughput bottlenecks High camera counts writing to an NVR or NAS simultaneously can saturate the storage interface. The typical failure mode is frame drops and recording gaps during high-activity periods — when motion across many cameras increases bitrate simultaneously. The storage device cannot write data fast enough, and frames are dropped. Solution: calculate total write throughput required (camera count × average bitrate) and verify the NVR or NAS storage interface supports it with 20% headroom. For NAS deployments, use dedicated storage NICs (not shared with other network traffic) and verify the NAS's sustained write throughput specification — not just the burst specification. ### Retention policy drift Manually managed retention policies are not applied consistently. Without automated enforcement, footage is either deleted too early (overwritten before an incident is discovered and investigated) or kept indefinitely (storage fills, recording fails, new footage cannot be written). Solution: configure automated retention policies at the analytics platform level, not the NVR level. The AI platform should manage its own event clip retention independently of the NVR's continuous recording retention. Separate the two retention lifecycles so that AI-flagged evidence clips are preserved even when continuous background footage is overwritten. ### Clock synchronisation between NVR and analytics platform If the NVR and the AI analytics platform use different time sources or have drifted out of synchronisation, timestamps on recorded footage will not match AI event metadata timestamps. The result: a forensic search for an event at 14:23 returns footage timestamped at 14:25 on the NVR — or worse, returns nothing because the time window does not overlap. Solution: synchronise both systems to the same NTP source. Verify synchronisation as part of commissioning and monitor it continuously. A 2-second drift is acceptable; a 30-second drift makes forensic correlation unreliable. ## How SafetyScope handles NVR and NAS integration SafetyScope connects to live camera streams via RTSP — either directly from cameras or through NVR stream forwarding. For recorded footage access, the platform supports RTSP playback from compatible NVRs, enabling forensic metadata search across historical footage. AI-triggered selective recording is built into the platform's event pipeline. Detected events are recorded as high-quality clips with configurable retention periods independent of continuous recording. Continuous background recording can be managed by the NVR or NAS with its own shorter retention cycle. For NAS-based deployments, SafetyScope supports direct-to-NAS recording via SMB shares. Storage capacity monitoring alerts administrators when available storage drops below configurable thresholds, preventing silent recording failures from unmanaged disk space. ## FAQ ### How does AI video analytics connect to an NVR? The AI platform connects to the NVR via RTSP to receive camera streams for real-time analysis. For recorded footage access, the NVR must expose an RTSP playback interface or retrieval API. The AI platform can also connect directly to cameras via RTSP, bypassing the NVR for live analysis while the NVR handles recording independently. ### Can AI video analytics work with a NAS instead of an NVR? Yes. In a NAS-based architecture, the AI analytics platform or a VMS manages camera connections directly and writes footage to NAS shares via SMB or NFS. The NAS provides expandable storage capacity without camera management functions. This pattern is common in larger deployments where storage requirements exceed standalone NVR capacity. ### Does AI video analytics require a dedicated NVR or can it use an existing one? AI video analytics can work with an existing NVR provided it exposes RTSP streams for connected cameras and supports the camera count and throughput required. Verify RTSP accessibility and third-party compatibility with the specific NVR model and firmware version. If the existing NVR restricts third-party access, the AI platform can connect directly to cameras instead. ### How does AI-triggered recording reduce storage requirements? AI-triggered recording only stores footage when a detection event occurs — a person entering a zone, a vehicle at a gate, an anomaly detected. Continuous recording stores everything regardless of activity. AI-triggered recording typically uses 5–20% of the storage required for continuous recording, depending on site activity levels. Combined with tiered retention (longer for AI clips, shorter for continuous), the storage savings are substantial. ### What NVR specifications are needed for AI video analytics? The NVR must support RTSP stream output for third-party access, have sufficient channel capacity and total throughput for the camera count, and provide enough storage capacity for the defined retention period. Verify the sustained write throughput specification (not just burst) and calculate storage using the bandwidth calculator. RAID 5 or 6 is recommended for data resilience.