OpnIMG turns the first hours of a disaster into a structured stream of validated, geolocated damage observations. Tri-modal smartphone capture, a resilient multi-path sync stack, multi-observer validation in the AWS cloud, and a partner-driven asset-resolution layer that hands clusters to utility, emergency-management, and 311 systems for downstream action.
Counterfactual modelling against ten historical storms in the day-3-to-7 window.
Geometric, temporal, visual, and semantic agreement before a cluster forms. Design target — replaced with measured data at pilot.
LTE · Wi-Fi · SatCOLT · aid-station satellite.
Fifteen provisional patent applications on file with the USPTO. Detail under NDA.
OpnIMG emits validated, geolocated, computer-vision-tagged, validated observation records — confirmed when multiple observers converge on the same event, and emitted to partner systems through documented endpoints. The utility OMS, the state EMA, or the 311 platform turns those observations into work orders and dispatches crews.
Each observation carries provenance, capture-time signatures, computer-vision tags, contributor tier, and a confidence score. A single low-trust observation cannot carry an incident on its own — multi-observer convergence is what validates an event.
Clusters carry validated geometric evidence, aggregated CV evidence, thumbnails, and a reference to an active event — storm, wildfire, declared disaster, or self-derived implicit event.
Each cluster is emitted to the matching partner. The partner returns an opaque reference number — never an internal asset identifier — and OpnIMG records that reference in an append-only audit ledger.
Within the first 72 hours of a major event, the public switchboard collapses, satellite imagery is obscured by cloud or smoke, and field crews are sized for restoration rather than reconnaissance. Hurricane Helene knocked roughly three-quarters of the cell sites across its disaster area offline within a day of landfall. Hurricane Ian alone drew more than eight billion dollars in total federal disaster support (DR-4673-FL).
The structural gap in that window is validation — too many candidate observations, too little assurance any of them are real. OpnIMG fills it by treating every smartphone and every responder device as a candidate observation node and applying geometry, computer vision, and cross-observer validation before anything is emitted downstream.
Counterfactual savings figures appear in OpnIMG materials only when labelled as model output, not as measurement. Operational figures from specific storms are not asserted in external materials unless a source-validated figure exists at the time of writing.
Each layer is engineered for the conditions of a disaster — degraded networks, intermittent power, unreliable GPS, adversarial submissions — and each fails safely toward the higher-trust state.
Three capture surfaces on one shared envelope: an offline-first Progressive Web App — the live, citizen-grade path — plus native iOS with ARKit and LiDAR depth for crews, and native Android for production capture today, with ARCore depth on the near roadmap. All three write the same canonical envelope — image / clip, capture timestamp, location specific data, device class, and a per-device capture signature.
Each submission passes through moderation, computer-vision labelling, geospatial reconstruction, multi-observer validation, and composite confidence scoring. Cluster formation depends on multi-dimensional agreement weighted by observer trust — not on a single low-trust observation alone.
Clusters and validated observations exit through documented endpoints: signed webhooks, OGC WFS 2.0 for GIS tools, NIEM 6.0 JSON-LD for FEMA / DHS exchange, and an Esri Feature Service-compatible endpoint. The partner reconciles each cluster against its authoritative asset database and returns an opaque reference number.
The capture layer is designed to attempt, in priority order, the first available of four sync paths. Capture order is preserved across paths by signing every observation with its capture-time timestamp at the device — the backend always orders by capture time, not arrival time.
Standard LTE / 5G when the local network is healthy.
Open or municipal Wi-Fi where it is available.
Satellite-on-cells-on-light-trucks deployed by responding carriers.
Starlink and equivalent shared satellite uplinks staged at relief points.
The platform consumes a layered set of authoritative storm, wildfire, and incident feeds so every cluster is tagged with the right active event ahead of impact. Three weather tiers run continuously and a fourth — radar — is in active rollout, while wildfire perimeters are monitored on a separate, always-on national feed.
National Hurricane Center, polled every thirty minutes for active tropical systems — the authoritative source for declared hurricanes and tropical storms.
api.weather.gov, polled every five minutes for severe-weather, watch, and warning products — picks up tornadoes, ice storms, floods, and weather events outside the NHC envelope.
Implicit-event detector on a fifteen-minute rolling window — catches incidents that neither federal agency has yet declared, from the ground up. The always-on backstop when official feeds are quiet.
Radar corroboration — in active rollout.
A national wildfire feed running in parallel with the weather tiers. OpnIMG ingests authoritative NIFC interagency wildfire perimeters — refreshed continuously through the day — as an independent active-event source, so a field observation of fire damage is tagged to the right incident the same way a storm capture is tagged to the right system. Because fire is tracked separately, a cluster can carry both a weather event and a wildfire event at once.
The active-events store is the system of record for which event a cluster belongs to. Partners can roll up validated observations by storm, by NWS warning, or by self-derived event — which is how Public Assistance documentation, mutual-aid sequencing, and after-action reviews get their event-level frame. When NHC issues an upgrade or NWS issues a warning, the gating layer flags the active event ahead of the surge, and capture clients are hinted to prioritise sync during the first window after impact.
Consolidation is not deduplication of similar pixels — it is convergence on the same real-world event, captured by multiple observers. The validation layer requires agreement across multiple dimensions before any observation becomes a validated cluster.
Validation weights agreement across independent observers. A single low-trust observation cannot carry an incident on its own.
Observer identity contributes to the validation weighting. Higher-trust observers contribute more to forming a validated cluster.
A lone low-trust observation cannot carry an incident on its own. Bad-faith submissions are resisted by multi-observer convergence and trust-weighted scoring. Clusters can exist before any asset resolution; asset truth lives at the partner. The output to partners is a validated cluster — already through our validation layer.
An internal CEII, PII, and GDPR compliance review was completed in May 2026. That review — an internal opinion, not legal advice — produced the Reference-Number-Only Architecture that governs the platform today: it reduces our data-exposure surface to what the partner asset-resolution contract strictly requires, and explicitly removes the path that would have us holding an internal asset registry.
Cluster formation depends on multi-observer agreement and contextual evidence. No asset-match scoring against an internal asset catalog.
Clusters are bundled with validated evidence and thumbnails, then emitted to the partner webhook. The partner returns an opaque reference number — never an internal asset identifier.
We do not centralise power lines, transformers, utility poles, substations, power plants, or primary distribution feeders. There is no internal mirror of partner asset data to protect.
The audit ledger stores the opaque reference number, not a partner_asset_id, asset_type, or asset_label. Per-observation retention drops from seven years to thirteen months; a separate aggregates table holds seven-year FEMA-style summaries.
Centralising utility asset data — particularly criticality flags and partner-internal asset identifiers — approximates the surface that FERC Critical Energy / Electric Infrastructure Information (CEII) under 18 CFR § 388.113 and NERC CIP-011 / CIP-014 are designed to restrict. Holding precise GPS, timestamps, and device metadata for many years also creates a larger PII surface under CCPA / CPRA and similar state laws than is strictly necessary for downstream partner action. This architecture removes the first exposure entirely and reduces the second to a defensible window. For partners with European data subjects, GDPR applies; OpnIMG is sequencing a documented lawful basis, a Data Protection Impact Assessment, and a Schrems II Transfer Impact Assessment with the 2021 EU Standard Contractual Clauses (with the UK addendum where relevant) before any European partner data crosses the platform boundary.
We are focused on the three buyer types where validated observations meaningfully change downstream decisions: storm and disaster response, utility operations (storm-mode and steady-state), and municipal 311.
State Emergency Management Agencies, FEMA regional staff, county OEM, mutual-aid coordinators.
Tier-1 investor-owned utilities in the U.S. Gulf region, public-power, co-ops. Storm-mode and steady-state.
Tier-1 city public-works, code enforcement, transportation, ROW management.
OpnIMG has not yet been deployed under a paid partner pilot. The company is identifying potential pilot candidates and is open to warm introductions to Tier-1 investor-owned utilities in the U.S. Gulf region, to state Emergency Management Agencies, and to municipal 311 system operators.
Operational figures from specific storms are not asserted in external materials unless a source-validated figure exists at the time of writing. Counterfactual savings figures — for example, modelled avoided losses across historical storms — appear in OpnIMG materials only when labelled as model output, not as measurement.
Fifteen provisional patent applications on file with the USPTO. The portfolio covers the core multi-observer validation architecture that distinguishes the platform.
Specific claim coverage discussed under NDA.
Utilities, EM agencies, municipal CIOs, integration partners — use the form below. We do not publish email addresses.
