Owl Sidecar icon

Your device,
your private exit

Owl Sidecar turns a machine you own into a residential exit for Owl Browser. Your traffic runs straight between the browser and the device. It never passes through Olib servers.

macOS, notarized·Windows·Linux x64 and arm64

How it works

Three parts, and your data only touches two of them.

1

Pair a device

Install the app, enter a code from the Owl portal, and the device registers to your account. The key is made on the device and never leaves it.

2

Browser connects to it

A small coordination service helps the browser and the device find each other, then steps out. The two sides connect directly, even from behind NAT with no open ports.

3

Traffic goes out clean

The device opens an ordinary outbound connection to each site and forwards raw bytes. The browser keeps its own TLS, so nothing on the wire marks the traffic as proxied.

Built to stay out of the way

Pair once, then it runs quietly and you stay in control.

Peer to peer

Your traffic runs directly between the browser and the device. Olib never carries or sees it.

No open ports

The device connects outbound only, so it works from a home network with nothing forwarded.

Undetectable as a proxy

Raw byte forwarding and a residential address, with the browser's own end to end TLS. No added header, no rewrite.

Yours only

A device is usable only by browsers on the same account. Sessions cannot cross accounts.

Menu bar and tray

See online state, active connections, and transfer. Close the window and it keeps running in the background.

Pause and resume

Stop serving at any time without unpairing. Turn on start at login to keep it running across reboots.

Private by design

The architecture is the guarantee, not a policy.

Olib is not in the path

The coordination service only helps the two sides connect at the start of a session. It cannot carry your traffic, because there is no relay to fall back on.

Mutually authenticated tunnel

The browser and the device authenticate each other with keys tied to your account. A compromised coordinator cannot insert a fake exit.

Keys stay on the device

The device generates its key on first run and keeps it local. Pairing registers only the public half.

Signed builds

The macOS app is signed with our Apple Developer ID and notarized by Apple. Report anything suspicious to security@olib.ai.

Install

Pick your platform, then follow the pairing guide.

macOS

Download the tarball, move OwlSidecar.app to Applications, and open it. Notarized, so no Gatekeeper override.

Windows

Download the zip and run owl-sidecar.exe. Keep it in the tray and enable start at login.

Linux

Install the .deb on Debian and Ubuntu, or use the tarball and install script on other distributions.

curl -fsSL https://raw.githubusercontent.com/Olib-AI/owl-sidecar/main/scripts/install.sh | sh

Go to downloads   Pairing guide