Operational Entry Surface

Quiet edge routing for small, fast-moving teams.

Adalat Edge Platform is a compact control surface for TLS entry, service routing, static delivery, and health publication. This node exposes a narrow public interface while keeping application movement predictable and measurable.

OnlineCurrent public service state fetched from the local edge health endpoint.

-- msObserved browser-side health probe time to the current node.

edge-msk-01Primary edge label served by the status document for this public node.

Service Fabric

The public node is designed around a thin entry layer, controlled local routing, and a deliberately small operational footprint. Shared-port handling, certificate automation, and endpoint fallback are used to keep the public face stable without widening exposure.

Edge TLS entrySingle-domain HTTPS ingress with certificate rotation and soft fallback behavior.

adalatvpn.lol:443

Health publicationMinimal public health endpoints for upstream probes and operator visibility.

/healthz · /api/status.json

Static deliveryInstrumented landing surface with browser-side checks and compact status rendering.

static + JSON

Service routingLayered local dispatch for website traffic, transport handling, and control-plane separation.

edge split / fallback

Published Endpoints

GET /healthzPlain health check for lightweight liveness probes.

text/plain

GET /api/status.jsonCompact node status document with role and capability summary.

application/json

GET /api/regions.jsonStatic region manifest describing public entry labels.

application/json

Sample response

{
  "status": "ok",
  "node": "edge-msk-01",
  "role": "public-edge",
  "site": "adalatvpn.lol"
}

Change Window

This node is optimized for low-touch maintenance. Public surface changes are kept narrow, certificate handling is automatic, and health paths are stable so external monitors do not need frequent reconfiguration.

Certificate automationRenewal is exercised regularly and reload hooks refresh the entry services after successful updates.

automated

Access policyOnly SSH and HTTPS remain exposed at the firewall boundary for this node.

22/tcp · 443/tcp

Status publicationPublic health output stays intentionally small to reduce accidental disclosure.

narrow surface