GCXONE · Platform
NXG Edge
Field Hardware and On-Site Analytics
Where the Signal Starts.
NXG Edge is everything that runs at the customer premises: the appliance and the analytics on it, the cameras and recorders it speaks to, the routers that connect the site, the IoT and actor connections that let it act, and the power hardware that keeps it alive. It carries the NXG prefix rather than a GCX one for a reason — it is the one part of the platform that is not in the cloud, and the distinction is what the whole naming structure turns on.
Key capabilities
- On-device analytics: smart detection performed at the site, before anything is transmitted
- IP camera auto-discovery and configuration over RTSP, HTTP and UDP
- Direct camera integration without a recorder, including ONVIF and Axis over RTSP and VAPIX
- Industrial routing with LTE/4G WAN, dual-SIM failover, VPN tunnels and remote diagnostics
- Digital, analog, isolated and relay I/O for gates, barriers, sirens and detection inputs
Primary use cases
- Sites whose bandwidth cannot carry continuous video to the cloud for analysis
- Deployments that need the lowest possible latency between detection and response
- Mixed brownfield estates where the recorders are already there and are staying
- Off-grid and mobile sites, where connectivity and power are hardware problems before they are software ones
At a glance
4
I/O types supported
3
Stream configuration protocols
Per channel
Edge analytics licensing
2
Power ecosystems integrated
Layer
Edge analytics
Detection performed on the appliance, so what leaves the site is an event rather than a video stream waiting to be judged.
- Best for: constrained bandwidth and latency-sensitive response
Layer
Cameras and recorders
Direct IP cameras over ONVIF or vendor protocols, or an existing recorder kept exactly where it is.
- Best for: brownfield estates and mixed-brand fleets
Layer
Connectivity
Industrial LTE routing with dual-SIM failover, VPN, GPS and remote diagnostics.
- Best for: sites with no fixed line, and anything that moves
Layer
Power
Victron solar, battery and inverter hardware, and EFOY fuel cells, reporting telemetry as well as supplying power.
- Best for: off-grid, where power is the availability story
Architecture
Technical specifications
- Analytics
- Smart analytics performed on the device, so environmental noise is filtered before it is transmitted
- Configuration Services
- RTSP, HTTP and UDP stream configuration
- Discovery
- IP camera auto-discovery on the site network
- Storage
- Secure encrypted local storage
- Clustering
- Server clustering for larger sites
- Connectivity
- Cloud connect and an edge API
- Licensing
- Per channel, hardware-agnostic and available for OEM deployment
- Direct IP
- ONVIF and Axis over RTSP and VAPIX, with no recorder required
- Brands
- Hikvision, Dahua, Milestone, Axis, Axxon, Hanwha, Mobotix, Vivotek, NetVu, Avigilon, Geutebruck, NX Witness and more from the integration catalogue
- Wireless Detection
- Reconeyez wireless PIR detection cameras, and AJAX wireless camera and recorder lines
- Streaming Protocols
- RTSP, TCP JPEG and raw, HLS, and manufacturer SDKs
- AI Boxes
- Third-party analytics and perimeter detection such as Davantis, Camect and Senstar
- Router
- Teltonika industrial LTE/4G router, enrolled in Remote Management System
- Requirements
- Administrative credentials with API access, a reachable IP directly or over VPN, the serial number, and the control port (default 80)
- Features
- Dual-SIM failover, VPN tunnels, GPS location, remote reboot and diagnostics
- Telemetry
- Signal quality (RSRP, RSRQ), SIM data usage against a configured limit, I/O state, GPS position, jamming detection
- Tracker
- Teltonika Telematics FT and FMB vehicle trackers on OBD-II or CAN, 10-30V DC with battery backup
- Types
- Digital, analog, isolated and relay
- Direction
- Input, receiving a signal from an external source, or Output, driving a gate, lock, barrier or siren
- Configuration
- Per port: type, display name, IO URL, activation duration and zone
- Local Operation
- I/O operated directly over a local device connection where the device supports it
- Solar And Battery
- Victron MPPT charge controllers, battery monitors and inverters, through a Cerbo GX or Color Control gateway
- Fuel Cell
- EFOY Pro fuel cells with a network gateway and an EFOY Cloud account
- Audio
- SIP-enabled IP speakers registered through a Genesis Audio device on the site
- Prefix
- Edge-deployed products keep the NXG prefix because they run on customer premises. A cloud product with the same function would carry a GCX one
- Local Mode Dependency
- Direct peer-to-peer operator access needs the Local Mode service on the workstation and is not supported for every device type
- Compatibility Is A Catalogue
- Hardware support is decided by the integration catalogue, not by any one product. A device not in it is not reachable however the site is wired
Edge software
Cameras and recorders
Connectivity hardware
IO and actors
Power hardware
Governance & Limitations
Getting started
Specified as part of the site design. What matters most is which detection runs where, because that decision sets the alarm volume for the life of the site.
- 01Design the siteDecide what is detected on the camera, what on the appliance, and what in the cloud
- 02Connect itInstall and enrol the router, confirm reachability directly or over VPN, and whitelist the platform ranges
- 03Onboard the devicesAdd the recorder or cameras under the site, then the I/O, power and audio devices
- 04Set the detectionConfigure on-device intelligent detection rather than basic motion, before the site goes live
Works with
