Infrastructure
Public edge to home server
This is the public path I operate: Cloudflare fronts mayphus.org, the Worker serves pages and APIs, runtime services answer behind it, and pb62 reports sanitized host health.
public path
How a request moves
mayphus.org receives the public request.
The public entry point stays stable for pages, tools, and status checks.
Cloudflare serves static assets and Worker routes.
The edge handles the public site surface before anything reaches a backend.
Runtime services answer tool and health requests.
The live service list below shows which public backends are currently responding.
pb62 publishes a sanitized host summary.
Only public-safe capacity and health signals are exposed.
network
Public edge, private network
- mayphus.org DNS and HTTPS traffic
- Cloudflare Worker routes and static assets
- public APIs such as status and project metadata
- sanitized health summaries only
- host addresses and internal service names stay hidden
- admin, repair, and recovery paths are not public pages
- private inventory and credentials are never exposed
- only public-safe checks cross the boundary
The page shows enough network shape to understand operations without publishing a usable private topology.
live system
Current state
These cards read the deployed status endpoint. They show the public edge, the runtime checks, and the host summary without exposing private details.
runtime
Services
Checks
0
Healthy
0
Latency
--
site index
Checking /pages.json
pending
Waiting for live status.