Project Bantay BayanCommunity resilience infrastructure

Wizaya Server Suite

PBB Kit Setup

Windows-oriented provisioning and service orchestration for preparing a repeatable PBB local-node installation.

What it is

A service in the local-node foundation

Integrated · Production hardening Baseline node service

PBB Kit Setup prepares the confirmed Windows local-node stack, including WAMP-oriented application prerequisites, local name services, service configuration, and required data locations.

Provisioning still requires administrative access, deployment-specific secrets, verified artifacts, and recovery planning. FRP appears in planning material but is not presented as a confirmed implemented setup feature.

Node role

What it contributes

Turns approved software artifacts and deployment configuration into a repeatable managed local-node installation with known services and data locations.

Service behavior

Local operation and connectivity

On the local node

  • Prepares application prerequisites, local services, configuration, and persistent data paths on the node.
  • Supports Windows service lifecycle and local name-resolution setup for the confirmed stack.

Across a route

  • Artifact acquisition and updates require an approved delivery path or offline media process.
  • FRP connectivity is planned material, not a confirmed public implementation claim.

Confirmed current integration

Modules with verified service paths

Only module integrations confirmed in the current implementation are listed here. Planned packaging, architectural relationships, and unverified paths are excluded.

Emergency and operations PBB Hotline / Vox Local emergency intake, incident handling, command reporting, and support coordination.
Emergency and operations PBB Support System / Imperium Consolidates SITREPs and manages support-request lifecycles at designated support nodes.
Health and welfare PBB Natalium / Natalium Local patient registry and continuity-of-care workflows for community health services.
Community communication PBB Chat / Civitas LAN-local rooms, direct messages, moderation, and emergency handoff for community communication.
Community engagement PBB Games / Tabulus Optional local engagement and preparedness-learning experiences with emergency-mode safeguards.
Utility and public service coordination PBB Utility / Vena Inbound incident context and local mission coordination for designated utility operators.

Deployment placement

Where it fits

Baseline deployment

Barangay node; Local command node

Hardware, power, connectivity, training, travel, and field logistics remain deployment-specific.

Operations and security

Boundaries operators must preserve

Operational considerations

  • Verify administrative privileges, hardware, storage, power, and recovery media before installation.
  • Record artifact versions, checksums, secrets ownership, backup locations, and rollback steps.

Security boundary

  • Run provisioning only from trusted signed artifacts under authorized administration.
  • Keep deployment secrets out of public bundles and review every remote-access mechanism separately.

Practical questions

Frequently asked questions

What operating environment does Kit Setup target?

It currently targets Windows computers. It prepares the web server, database software, local service names, and storage locations needed by the node.

Is deployment completely automatic?

No. An authorized person must still check the hardware, choose how the node will connect, protect passwords and keys, verify the installation files, make backups, and approve the completed setup.

Does Kit Setup configure FRP today?

No confirmed implementation does this today. FRP appears in planning documents, but it is not presented as a working Kit Setup feature.

How should node software be updated?

Use approved installation files, confirm their version and authenticity, make a protected backup, schedule the work, test the result, and keep a proven way to return to the previous version.

Where should deployment secrets be stored?

Passwords, security keys, and similar private information should be kept in protected storage managed by the deployment owner. They should never be placed in public installation files or documentation.

Status and readiness

Integrated

Windows-oriented preparation, local service setup, Technitium integration, and data-directory orchestration are implemented.

Remaining hardening work

  • Publish a signed, repeatable release and rollback procedure.
  • Complete secrets, backup, and field-recovery runbooks.
  • Treat FRP as planned until implementation evidence and security review are complete.

Companion services

Local-node infrastructure PBB Landing Local launcher and safe node metadata projection. Local-node infrastructure PBB Maestro Observer-only worker telemetry and health visibility. Local-node infrastructure PBB MapServer Prepared local map tiles and boundaries.

Broader platform context

These relationships provide context and do not assert a confirmed current service integration. Verified integration paths appear in the earlier confirmed-integration list.

Emergency and operations PBB Hotline / Vox Local emergency intake, incident handling, command reporting, and support coordination.
Health and welfare PBB Natalium / Natalium Local patient registry and continuity-of-care workflows for community health services.
Learning and knowledge PBB Library / Libria Governed cloud releases and a local offline catalog for public knowledge resources.

Briefing and pilot discussion

Discuss PBB Kit Setup in a local PBB deployment

Explore how a local-node deployment could support practical service continuity in your community.

Request a briefing