Proxy your shell.

Every terminal can be somewhere else.
US in one tab. Germany in another. Japan in CI.

Session=active, Proxy=US residential shellroute
/connect /rotate /status /countries /cities US /iptype /disconnect /exit
Install shellroute View on GitHub

Start with $1 credit. No card required.

Open-source CLI · Pay per use · Residential + datacenter proxies

One-off task or full terminal session.

Use shellroute run for a single job. Use interactive mode to stay connected while you work.

shellroute run direct mode
~ $ shellroute run DE -- python3 check_geo.py Region: eu-central-1 (Frankfurt) ✓ shellroute session ended. Duration: 4s Data used: 48 KB Cost: $0.0001 Balance: $9.96

For scripts, CI, tests, and agents.

shellroute interactive mode
~ $ shellroute ● shellroute · not connected · direct traffic ~ ❯ /connect US Connecting to US (residential)... ✓ Connected to US — New IP: 45.12.67.89 ● shellroute us · 45.12.67.89 ~ ❯ cd dev/api-check ● shellroute us · 45.12.67.89 ~/dev/api-check ❯ python3 verify_api.py US endpoint OK — latency 42ms

Connect once, then run commands normally.

Every shell can have its own country, proxy type, and IP.

Stop configuring proxies. Just use them.

You should not have to configure every tool just to use a proxy.

Wire proxy credentials manually

  • Copy endpoint and auth
  • Set env vars
  • Configure each tool
  • Clean up afterwards

Route the whole machine

  • Changes all traffic
  • Affects browser and apps
  • Hard to isolate
  • Heavy for quick tests

A different country is one command away.

Start shellroute. Pick a country. Keep working in the terminal.

1

Start shellroute

shellroute

Opens a proxied shell with your aliases, PATH, and functions.

2

Connect to a country

/connect US

Pick a country. Traffic in this shell now uses the proxy.

3

Run commands normally

curl https://httpbin.org/ip
python3 check_api.py
npm run test

Run curl, Python scripts, test suites, and the rest of your terminal workflow.

A normal shell, through a proxy

Connect once, then run the commands you already use

shellroute interactive mode

120+ countries · Residential + datacenter · Usage metered per session

Shellroute vs the usual setup

No per-tool proxy configuration. No whole-machine VPN.

Manual proxy VPN shellroute
Scope Per tool Entire device One shell or command
Setup Env vars, ports, auth App install, server select /connect US
Affects browser Depends Yes No
Parallel countries Manual per tool One at a time Multiple shells
Automation Per-tool wiring Manual toggle Script/CI/agent native
Billing Varies Monthly subscription Pay per GB

Set the proxy once. Run commands normally.

Residential
From $3/GB. Home IPs in 120+ countries.
Datacenter
From $1/GB. Faster, cheaper for testing.
/rotate
Switch exit IP inside an active session.
--sticky
Keep one proxy identity across commands.
--city
Target supported city-level locations.
--no-stat
Clean output for piping and scripts.

Start proxying your shell.

Open a session, connect a proxy, and run commands normally

Install shellroute View on GitHub

Pay per use · Open-source CLI · No contracts