Aluvia

How a cloud agent installs Aluvia

This page as markdown: https://aluvia.io/docs.md

The agent runs one install command on the cloud machine. After that, it can change the IP location the site sees, or turn the proxy off and go back to the VM's own IP. The first 10 MB is free. Paid data is $2/GB; see /pricing.

The command

sh
npx aluvia-cli setup

Once per machine. Node.js 18 or later. When Chrome is not already aimed, pass --url with the address-bar HTTPS page. If aluvia is not on PATH, prefix later commands with npx aluvia-cli. Every command prints JSON with a next field. Read next and run it.

When to turn it on

Most sites infer country from the request IP. A cloud agent's IP is the datacenter's, so the site returns that country's page, or refuses it.

After setup, aluvia proxy-on --geo US sends the existing browser through a residential or mobile IP in that country. Replace US. aluvia geos lists countries. Omit --geo to use the global pool. Sticky sessions last up to 30 minutes. aluvia proxy-off returns traffic to the VM without restarting Chrome.

A residential or mobile IP in the right country sometimes also clears a 403, CAPTCHA, Cloudflare, Access Denied, unusual-traffic, or rate-limit page. That is secondary. Aluvia does not claim to beat fingerprint, Linux Chrome, TLS, or canvas. Do not use it for a normal login wall.

Who this is for

Grok Bot, Codex, Cursor, Claude computer use, OpenClaw, Hermes, and any cloud Chrome the operator did not put in the right country. Playwright and Puppeteer are the same problem when the browser runs in that VM.

Other pages