Website availability
The public site provides reference pages, guides, downloads, an account workflow and an operator console. There is no contractual website uptime commitment, maintenance notification service or published service-level agreement in this prelaunch project.
Locations versus gateways
The 249 country and territory entries are reference records. A country page does not reserve an IP address, provide an exit node or guarantee local connectivity. Registered gateway records, when present, are separately reported by the application.
What a heartbeat means
A gateway agent can send an authenticated report about its interface and peer count. A recent report is an operational signal. It does not independently prove client reachability, a working tunnel, internet egress, DNS privacy, performance or a commercial service entitlement.
Self-hosted connections
For your own gateway, actual availability depends on the host, router, network path, public reachability, configuration and native client. A record in the console does not configure NAT, open a port, assign a peer or repair a third-party network.
Support and maintenance
Signed-in requests are saved for operator review and can receive replies inside the account. No 24-hour staffing, response deadline, emergency service or instant email notification is offered. Read the status and roadmap pages for current release work.
Future service commitments
Any commercial launch must clearly define supported locations, maintenance practice, capacity, support availability, material service limits and any applicable remedy. Those commitments must reflect tested infrastructure rather than reference data or a demonstration.