PyroTech is a real-time incident command platform that simulates wildfire response using a multi-agent orchestration layer powered by Google Gemini. It combines physics-based fire modeling with real-world geospatial data to provide a 3D decision-support dashboard.
- Purpose: Real-time simulation and tactical recommendation for wildfire disasters.
- Key Features:
- Physics-Informed Fire Spread: Vector-based elliptical growth engine driven by wind, humidity, and temperature, with distinct head/flank/back fire sectors.
- Hard-Stop Dozer Barriers: Dozer firebreaks act as true containment lines integrated directly into the perimeter calculation, not post-hoc subtraction.
- Automatic Suppression Prestaging: Resource deployments automatically generate suppression zones ahead of the predicted fire path.
- Dynamic Traffic & Evacuation: Real-time congestion modeling that reacts to fire proximity and auto-closes routes intersecting the perimeter.
- Multi-Agent Orchestration: Eight specialized LLM agents (Disaster, Evacuation, Resource, Infrastructure, Communications, Congestion, Synthesis) coordinate response over a virtual radio net with conflict detection.
- What-If Branching: Fork the simulation at any tick to explore alternative tactical outcomes (e.g., wind shifts).
- Live Geospatial Data: Fetches infrastructure, roads, and population on-the-fly via OSM Overpass, NASA FIRMS, and Census Bureau.
- Voice Radio Net: Optional ElevenLabs TTS for radio-style agent transmissions.
- Frontend: Next.js 16, React 19, TypeScript, Tailwind CSS v4, Mapbox GL v3, deck.gl v9.
- Backend: Node.js 20, Express 5, WebSocket (ws), Google Gemini (
@google/genai), Postgres, Redis (ioredis), pdfmake. - Geospatial: Turf.js for polygon intersections and spatial operations.
- Data Sources: OpenStreetMap (Overpass API), NASA FIRMS (live fire detection), Census Bureau (population density).
- Node.js 20+
- Google Gemini API Key
- Mapbox Public Token
- (Optional) ElevenLabs API Key for voice synthesis
- Clone the repository.
- Install dependencies:
# Backend cd backend && npm install # Frontend cd ../frontend && npm install
- Set up environment variables (see
.env.examplein each folder).
- Start the backend:
cd backend && npm start(runs on port 4000) - Start the frontend:
cd frontend && npm run dev - Navigate to
http://localhost:3000.
The simulation runs on a dual-loop system:
- Physics Loop (500ms): Updates continuous visual states — fire perimeter growth, evacuation vehicle particles, route congestion, and suppression geometry.
- Agent Cycle (~30 logical min): Triggers the LLM agents sequentially to analyze the situation, resolve conflicts via the Synthesis agent, and issue new tactical orders as structured map events.
DisasterAgent— Predicts fire spread and threat zones.EvacuationAgent— Manages road closures, shelters, and zone statuses.ResourceAgent— Deploys engines and dozers with[lng, lat]coordinates.InfrastructureAgent— Monitors power, water, and hospitals.CommunicationsAgent— Generates public alerts.CongestionAgent— Monitors and manages evacuation traffic flow.SynthesisAgent— Resolves agent conflicts and builds the Incident Action Plan.
wildfireEngine.js— Elliptical perimeter growth with wind/weather inputs.suppressionProbe.js— Dozer barrier and engine sector suppression geometry.resourceModel.js— Tracks assigned resources and computes their suppression effects.trafficModel.js— Dynamic route congestion and fire-driven closures.particleEngine.js— Ambient evacuation vehicles on the OSM road graph.stateManager.js— Canonical event log supporting branching and replay.
PyroTech uses a "merged geospatial state" model:
- Pre-seeded data: Baseline infrastructure for Los Angeles (Palisades area).
- Dynamic data: Fetched on-demand for the bounding box of any city worldwide during the Setup phase.
- Spatial Intersections: Infrastructure damage, route closures, and suppression effects calculated via real-time polygon intersections (
turf.js).
