Topology
Connectors#
A connector is a small service you run inside a network. It:
- holds the network's identity and renews its certificate,
- maintains outbound sessions to the edge,
- publishes local services and enforces policy on both inbound and outbound flows,
- resolves
*.proxnames for local clients.
It needs no inbound reachability and no public address. One connector per network boundary is the minimum; two is the production answer.
Edge#
The edge is the ScaiLabs-operated relay. Connectors attach to the two nearest edge points in their region and keep both sessions warm. The edge authenticates connectors, relays ciphertext between them, and emits metadata events. It evaluates no policy and holds no session keys.
Regions follow the ScaiLabs <region>-<level> convention, matching Storey and
Scuttle:
| Region | Location | Level |
|---|---|---|
nlwest-std |
Netherlands, west | Shared |
nlsouth-std |
Netherlands, south | Shared |
Failure behaviour#
Being specific about failure is more useful than claiming resilience.
| What fails | What happens |
|---|---|
| One edge point | Connectors shift to their second session. Established sessions are re-established; in-flight connections drop and must reconnect |
| A whole region | Connectors re-attach to the other region. Latency rises; service continues |
| One connector of a redundant pair | Its sessions drop. The peer carries the load. Clients reconnect |
| The only connector in a network | That network is unreachable until it returns. Nothing else is affected |
| The control plane | Data plane keeps running. Existing policy stays enforced and sessions keep working. You cannot enrol, change policy or publish services until it returns |
| Certificate renewal failing | The connector keeps working until its certificate expires, then stops being trusted. Alert on renewal failure, not on expiry |
The control-plane row is the important one: a control-plane outage must not take customer traffic down, and it does not.
Sizing#
A connector is mostly cryptography and copying. Throughput scales with cores; budget roughly one core per gigabit of sustained encrypted traffic, plus headroom for rekeying. Memory is a function of concurrent sessions rather than bandwidth. Real numbers belong in Connect a network once the team has benchmarked the shipped build.