# Tailscale home exit vs Aluvia vs take over the computer

Three ways to keep a cloud agent browsing when the site sees a datacenter IP: take over the computer, a Tailscale home exit, or Aluvia on the VM.

This is a field note for operators running Grok Bot or another cloud agent whose browser sits on a datacenter IP. You still need the agent to finish the job without you sitting in the seat.

## The command

```sh
npx aluvia-cli setup
aluvia geos
aluvia proxy-on --geo US
```

Replace `US` with the country the page needs. Omit `--geo` for the global pool. Sticky sessions last up to 30 minutes. First 10 MB is free, with no account and no API key. Then $2/GB.

## The problem in one scene

The agent's computer lives in a cloud datacenter. Many sites treat that address as high risk or as the wrong country. You see Cloudflare's "Verify you are human," a CAPTCHA that returns after every solve, Imperva's "This request was blocked by our security service" / Error 16, or a shop that will not ship to that region.

## Take over the computer

xAI's docs and forum advice often land here: clear the challenge yourself, or use your own browser. That works for a one-off. It fails for unattended work. The moment you have to click Verify human, the agent is no longer running alone.

Use takeover when you are debugging. Do not build your workflow on it.

## Tailscale (or similar) with a home exit node

The pattern is to install Tailscale on the Grok Bot machine, put an always-on home Mac or mini on as an exit node, and send Chrome through the house's residential IP. That can clear datacenter-triggered challenges because the site now sees a home address. Operators report it helps for logins and CAPTCHAs that were keyed on the cloud range.

The failure mode is the instance. When the cloud computer is replaced or reset, the Tailscale path is gone until someone puts it back. Your always-on home box is now a dependency for every agent run. You are operating a VPN mesh so an agent can browse.

Use a home exit when you already run that mesh for yourself and you accept the wipe risk. It is not a productized agent egress path.

## Aluvia on the agent machine

Aluvia is a local CLI the agent installs on the same VM. It sends the existing Chrome through a residential or mobile IP in a country you pick. Bring-your-own proxy URL is free for bandwidth on Aluvia's side. The agent runs the commands. You do not SSH in to set env vars for the happy path.

## When Aluvia helps

- Wrong country: the site shows the datacenter's catalog, prices, language, or "not available in your region."
- Datacenter-triggered blocks: a residential or mobile IP sometimes clears a 403, CAPTCHA, Cloudflare challenge, Imperva Error 16, or similar. Sometimes. Not a promise.
- An IP-triggered login page from a datacenter address: changing to a residential or mobile IP is the job. A password, SSO, or 2FA problem with no IP story is not.

## When Aluvia is the wrong tool

- Fingerprint, Linux Chrome, TLS, or canvas is the stated cause and the IP already looks residential.
- Streaming or live video.
- A normal login wall that already rendered and needs credentials, not a new exit IP.
- City-level targeting, GPS, timezone, or Accept-Language spoofing. Country only.

## Pick one

- Take over the computer: not unattended. It does not select a country.
- Tailscale home exit: mostly unattended. It does not survive instance replace. Country select only works if the home is already in that country.
- Aluvia: unattended. It survives instance replace if you re-run setup on the new machine. Country select is `--geo`.

## Next step

If the site is reacting to the datacenter IP or the wrong country, start with `npx aluvia-cli setup`, then open [https://aluvia.io](https://aluvia.io) for docs, geo pages, and the error-string guides under `/unblock`.

---

Source: https://aluvia.io/resources/tailscale-vs-aluvia