Answers to the questions we hear most.

The dashboard opens with four KPI cards covering the time range you have selected, which defaults to the last 2 days and can be adjusted with the date range filter. They summarise alarm volume, how many sites you have configured, devices that are active but silent, and cameras that failed their last HealthCheck. The Unhealthy Cameras card links straight into the HealthCheck module, so a non-zero count can be investigated without hunting for the report.

• Total Alarms - all alarm events generated across your monitored sites
• Total Sites - sites configured under your service provider account
• No Alarm Devices - active devices with no alarms in the period, often a connectivity or sensor sign
• Unhealthy Cameras - cameras that failed their most recent HealthCheck

GCXONE is a cloud-based, AI-powered platform for intelligent alarm management and security operations. It brings alarms, video surveillance, device health, workflows and AI capabilities together in a single interface, so monitoring can be centralized and location-independent without local infrastructure. It is designed as an operational control center intended to increase efficiency, automate processes and scale security operations.

Open the gear icon at the bottom of the left navigation sidebar and choose Switch Tenant. That moves you between the service provider tenants you have access to in the same session, so a provider managing multiple clients does not have to sign out and back in. The same gear menu is also where General preferences, User Profile, Roles, Users, Reports and Tags Management live.

It targets the recurring problems of security operations centers and service providers: too many false alarms, slow manual verification, and cameras that fail without anyone noticing. It also addresses slow onboarding of new customers, sites and devices, and poor visibility across distributed locations. The platform is positioned as reducing these issues while giving full transparency over security operations.

• False alarms triggered by movement, light or weather
• Time-consuming manual verification of every event
• Cameras going offline or degrading unnoticed
• Limited visibility across distributed systems and sites

Devices, cameras and sensors send their events to GCXONE, where the NOVA99x AI filters up to 99% of false alarms in real time. Verified alarms are then delivered to Talos with full context, and operators review, confirm or escalate them. Automated workflows handle notifications and escalation, and every alarm ends up documented in the audit log.

No. GCXONE runs entirely in the browser, so no software installation is required on operator workstations. You do need a supported browser with JavaScript enabled, and a screen resolution of 1920x1080 or higher is recommended so the full dashboard is visible.

• Google Chrome 90 or later (recommended)
• Microsoft Edge 90 or later
• Mozilla Firefox 88 or later
• Safari 14 or later

A minimum of 10 Mbps is required for standard platform operations. Video streaming and large data exports need more than that, and how much more depends on how many cameras and sites are active. Plan the connection for the busiest case rather than for the baseline.

Port 443 is the primary one: it carries all web platform access, real-time WebSocket updates, REST API calls and outbound webhooks. Port 80 is optional but recommended for HTTP-to-HTTPS redirects, and the remaining ports depend on what you monitor or integrate. Your network also has to resolve and reach the nxgen.cloud domain, so add the A or CNAME records first if you run internal DNS.

• 443 HTTPS/WSS for platform access, WebSockets, API and webhooks
• 161/UDP and 162/UDP for SNMP monitoring and SNMP traps
• 502 for Modbus TCP industrial and power equipment
• 1883 or 8883 for MQTT IoT devices; 8883 is encrypted and preferred

If your organization routes traffic through a proxy server, that proxy has to be configured to allow WebSocket connections on port 443. Standard HTTP proxies may block WebSocket traffic, which is exactly what real-time alarm updates rely on. Check the proxy configuration for WebSocket support before assuming the platform itself is at fault.

No. Registration and the activation email require a corporate email address; personal addresses are not accepted. You also need administrative access to configure firewall rules and network settings during setup, plus a primary and secondary contact for account recovery and escalation. Both contacts should be reachable during the deployment window.

Collect the administrator credentials for every camera and sensor you plan to integrate, along with each device's IP address and communication port. Have the network topology for each site to hand, meaning subnet details and gateway addresses. Verify that all devices are running up-to-date firmware first, so you do not hit compatibility issues during integration.

• Administrator usernames and passwords per device
• Documented IP address and port for each device
• Subnet and gateway details for every site
• Firmware brought up to date before integration

Genie is GCXONE's built-in AI assistant and sits as a floating panel on the dashboard, always available. You type a question and it either pulls the relevant data or carries out the action directly. It covers five areas: insights such as alarm summaries and system data analysis, ticket management, VPN requests, device setup and troubleshooting guidance, and Spawn for triggering platform actions.

Evalink Talos is a fully cloud-hosted alarm management platform for monitoring stations and enterprise security teams, reached from inside GCXONE through a partnership between NXGEN Technology AG and Evalink. In the NXGEN ecosystem it is the alarm verification and dispatch engine: GCXONE handles video analytics, device management and AI filtering, and Talos provides the queues and workflows operators use to process alarms, contact customers and document incidents. It prioritises alarms on your own business logic, embeds GCXONE video inside the alarm card, and logs every operator action in an immutable audit trail.

• Built as cloud-native microservices on AWS, with servers across America, Europe and Asia
• If one microservice has a problem the rest of the platform keeps running
• Updates are deployed remotely; a major change prompts you to reload the page

Local Mode lets the operator workstation connect directly to the NVR or device over the local network using the device's native SDK, bypassing the central GCXONE cloud streaming gateway for high-bandwidth functions. Use it on on-site operator workstations, where it gives lower latency, higher quality video and access to features that only work over a direct device connection. If local access fails, the video viewer switches to cloud streaming automatically, so monitoring continues without operator intervention.

• Enables P2P streaming, live video, playback and local SDK audio
• Also enables encrypted streams, local PTZ, local IO and the timeline
• Falls back to cloud streaming automatically on local network interruptions
• Best installed on every operator workstation at the start of deployment

Every alarm has passed through a five-step pipeline. A camera or sensor detects activity and signals the platform through the Proxy Layer, the platform logs the raw event with a timestamp, device ID, site and customer reference, and the event then goes through the NOVA99x AI engine, which classifies it. Real Alarms are pushed to the operator queue in Talos, False Alarms are filtered out and kept for reporting and analytics, and Technical Events trigger automated notifications or workflows such as calling a technician. The operator reviews and closes the event, and every action lands in the Audit Trail.

Local Mode components must be installed on every operator workstation that will use it — it is not a server-side switch. Download the Genesis Installer and run it as an administrator; there are two ways to install it, a graphical wizard or a silent command-line run, and both install the same components. Use v.2.9.7 or later to ensure full feature compatibility. Local Mode features such as P2P streaming, encrypted streams and local audio all depend on that component being present on the workstation.

• Install on every operator workstation, not centrally
• Use Genesis Installer v.2.9.7 or later
• Run the installer as an administrator (wizard or silent command line)
• Install at deployment time rather than during an active incident

A Real Alarm is a genuine security event needing operator attention, such as motion detection, line crossing or intrusion. A False Alarm is triggered by non-threatening activity such as animals, weather or lighting changes, and NOVA99x filters it out before it reaches the queue. A Technical Event is system-generated by HealthCheck - a camera going offline, a black screen, an obstruction, or low light - and drives automated notification rather than operator review. Never ignore a technical event: a camera that is offline is a blind spot in your coverage.

• Events move through New, Filtered, Assigned, In Progress and Processed
• A Real Alarm rate above 30% may mean NOVA99x needs reconfiguring
• False alarm decisions feed back into NOVA99x analytics

When Local Mode is on but there is no P2P connection, or latency stays high, check the Local Mode service first: confirm it is running in Windows Services, then restart or reinstall it and read the service logs for errors. Next confirm the workstation and the device are on the same network, and review network routing, VLAN configuration and firewall rules. If auto-discovery is not finding the devices, configure their IPs manually in the Local Mode settings. Note that Hanwha and Genesis Audio do not support Local Mode at all, so those devices will always use cloud streaming.

• Verify the Local Mode service is running in Windows Services
• Confirm the workstation and device sit on the same network
• Check routing, VLAN configuration and firewall rules
• Configure device IPs manually if auto-discovery fails

Yes. A new site created in GCXONE shows up in Talos automatically, in real time over MQTT messaging with error handling and retry logic, carrying the site name and address, contact information, geographic coordinates, configuration parameters and operational status. The reverse is not automatic: a site created in Talos first has to be brought across by hand. Where something is out of step you can force it from Configuration, Customers, the Sites tab, then the actions menu next to the site - Push to Talos sends the latest GCXONE data over, Pull from Talos brings Talos data back in. The same menu also arms and disarms the site without opening Talos.

• Create sites in GCXONE first so automatic sync does the work
• Push to Talos after a bulk configuration change
• Pull from Talos when troubleshooting a discrepancy before escalating to support

Local Mode is either unsupported or unnecessary for three device types. Hanwha devices do not support Local Mode features, Senstar does not support Local Mode operations, and Genesis Audio using SIP or Twilio does not need it because it is designed for cloud integration. Do not attempt to configure Local Mode for these devices — use cloud streaming instead. Full support across both cloud and Local Mode covers Adpro, Axis, Axxon, Dahua, Hikvision and Milestone.

• Hanwha: Local Mode features are not supported
• Senstar: Local Mode operations are not supported
• Genesis Audio (SIP/Twilio): not required, cloud integration by design
• Full cloud and Local Mode support: Adpro, Axis, Axxon, Dahua, Hikvision, Milestone