From raw data streams to operational alerts in four layers.
Larx processes satellite imagery, sensor readings, and camera feeds through a spatial alignment pipeline, applies your detection rules, and surfaces alerts directly to your operations team.
The Larx data pipeline.
Four processing layers, each with a specific job, between raw imagery and an actionable alert.
Layer 1: Multi-source ingestion
Larx connects to satellite imagery providers, fixed camera streams, point sensor APIs, and SCADA data exports. Ingestion handles format normalization, timestamp alignment, and coordinate reprojection so every data source lands in the same reference system from day one.
Layer 2: Spatial alignment and baseline building
Every incoming data point is indexed to its spatial location and compared against a rolling baseline for that location. Larx builds and maintains those baselines automatically, adjusting for seasonal patterns and known-good states so the change signal you get reflects real anomalies, not calendar noise.
Layer 3: Detection rule engine
You define what constitutes an alert for each monitored corridor or site: encroachment buffer distances, vegetation height thresholds, sensor deviation limits, or custom combinations of conditions. The rule engine evaluates every spatial event against your configured rules, not a generic model's defaults.
Layer 4: Alert delivery and workspace
Alerts surface in the Larx workspace with the full spatial context attached: imagery for the event date and prior dates, sensor readings at the same location, and any prior history for that site. Your team sees the confirmation picture before dispatching a crew, not just a coordinate.
Onboarding is connecting your corridors, not building a new system.
Larx onboarding starts with your existing asset registry. We ingest your corridor and site geometries, connect the satellite coverage for those locations, and walk through your alert rule configuration with your operations team.
Most customers complete onboarding within two weeks. The integration layer handles the data plumbing; your team focuses on configuring what matters for their specific asset portfolio.
Walk through a demoData handling and security.
Larx processes all data within SOC 2 Type II audited infrastructure. Asset geometries, sensor data, and imagery are stored in tenant-isolated environments. No customer data is used to train shared models or shared across tenant boundaries.
Access controls support role-based permissions, SSO integration via SAML 2.0, and audit logging for every workspace action. Enterprise deployments include data residency options for US-only storage.
System availability and data freshness.
The Larx platform maintains a 99.9% uptime SLA for the workspace and alert delivery layer. Satellite imagery refresh cadence varies by provider and corridor priority, with daily revisit available for high-priority assets in most coverage zones.
Real-time camera and sensor feeds stream directly from your existing infrastructure. Larx does not store raw video streams; analysis results and event records are retained per your configured retention policy.