Service level & data freshness
Last updated: June 5, 2026
This page documents specific operational targets for Floodi. It does not constitute a guaranteed SLA unless separately agreed in writing with a pilot or government partner.
Operational targets
| Metric | Target | Notes |
|---|---|---|
| NWS alert polling | Every 15 minutes | Scheduled job calls api.weather.gov. Missed cycles self-correct on the next run. |
| USGS gauge polling | Every 15–30 minutes | Stream gauge readings pulled from waterservices.usgs.gov. Frequency varies by gauge availability. |
| Community report → map | < 5 seconds | Reports without photos appear on the map immediately after submission. Reports with photos are held pending AI moderation. |
| AI photo moderation | Typically < 30 seconds | Gemini Vision classification. If AI is unavailable, photos are queued for manual review (up to 48 hours). |
| Public map availability | 99%+ (no contractual commitment for community tier) | Hosted on Cloudflare edge with Supabase backend. Contractual uptime SLA available for government pilot agreements. |
| P1 incident acknowledgment | 4 hours (pilot partners) | A P1 incident is defined as: public map inaccessible, data ingestion stopped for > 1 hour during an active NWS warning, or loss of database connectivity. |
| P1 incident resolution target | 24 hours (pilot partners) | Best-effort resolution. Complex infrastructure failures may take longer. Partners are notified of status and ETA. |
| Data retention — active reports | Until resolved + 90 days | After 90 days, resolved reports are anonymized (coordinates generalized to county level, reporter data removed). |
| Data retention — government partners | Negotiated per agreement | Government pilot agreements specify retention schedule, secure disposal method, and export format. |
| Planned maintenance window | Tuesday 2–4 AM ET | Preferred window for schema migrations and infrastructure updates. Avoided during active NWS warning periods. |
What is NOT guaranteed
- Community tier uptime (best-effort, no SLA)
- Real-time photo approval (depends on AI availability and manual queue)
- 100% NWS/USGS data completeness (upstream sources can be delayed or unavailable during severe weather)
- Specific report volume or accuracy (community data is user-generated and not verified for factual accuracy beyond AI photo check)
Pilot partner commitments
For formally onboarded government or property management pilot partners, Floodi provides:
- A named support contact reachable by email during business hours (9 AM–6 PM ET, Mon–Fri)
- P1 acknowledgment within 4 hours of reported incident
- Written incident report within 5 business days of any P1 event
- Advance notice (minimum 48 hours) for planned maintenance that affects the public map
- A data export path so partners are never locked in — request at any time
- Written data governance terms before any data exchange begins
This SLA page applies to Floodi MVP / pilot phase only. Production government contract SLAs are negotiated and executed separately.