GCXONE · Platform

NXG Data

Event and Recording Storage

Kept, and Findable.

NXG Data is where events and footage live. Every alarm, every clip captured around it, and every action taken on it is retained and searchable for the period the deployment is sold with — real-time event storage as standard, with delayed longer-term retention as an option, and capacity that grows with use rather than being bought up front.

Datasheet · v1.0 · verified 15 September 2026

How NXG Data works. Step 1, Buffer: A rolling buffer on the device; 5 seconds of pre-alarm minimum. Step 2, Capture: Clip extracted on the trigger, pre, event and post. Step 3, Retain: 30 days real-time; a further 60 delayed, optional. Step 4, Find: Filtered and paginated, scoped by hierarchy.

Key capabilities

Real-time event storage covering the working retention window, with an extended delayed tier as an option
Alarm clips stored with their pre-event and post-event context attached to the alarm itself
Scalable cloud storage for recordings, with encrypted storage at rest
Filtered, sorted and paginated search across stored files, scoped by hierarchy level
Pay-as-you-grow capacity, charged per GB per month rather than provisioned in advance

Primary use cases

Investigations that begin days after the event they are about
Compliance regimes with a defined minimum retention period
Timelapse and long-horizon site records, where the storage profile is images over years rather than video over days
High-alarm environments where retention settings are a cost decision, not a default

At a glance

30 days

Real-time event storage

+60 days

Optional delayed retention

Per GB / mo

Pay-as-you-grow pricing

~26.7 GB

Per camera per year, timelapse

What happens to a clip

Device buffer
Alarm trigger
Clip extracted with pre and post context
Attached to the alarm
Stored and searchable

Architecture

Where events and footage live. NXG Data connects Events, Alarm clips, Audit log to Investigations, Compliance, Playback and timelapse.

Technical specifications

Option 1: 30-day real-time event storage
Option 3: A further 60 days of delayed storage on top of the real-time window
Model: Pay as you grow, per GB per month
Events: Every ingested event with its timestamp, device, sensor, site and customer reference, and its classification
Alarm Clips: Short segments captured from the device buffer around each alarm, including pre-event and post-event footage
Recordings: Cloud recording for sites using cloud video, alongside recorder-held footage reached through the device
Audit: The immutable log of every action taken on the platform, at every hierarchy level
Search: Stored files filtered, sorted and paginated, with hierarchical scoping — either an explicit level or the level the signed-in user occupies
Delivery: Files served through time-limited signed URLs rather than open links
Security: Secure encrypted storage, with access following the same role and entity permissions as the rest of the platform
Clip Guidance: At least 5 seconds of pre-alarm footage; about 30 seconds in total, 15 seconds either side, is better
Focus: Limit clip capture to the alarm types that matter — capturing everything is the usual reason a storage bill surprises somebody
Timelapse Example: A per-camera timelapse record has run at roughly 26.7 GB a year, about 80 GB across three years
Device Dependency: A clip exists only if the device supports recording and holds a buffer. A camera without one produces an alarm and no footage
Retention Is A Decision: Storage is bought for a period. Footage outside the configured window is not recoverable later, and no part of the platform will tell you it was needed
Not A VMS Replacement: Cloud storage sits alongside on-site recording rather than replacing it; which one holds the authoritative copy is a design decision per site

Getting started

Sold as part of the deployment and sized against the estate. The configuration that matters is what gets captured, not where it is kept.

01Pick the retentionThe real-time window, and whether the delayed tier is needed for the customer compliance position
02Set clip captureEnable clips on the alarm types worth keeping and set the pre and post windows
03Check the buffersConfirm each device actually holds a buffer long enough for the pre-event window configured
04Review the growthWatch consumption in the first months against the estimate, before it becomes a renewal conversation