On the local node
- The launcher can list locally available applications and approved node information.
- Users on the node network can reach local routes without relying on the public website.
Wizaya Server Suite
PBB Landing
A local application launcher and safe projection of approved node metadata for people connected to a PBB node.
What it is
A service in the local-node foundation
Integrated · Production hardening
Baseline node service
PBB Landing is the local entry surface for a deployed node. It can show available applications, node identity, and carefully selected status information without exposing internal configuration.
It is distinct from this public marketing and documentation website. Any gateway or route behavior belongs to the local deployment and must be configured with a narrow public-data boundary.
Node role
What it contributes
Provides a clear local starting point for available PBB services while projecting only metadata that deployment owners have approved for that audience.
Service behavior
Local operation and connectivity
Across a route
- External routes remain deployment-specific and can be unavailable.
- The local launcher does not make every module or administrative endpoint public.
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.
Deployment placement
Where it fits
Baseline deployment
Barangay node; Local command node; Daily-apps node
Hardware, power, connectivity, training, travel, and field logistics remain deployment-specific.Operations and security
Boundaries operators must preserve
Operational considerations
- Keep launcher availability aligned with actual application health and policy.
- Define useful disconnected, degraded, and maintenance messages.
Security boundary
- Project only approved non-sensitive node metadata.
- Keep administrative routes and internal configuration out of the public launcher contract.
Practical questions
Frequently asked questions
Is PBB Landing this public website?
No. PBB Landing is the start page people use on a deployed local node. This public website explains the wider PBB platform.
Can the launcher work without internet access?
Yes, as long as the local node network, launcher service, and linked apps are working.
What node information may it display?
It should show only basic node information that has been approved for the people who will use the launcher. Private or administrative details should stay hidden.
Does it expose every local route through a gateway?
No. Only specifically approved routes should be available, and protected routes must require the right sign-in and security review.
How should unavailable applications appear?
The launcher should clearly say when an app is unavailable, partly working, or under maintenance instead of making it look ready to use.
Status and readiness
Integrated
Local application discovery and a safe node-metadata projection are implemented in the confirmed stack.
Remaining hardening work
- Finalize the approved public metadata contract for each deployment.
- Harden gateway routes and failure states before field release.
- Validate launcher content, branding, and application availability on pilot hardware.
Companion services
Related infrastructure
Broader platform context
Architecturally related modules
These relationships provide context and do not assert a confirmed current service integration. Verified integration paths appear in the earlier confirmed-integration list.
Briefing and pilot discussion
Discuss PBB Landing in a local PBB deployment
Explore how a local-node deployment could support practical service continuity in your community.