Dedicated instance

Most teams run on the shared, multi-tenant service and never think about where it runs. A dedicated instance is for the teams that do: a single-tenant deployment of the same gateway, on isolated infrastructure we provision and operate, in the region you choose. No other customer's traffic touches the machine.

It is the same product, not a different one. The console, drift dashboards, coverage, alerting and the version diff are exactly what you already use; what changes is the data plane underneath your proxies - yours alone, sized for your traffic, in your region.

What you get

• Single-tenant isolation. Your gateway runs on infrastructure dedicated to your account, isolated from every other customer. Nothing is shared at the data-plane layer.
• Region of your choice. We deploy the instance where it suits your latency and your compliance posture.
• Dedicated capacity and SLA. Throughput is provisioned for your traffic rather than drawn from a shared pool, and the Business SLA (99.9%, four-hour response) applies.
• We operate it. Provisioning, upgrades, capacity and on-call are ours. You get the isolation without taking on the running of it.

What stays the same

Everything you already do. Proxies, specs, environments, drift, coverage, alerts and the API and CLI all work identically - a dedicated instance is where your proxies run, not a separate console to learn. The data processed is exactly as described in What leaves your network and our DPA; the difference is that no other customer shares the instance.

Getting one

A dedicated instance is a Business-plan feature. Tell us your expected traffic and preferred region; we provision it, migrate your proxies onto it, and cut over - the slug and the console stay the same, so nothing your clients call has to change.