How it works
Plug in. Run. Send back. Infra runs beside the system you have.
Plug in. Run. Send back.
Infra runs beside the system you have. Nothing is replaced.
- In: Open311 GeoReport v2, CSV / ArcGIS import, resident intake
- Run: triage, merge, route and incidents inside Infra Atlas
- Out: signed webhook JSON back to your system
Results go back to your current system through signed webhooks.
Connect
Reports reach Infra Atlas through the Open311 create endpoint, a one-time import from ArcGIS, CSV or SeeClickFix, resident intake, or Infra Lens detections.
POST /api/open311/v2/requests
Atlas runs it
AI triage, duplicate merge, crew routing, incidents and FEMA costs all work from the same report and the same map.
Example: AI triage, duplicate merge, crew routing
Send back
Report events go to your endpoint as signed webhooks. Cityworks and Accela adapters are coming.
X-Civic-Signature: HMAC-SHA256 of the raw body
What changes for your team
Your current system stays where it is. Reports keep arriving the way they do now, and they also arrive through the Open311 create endpoint, one-time imports from ArcGIS, CSV or SeeClickFix, photo reports from residents, and detections from Infra Lens.
Triage, duplicate merging, crew routing and incident cost tracking all work from the same report and the same map. Staff correct a classification when it is wrong, and that correction is stored.
Results go back to your system as signed webhooks your endpoint verifies with a shared secret. Vendor adapters for Cityworks and Accela are planned and not built yet, so until they exist the webhook is how results travel back.
Pilot in 4 steps
Connect
Point your Open311 feed, an import file, or resident intake at Infra. Nothing in your current system is switched off.
Choose features
Pick which capabilities to run for the pilot, such as AI triage, duplicate merge, crew routing, or Lens video detection. Each one runs as its own module.
Run alongside your current system
Infra processes reports next to your existing queue. Staff keep working where they work today, and results arrive back through signed webhooks.
Decide
Review what the pilot caught, merged and routed, then decide whether to keep going. The import and webhook paths stay open either way.
Who it is for
311 and customer service
Every call and form becomes a sorted report with a category and severity, so the queue answers itself first.
Public works crews
Work orders arrive with a photo, a precise location and a materials estimate, so crews roll out once.
Emergency management and finance
Disaster reports group into incidents with costs logged as work happens, ready for FEMA documentation.
What is live, what is coming
Newest first. Every line matches what the product does today.
Infra Atlas
- AI triage with work ordersCategory, severity and cost estimate on every reportLIVE
- Duplicate merge and crew routingOne work order per defect, sent to a staffed crewLIVE
- Resident intake and Open311 APIWeb, SMS and QR reports, read and create endpointsLIVE
- Privacy blur and signed webhooksFaces and plates blurred on device, signed deliveryLIVE
- FEMA documentation checklistReadiness check and cost exports per incidentLIVE
- Cityworks and Accela adaptersWrite results back into the system you already runCOMING
Infra Lens
- Video damage detectionDashcam clips group repeat sightings into one taskLIVE
- Live traffic cameras and hazard feedsPublic cameras through the damage detector, incidents from hazard feedsCOMING
Start with Atlas, Lens, or both.
Tell us which system you use and which parts matter. We will map the connectors with you.