Network routing

Proxies, Tor and Owl Sidecar

Olib AI does not sell proxies or IP addresses. Owl Browser gives every browser context its own route: a proxy you already pay for (HTTP, HTTPS, SOCKS4, SOCKS5 or SOCKS5h), the Tor client bundled in the container with a separate circuit per context, or Owl Sidecar, an app that turns a device you own into a private exit.

Bring your own proxy

Set a proxy when you create a context, so parallel sessions can leave through different addresses from one engine.

  • Types: http, https, socks4, socks5 and socks5h (DNS resolved by the proxy).
  • By default the context's timezone follows the proxy's location (proxy_spoof_timezone); override it with proxy_timezone_override or timezone.
  • HTTPS-inspection proxies such as mitmproxy work with a custom CA (proxy_ca_cert_path, proxy_trust_custom_ca).
  • Change or check routing on a live context with browser_set_proxy, browser_get_proxy_status, browser_connect_proxy and browser_disconnect_proxy.
per-context proxy
curl -X POST http://localhost:8080/execute/browser_create_context \
  -H "Authorization: Bearer $OWL_HTTP_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "proxy_type": "socks5h",
    "proxy_host": "proxy.example.com",
    "proxy_port": 1080,
    "proxy_username": "user",
    "proxy_password": "secret"
  }'

Tor, one circuit per context

The Docker image runs a Tor client (SOCKS on port 9050). Mark a context as Tor and it gets its own circuit and exit node.

Circuit isolation

With is_tor set (or a proxy on localhost:9050), Owl asks Tor for a new circuit per context through the control port, so parallel contexts do not share an exit.

Nothing to install

Tor ships in the container. Outside Docker, point the context at your own Tor client and its control port (tor_control_port).

Trade-offs

Tor is slower than direct or proxied traffic and many sites treat Tor exits with suspicion. We have not published latency figures.

Closing

Close the context when you are done; its circuit is no longer used.

Tor context
curl -X POST http://localhost:8080/execute/browser_create_context \
  -H "Authorization: Bearer $OWL_HTTP_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "proxy_type": "socks5h",
    "proxy_host": "127.0.0.1",
    "proxy_port": 9050,
    "is_tor": true
  }'

Owl Sidecar: a private exit on a device you own

Install Owl Sidecar on a home machine or a server you control, pair it to your Owl account with a code from the customer portal, then route contexts through it.

Peer to peer

The browser and the sidecar connect directly over mutually authenticated QUIC. An Olib AI coordination service helps them find each other; it never carries your traffic.

No open ports

The sidecar only makes outbound connections, so it works behind home NAT without port forwarding. There is no relay: if both sides are behind symmetric NAT, the connection fails with a clear error rather than routing through Olib AI.

Your TLS, untouched

The sidecar forwards raw bytes for each connection (SOCKS5 CONNECT, DNS resolved remotely). It does not terminate or inspect TLS, so the browser's own handshake reaches the site.

Paired to your account

The device generates its key during pairing and keeps it locally. A device is usable only by browsers on the same account, can be removed from the portal, and refuses to connect to private-network addresses.

Route a context through your device

Use proxy_type: "owl_tunnel" with the device's proxy_id instead of a host and port.

Downloads

PlatformArchitecturePackage
macOSApple Silicon (arm64).tar.gz
Windowsx64Installer (.exe) or .zip
Linuxx86_64 and arm64, headless.deb (with a systemd user service) or .tar.gz

Packages as of Owl Sidecar 0.2.1.

sidecar context
curl -X POST http://localhost:8080/execute/browser_create_context \
  -H "Authorization: Bearer $OWL_HTTP_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "proxy_type": "owl_tunnel",
    "proxy_id": "<32-hex id of your paired device>"
  }'