Platform
How the network is assembled.
A short technical description of the control plane, the data plane and the telemetry you get from both.
Control plane
Declarative. You describe desired state; the reconciler converges and reports drift.
# create an instance curl -s https://sla.sunlawai.com/api/v1/instances \ -H "Authorization: Bearer $TOKEN" \ -d '{"region":"lax","vcpu":2,"mem_mb":4096}' # response {"id":"ins_8f21c","state":"provisioning","ipv4":"…","eta_s":90}
Data plane
Ingress
Anycast announcement from two upstreams. Inbound policy is applied at the first hop, not after crossing the fabric.
Transit
Private tunnels carry traffic to your origin over a path we select per destination, with explicit congestion control.
Egress
Landing endpoints are health-checked every 30 seconds; two consecutive failures shift the selector.
Telemetry
Per-path, per-minute, retained 30 days. The same numbers we use internally are exposed to you.
- Round-trip time, jitter and loss per path and per upstream.
- TCP retransmits and congestion-window samples from both ends of a tunnel.
- Handshake timings: DNS, TCP, TLS, first byte — reported separately.
- Selector events: who switched which path, when, and why.