Platform

One incident record. Every screen that needs it.

MapsBox is a live map, an operations console, an AI intake that reads plain-English reports, a driver app and a public API, all reading from one record of what is happening on your roads.

Operations console

Triage, update and clear incidents from one queue

Your operators work from a single list of incidents with the map beside it. Filter by status, severity or type, search by road or location, and open any row to edit it.

  • Set severity, lanes affected and direction of travel separately for each incident
  • Clear an incident and reopen it later if conditions return
  • Every change is written to an activity log with the user who made it
Live incident map · Austin, TX (demo)

Live incident map

The network at a glance, colored by severity

Incidents plot on a MapLibre map over OpenStreetMap data. Major, moderate and minor incidents have their own colors, and an incident disappears from the active view as soon as it is cleared.

  • Opens on the metro area you pick when you create your workspace
  • Place a new incident by clicking the road where it happened
  • The demo on this page uses simulated incidents

AI report intake

Paste the message. Confirm the incident.

A trooper text, a dispatcher note or a driver message goes in as written. Intake pulls out the road, direction, event type, severity, lanes and nearby location, and shows how confident it is. An operator reviews the draft before it is published.

  • Understands highway names, directions, lanes and cross streets
  • Recognizes crashes, closures, construction, hazards and congestion, plus “cleared” updates
  • The same parser is available to your own systems at POST /v1/reports/parse
Parse report endpoint
report.txt
Road work on TX-71 EB, left lane closed until 5 AM
Parsed incident
{
  "road": "TX-71",
  "direction": "Eastbound",
  "event": "construction",
  "severity": "moderate",
  "lanes": "left lane",
  "location": null,
  "confidence": 0.95
}

Driver app

The people on the road see what you see

The driver app puts your published incidents on a phone. Drivers save the roads they use and get an alert when something changes on them, and field staff can send reports back.

  • Alerts for saved roads
  • Photo and video reports from the field
  • Offline support: reports queue on the device and sync when signal returns
  • Available under your own name with the white-label option
Ask about the driver app

Public API & GeoJSON feeds

Feed your own maps, dashboards and dispatch tools

Every incident in your workspace is available over a REST API. Request a bounding box as GeoJSON for a web map, post incidents from a sensor or CAD system, and update them as they change. Tokens are created in the console and carry read or write scope.

Read the API reference
Create an incident from a plain-English report
curl -X POST https://mapbox.cc/v1/incidents \
  -H "Authorization: Bearer mbx_YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "report": "Crash on I-35 southbound near Riverside Dr",
    "lng": -97.73,
    "lat": 30.25
  }'

Team roles & activity log

Give each person the access their job needs

Invite teammates by link and choose a role. Roles are enforced on the server for every request, not just hidden in the interface.

RoleCan do
ViewerRead incidents, the map and the activity log.
OperatorEverything a viewer can, plus create, edit and clear incidents and use AI intake.
AdminEverything an operator can, plus delete incidents, manage API tokens and team members, and change workspace settings.
OwnerAn admin who cannot be removed or demoted. The person who created the workspace.

Security

Built to hold operational data

The controls we rely on today. We do not claim certifications we do not hold.

  • Hashed passwords

    Passwords are stored as salted PBKDF2 hashes, never in plain text.

  • Protected sessions

    The session cookie is HttpOnly, Secure and SameSite. Changing a password revokes other sessions, and you can sign out everywhere.

  • Hashed API tokens

    Token secrets are shown once and stored as hashes. Revoke a token in the console at any time.

  • Server-side roles

    Viewer, operator, admin and owner permissions are checked on every request.

  • HTTPS everywhere

    Traffic is served over HTTPS from the Cloudflare edge.

  • Abuse controls

    Rate limits on sign-in and sign-up, and bot protection on sign-up with Cloudflare Turnstile.

Details on data handling are in the Privacy policy.

Try it on your own network

Every account starts with a 14-day trial workspace.