Recording servers and cameras
Connect through the XProtect API Gateway, discover available recording servers and cameras, then select the entities that belong in AlarmForgeX.
MILESTONE XPROTECT HEALTH
Milestone XProtect health monitoring beyond the VMS client.
AlarmForgeX connects to the Milestone XProtect API Gateway to discover recording servers and cameras, track useful operational state, and bring VMS health into the same Windows workspace as the rest of the security estate.
Local Windows monitoringOperational state stays with the AlarmForgeX host unless you configure external delivery.
Recorder + camera visibilityDiscover XProtect recording servers and cameras through the configured API Gateway.
Optional receiver reportingRoute qualified faults and restores through configured AlarmForgeX reporting paths.
WHAT IT ADDS
One health view beyond the VMS client.
AlarmForgeX complements XProtect rather than replacing it. The goal is to make recorder and camera health visible alongside other infrastructure and to give installers a consistent operational history when something changes.
Useful operational state
Track recorder communication and camera recording state, plus selected persistent technical state groups exposed by the configured XProtect environment.
Qualified health faults and restores
When configured, confirmed state changes can use AlarmForgeX's persistent reporting queue, account mapping and receiver delivery paths.
LARGE-ESTATE HARDENING
Built to keep state processing bounded as XProtect estates grow.
AlarmForgeX batches XProtect state work, avoids repeated per-state estate lookups and uses bounded confirmation for camera health transitions. Development stress testing has exercised simulated XProtect estates up to 1,000 cameras; real-site performance still depends on the Windows host, XProtect environment and network conditions.
Efficient state snapshots
Large XProtect state snapshots reuse connection-scoped context so camera and recorder updates do not repeatedly rebuild the same estate lookups.
Monitoring re-enable recovery
After XProtect monitoring is disabled and re-enabled, current same-state evidence can safely re-establish Healthy or Fault state without manufacturing a receiver event just because monitoring was toggled.
Newer evidence wins
Older conflicting snapshots are rejected so stale camera evidence cannot overwrite a newer confirmed Online or Offline state.
WORKFLOW
Connect once, then monitor continuously.
The integration is designed around explicit discovery and state monitoring rather than modifying XProtect recording configuration.
Connect the API Gateway
Enter the XProtect server details and authenticate using the supported AlarmForgeX connection workflow.
Discover entities
Review the detected recording server, cameras and available technical health groups before importing.
Map monitoring points
Assign imported entities to the appropriate AlarmForgeX site and functional Area / Zone ranges.
Watch and report
Use live state, history, checks and optional reporting to identify and deliver confirmed conditions.
DESIGNED FOR SUPPORT
Useful when the question is “is the recording system actually healthy?”
AlarmForgeX gives installers another operational layer for sites where recorder state needs to sit beside cameras, recorders, UPS devices, network targets and monitoring-station reporting.
- Recorder communication state and recovery visibility
- Camera online and recording-state visibility where exposed by XProtect
- Selected stateful XProtect technical conditions for supported environments
- Common AlarmForgeX logs, device checks and service-mode workflows
- Optional CSV/IP or SIA DC-09 reporting of qualified conditions
TRY THE SAME WINDOWS BUILD
Add XProtect health to the wider security estate.
Start with the free capacity or activate the built-in evaluation, then decide whether the site needs a permanent commercial licence.