What it is
Safe-now.live is a sub-10KB static site aggregating US federal disaster declarations and state-level emergency information. Built entirely in HTML/CSS with no JavaScript dependencies, it lists active FEMA disasters (currently six severe winter storms across WV, NC, IN, KY, TN, AR) and links to local emergency resources by state and territory.
The site includes quick-reference guides for earthquake, tornado, flood response and emergency kit checklists sourced from Ready.gov. It's designed to load on degraded networks during infrastructure outages.
Why it matters
The architecture is notable for what it doesn't include: no backend, no dynamic content, no third-party scripts. This matters during actual disasters. LA County's recent South El Monte fire response (Jan 28 shelter-in-place order) relied on Alert LA County's multi-channel system—text, email, phone—but those systems assume functioning cellular infrastructure.
California's emergency ecosystem is fragmented: Cal OES manages 11 open federal disasters and administers $2.1B in grants, while local jurisdictions run separate opt-in systems (Alert Alhambra, NotifyLA, Rave Mobile Safety). Enterprise tech leaders expanding US operations face this patchwork—no single federal notification standard exists beyond Wireless Emergency Alerts.
The trade-offs
Static aggregation means no real-time updates beyond page refreshes. Official systems like Alert LA County offer targeted, localized instructions. Safe-now.live provides breadth (50 states plus territories) but lacks depth—users still need city-specific tools for actionable guidance.
The sub-10KB constraint is meaningful for APAC firms building similar systems for typhoon or earthquake zones. Japan's 110/119 emergency services and Australia's 000 system face identical bandwidth challenges during mass-casualty events. The question isn't whether this specific site scales, it's whether the pattern does.
What to watch
This is a reference implementation, not a replacement for established alert infrastructure. The real test comes when networks actually fail. History suggests static fallbacks matter—but only if users know they exist before they need them.