SYSTEM ONLINE | INFRASTRUCTURE · EU-CENTRAL-1
dns EDGE NETWORK

Frankfurt pods, 4.1ms from origin.

Capture latency is dominated by distance. The EU-Central cluster exists to remove it for European origins, with warm sessions ready before you ask.

dns

EU-Central Pods

Physical capacity in Frankfurt with redundant transit, so regional origins are captured from inside their own latency envelope.

pod.latency() → 4.1ms
route

Anycast Routing

Requests enter the nearest edge and are carried over private backbone to the pod holding the session.

route.optimize() → private
ac_unit

Warm Session Pool

Pre-hydrated browser sessions sit ready, so the first capture of a run does not pay the cold-start cost.

pool.warm() → 120 ready
bolt

Burst Capacity

Quotas are enforced on sustained rate, with headroom for spiky workloads instead of hard cliffs.

burst.headroom() → 3×
public

Regional Egress

Choose the country your traffic leaves from, independently of where the browser executes.

egress.region() → us / eu / br
monitor_heart

Observability

Per-request latency, resolution depth and failure reasons are exposed as metrics you can alert on.

metrics.export() → prometheus
cluster.status
STREAMING
region     pods   ready   p50      p99      status
eu-central-1 12    120   4.1ms    38ms     operational
us-east-1    6     60    38ms     96ms     operational
sa-east-1     3     30    94ms     180ms     operational
total active sessions 1,402   240 fps sustained