Welcome to FireBreak Platform Documentation¶
Wildfire risk assessment, done right. Fast, global, and ready for anything.
-
Wildfire Risk Assessment Platform
FireBreak is a production-ready, multi-tenant wildfire risk assessment platform built on Cloudflare's edge infrastructure. Analyze risk factors, generate reports, and deliver real-time insights to protect communities from wildfire threats.
-
Cloud-Native & Scalable
Built entirely on Cloudflare Workers, Pages, R2, D1, and KV for global edge deployment with zero cold starts and unlimited scale.
-
Enterprise Multi-Tenant
Complete tenant isolation with dedicated subdomains, custom branding, and per-tenant resource limits. Perfect for white-label deployments.
-
Developer-Friendly API
RESTful API with OpenAPI 3.0 specification, interactive documentation, and comprehensive error handling.
What is FireBreak?¶
FireBreak is a next-generation wildfire risk assessment platform that combines:
- Geospatial Analysis: Process terrain, vegetation, and weather data to calculate risk scores
- Real-Time Weather: Integrate with weather APIs for current conditions and forecasts
- Report Generation: Automated PDF reports with maps, charts, and recommendations
- Multi-Tenant Architecture: Serve multiple clients with complete data isolation
- Edge Deployment: Global CDN distribution via Cloudflare Workers
Key Features¶
- ✅ Python Backend - Geospatial processing with numpy, rasterio, and shapely
- ✅ JavaScript Frontend - Modern React/TypeScript UI with Mapbox GL
- ✅ Cloudflare Stack - Workers, Pages, R2, D1, KV, Images, Stream
- ✅ Multi-Tenant - Complete isolation with dedicated subdomains
- ✅ Automated Testing - Unified QA harness with unit, integration, and E2E tests
- ✅ CI/CD Pipeline - Automated deployment with rollback capability
- ✅ OpenAPI Spec - Interactive API documentation with Swagger/Redoc
- ✅ Monitoring - Real-time metrics, logging, and alerting
Quick Links¶
🚀 New to FireBreak?¶
- Quick Start Guide - Get up and running in 5 minutes
- Installation - Full installation guide
- First Deployment - Deploy your first instance
- Local Development - Set up your dev environment
🏗️ Understanding the Architecture¶
- System Overview - High-level architecture
- Multi-Tenant Design - How isolation works
- Security Model - Security architecture
- Decision Records - Why we chose this stack
📚 API & Development¶
- API Documentation - Complete API reference
- Authentication - API key management
- Coding Standards - Code style guide
- Contributing - How to contribute
🚢 Deployment & Operations¶
- Backend Deployment - Deploy Python workers
- Frontend Deployment - Deploy React app
- Multi-Tenant Setup - Provision new tenants
- Troubleshooting - Common issues
Platform Architecture¶
graph TB
subgraph "Edge Layer - Cloudflare Global Network"
A[Cloudflare Pages<br/>Frontend CDN]
B[Cloudflare Workers<br/>Python Backend]
C[Cloudflare Images<br/>Image Processing]
end
subgraph "Storage Layer"
D[R2 Object Storage<br/>Maps, Reports, Data]
E[D1 Database<br/>Structured Data]
F[KV Storage<br/>Cache & Config]
end
subgraph "External Services"
G[Weather APIs]
H[Terrain Data]
end
User([User Browser]) -->|HTTPS| A
User -->|API Requests| B
B --> D
B --> E
B --> F
B --> C
B --> G
B --> H
style A fill:#f96,stroke:#333,stroke-width:2px
style B fill:#fc9,stroke:#333,stroke-width:2px
style C fill:#9cf,stroke:#333,stroke-width:2px
style D fill:#9f9,stroke:#333,stroke-width:2px
style E fill:#9f9,stroke:#333,stroke-width:2px
style F fill:#9f9,stroke:#333,stroke-width:2px Technology Stack¶
| Layer | Technology | Purpose |
|---|---|---|
| Frontend | React + TypeScript | User interface and mapping |
| Backend | Python 3.11+ | Geospatial processing and API |
| Runtime | Cloudflare Workers | Edge compute platform |
| Storage | R2, D1, KV | Object storage, database, cache |
| CDN | Cloudflare Pages | Global content delivery |
| Testing | Pytest, Vitest, Playwright | Automated testing |
| CI/CD | GitHub Actions | Deployment automation |
| Monitoring | Cloudflare Analytics | Metrics and logging |
Development Teams¶
FireBreak is developed by specialized teams working in parallel:
- Team Alpha - Backend & API development (backend/CLAUDE.md)
- Team Beta - Frontend & UI (frontend/CLAUDE.md)
- Team Gamma - Multi-Tenant infrastructure (tenants/CLAUDE.md)
- Team Delta - QA & Testing (qa/CLAUDE.md)
- Team Epsilon - DevOps & CI/CD (.github/CLAUDE.md)
See Team Coordination for workflow details.
Current Status¶
Production Ready
FireBreak 3.0 is currently in active development with the following milestones:
- ✅ Architecture - Complete system design and ADRs
- ✅ Monorepo - Organized codebase structure
- 🚧 QA Harness - Sprint 0 (in progress)
- 📋 Core Migration - Sprint 1 (planned)
- 📋 Multi-Tenant - Sprint 2-3 (planned)
See Changelog for detailed version history.
FireBreak Tip
New to FireBreak? Start with our Quick Start Guide and you'll be running risk assessments in under 10 minutes.
Support & Community¶
- 📖 Documentation: You're reading it!
- 💬 Issues: GitHub Issues
- 🔧 Source Code: GitHub Repository
- 📧 Support: See Support Channels
License¶
FireBreak is proprietary software. See License for details.
Ready to get started?
Need help?