Skip to main content
Kernel proxies enable you to route browser traffic through different types of proxy servers, providing enhanced privacy, flexibility, and bot detection avoidance. Proxies can be created once and reused across multiple browser sessions.

Proxy Types

Kernel supports four types of proxies:
  1. Datacenter - Traffic routed through commercial data centers
  2. ISP - Traffic routed through data centers, using residential IP addresses leased from from internet service providers
  3. Residential - Traffic routed through real residential IP addresses
  4. Custom - Your own proxy servers
Datacenter has the fastest speed, while residential is least detectable. ISP is a balance between the two options, with less-flexible geotargeting. Kernel recommends to use the first option in the list that works for your use case.

1. Create a proxy

Create a proxy configuration from the types above that can be reused across browser sessions:

2. List your proxies

View all proxy configurations in your organization:

3. Use with browsers

Once created, you can attach a proxy to any browser session using the proxy_id parameter:

4. Bypass hosts

Configure specific hostnames to bypass the proxy and connect directly. This is useful for accessing internal services, metadata endpoints, or reducing latency for trusted domains.

Bypass host rules

  • Exact hostnames: example.com, api.service.local
  • Wildcard subdomains: *.example.com matches api.example.com, cdn.example.com, etc.
  • Maximum 100 entries per proxy
  • Maximum 253 characters per hostname
  • Hostnames are case-insensitive and automatically normalized
  • Ports, paths, and URL schemes are not allowed
  • IP addresses are not supported—use hostnames only
Bypass hosts is available on Start-Up and Enterprise plans.

5. Update a browser’s proxy

You can hot-swap the proxy on a running browser session without restarting it. This updates the proxy configuration immediately — all subsequent network requests from the browser will use the new proxy.
The browser’s network is momentarily disconnected during a proxy hot swap. Any in-flight requests may fail.
The update is synchronous — when the call returns, the proxy swap is fully applied and all new browser traffic routes through the updated proxy. The swap typically completes in 2–3 seconds.
If you swap the proxy on a browser acquired from a pool, the browser will be reset back to the pool’s default proxy configuration when it is released. Releasing the browser will be delayed by the swap duration (~2-3 seconds) while the proxy is restored to the pool default.

6. Delete a proxy

When no longer needed, delete the proxy configuration:
Deleting a proxy immediately reconfigures associated browsers to route directly to the internet.