Citizens
Access help, announcements, communication, and essential services through the local PBB network.
Offline-first · Local-node first · Public service
Keeping communities connected, informed, served, and coordinated — online or offline.
Project Bantay Bayan helps barangays, LGUs, health centers, responders, schools, NGOs, donors, and utilities keep essential local services available when connectivity is weak, intermittent, or unavailable.
Local services should not stop just because the internet stops.
Core continuity promise
Cloud where available. Local where necessary.
PBB places useful digital services on a local node so the community network can continue serving people without a constant cloud connection.
- Essential services remain reachable on the local network.
- Local records and prepared resources remain close to the teams using them.
- Selected reports and updates can move upstream when a route returns.
Who benefits
Built for the people who keep communities moving
PBB supports everyday public-service work and coordinated readiness across local institutions.
Barangays
Operate a local digital front desk for reports, advisories, maps, and coordination.
Businesses and CSR partners
Support local continuity efforts and contribute resources during disruptions.
LGUs
See structured reports, support requests, and service status from the barangay level.
Health centers
Keep basic health workflows and continuity-of-care support available locally.
Utilities
Receive clearer incident context when events may affect essential services.
Schools and youth
Use local learning and preparedness content even when mobile data is unreliable.
Donors and NGOs
Fund a living resilience capability that communities can use before and during emergencies.
Daily-use adoption
Useful before an emergency. Familiar when it matters.
A citizen may use the local network for announcements, health schedules, learning content, and community messages. When disruption arrives, that familiar network becomes a reporting and coordination channel.
Daily use creates habit. Habit creates adoption. Adoption creates readiness.
How PBB works
Continue locally. Deliver selectively.
“Offline-first” in PBB normally means local-server and LAN continuity. It does not mean every browser has a durable queue or every application database is synchronized.
- Serve the community locally.Citizen and operational modules use the node network and local supporting services.
- Keep work close to its owner.Records stay with the responsible module unless a confirmed integration says otherwise.
- Move selected updates.Relay handles defined store-and-forward messages; large Library releases use their own signed distribution path.
Featured modules
One platform, coordinated service layers
PBB Hotline / Vox
Local emergency intake, incident handling, command reporting, and support coordination.
Explore Vox
PBB Natalium / Natalium
Local patient registry and continuity-of-care workflows for community health services.
Explore Natalium
PBB Salus / Salus
Local evacuation-center registration, occupancy, and relief-receipt operations in active development.
Explore Salus
PBB Chat / Civitas
LAN-local rooms, direct messages, moderation, and emergency handoff for community communication.
Explore Civitas
PBB Library / Libria
Governed cloud releases and a local offline catalog for public knowledge resources.
Explore Libria
PBB Learning / Lumaria
A local learning gateway connecting providers, catalogs, and learning instances.
Explore Lumaria
PBB Utility / Vena
Inbound incident context and local mission coordination for designated utility operators.
Explore Vena
PBB Support System / Imperium
Consolidates SITREPs and manages support-request lifecycles at designated support nodes.
Explore ImperiumDeployment model
A service mix shaped around the local node
Baseline, optional, and specialized modules can be placed at barangay, command, health, learning, knowledge, field, support, or utility nodes according to real operating needs.
PBB provides the coordinated software platform and managed support layer.
Servers, networking, connectivity, power, travel, training, and field equipment are scoped separately unless explicitly bundled.
Node placement follows service ownership, privacy boundaries, and the realities of the local environment.
Readiness snapshot
Pilot-ready foundation
PBB has a strong integrated software foundation and is ready for structured pilot discussions. The next phase focuses on deployment hardening, security policy, data retention, field runbooks, and production-scale operations.
Platform integration9/10
Feature implementation8/10
Deployment preparation6/10
Security and governance5/10
Pilot readiness7/10
Overall readiness7/10Pilot-ready foundation
Technology foundation
Powered by Wizaya
The Wizaya Server Suite supplies local identity, selective relay delivery, live events, prepared maps, observer-only worker telemetry, a local launcher, and deployment tooling.
These components make PBB modules operate as one coordinated platform. They are not presented as separate citizen apps.
See the infrastructure layer →Briefing and pilot discussion
Bring local digital resilience to your community.
Request a briefing, explore a partnership, or discuss a structured pilot. Submitting uses the existing Formspree endpoint; if it is unavailable, your email application opens as a fallback.
- No operational feeds are submitted through this form.
- Hardware and field logistics remain deployment-specific.
- Pilot scope and safeguards are reviewed before live use.