# Tailscale home exit vs Aluvia vs take over the computer

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
```

First 10 MB free without an account, API key or payment, then 2 USD per GB. Run on the browser's machine with Node.js 18 or later and usable local Chrome or Chromium. Initial setup can restart Chrome. Read JSON and follow `next` for recovery before selecting a country. Reload the page and verify its content; `ready: true` is not target access. [Complete quickstart](/docs).

## 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

Manual takeover can help with a one-off challenge or diagnosis. It requires the operator to participate, so it does not meet a requirement for fully unattended work.

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

A home exit routes traffic through the exit device's public IP. It can help when that location and network fit the task. You need to maintain the exit device and configure browser-host access.

A Tailscale home exit needs an available exit node, device authentication and configuration on the browser host. Those steps can be automated, including when a VM is replaced. Aluvia needs setup on the new browser host and data on its network; it does not require a home exit node. Both approaches can need recovery. [Tailscale automated provisioning](https://tailscale.com/docs/install/with-cloud-init).

## 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 IP in a country you pick. Sticky sessions last up to 30 minutes on that residential exit. After an instance replace, re-run setup on the new machine; there is no home exit to reconstruct. 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 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 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: maintain an exit node and provision authenticated browser hosts. Replacement can be automated; use it when the exit location and network fit the task.
- Plan how the browser host will be configured after replacement. With Aluvia, run setup again and inspect its recovery output. Successful setup does not prove target access; paid continuation needs the operator.

## Next step

If the site is reacting to the datacenter IP or the wrong country, start with `npx aluvia-cli setup`. What that command writes, and how to undo it, is [what setup does](/setup). Picking a country is [change a cloud agent's IP location](/geo).

---

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