Comms fail during disasters
Power loss, signal congestion, and damaged infrastructure can cut off reliable reporting right when decisions matter most.
Organizing team and legal structure (in progress)
Practical tech for practical rescue.
Offline-first disaster reporting and coordination for when networks fail—designed for barangays, responders, and EOCs to share a common operational picture.
OFFLINE-FIRST
Works without internet; syncs automatically when backhaul returns.
- Offline-first
- Capture locally, sync later
- Rapid-deploy
- Local node kit + workflows
- Accountable
- Status + handover tracking
Why this matters
Reports become fragmented
Updates split across calls, chats, paper logs, and spreadsheets—making it hard to verify and consolidate.
Decisions slow down
Without a shared operational picture, response teams lose time coordinating, validating, and prioritizing actions.
What’s coming
A practical set of tools and workflows that operate locally first, then synchronize when backhaul is available.
Offline reporting
Structured forms, photos, status updates, and queues that keep working without internet.
Local node kits
Barangay-level capture + coordination node for temporary operations and consolidation.
Uplink sync to EOC
When LTE/Starlink returns, queued reports sync to the command post for consolidation and action.
Dashboards + SITREPs
Data freshness, queues, summaries, and basic situation reporting for operators.
Missing & relief tracking
Simple accountability flows: missing/found updates, dispatch → arrival → handover status.
Pilot direction (high-level)
- Target environments: signal-poor and upland barangays, evacuation centers, and rapid relief handover points.
- Primary outcomes: faster verified reporting, reduced duplication, clearer handovers, improved prioritization.
- Evaluation: operational usability, reliability under low connectivity, and data quality.
What success looks like
- Operators can consolidate field reports in minutes—not hours.
- Queues visibly drain once backhaul returns; dashboards show “data freshness.”
- Relief and response actions leave a clear audit trail (who, what, when, where).
Partners information
We are assembling governance, pilot hosts, and evaluators. If your organization can contribute capacity, we want to hear from you.
LGU pilot hosts
Barangay/City/Province partners for pilot deployment, operator coordination, and field validation.
Agencies & responders
Operational requirements, workflows, and interop guidance to ensure the system fits real response.
Donors & supporters
Support for kits, training, evaluation, and maintaining readiness between disasters.
Safeguards
Designed to be useful in emergencies while minimizing risk and protecting people’s data.
Privacy-by-design
- Collect only what is necessary for coordination and accountability.
- Role-based access (operators, supervisors, auditors) with defined permissions.
- Data retention and deletion policy (in development) aligned to operational needs.
Security posture (high-level)
- No public incident feeds by default.
- Audit logs for critical actions (creation, edits, handovers).
- Responsible disclosure channel for vulnerabilities.
Stay connected
Use the form below to request a briefing, explore partnership, or receive pilot updates.