Scripts in a real profile
A Veilus Flow script runs inside a profile's browser, so each request goes out with that profile's fingerprint, proxy and cookies, and logins stay in the profile between runs.
Collect public data with Playwright scripts that run inside your browser profiles, each with its own proxy, cookies and logins.
Download Veilus freeA Veilus Flow script runs inside a profile's browser, so each request goes out with that profile's fingerprint, proxy and cookies, and logins stay in the profile between runs.
Put URLs in a consume dataset: each run takes new rows, profiles running at the same time never get the same row, and a run that fails returns its rows, so no URL is lost.
Keep Concurrency low with a Delay Between launches in a run or a Stagger Delay on a schedule, wait between pages inside the script, and schedule collection at fixed times. Results land in Run History, and an AI assistant reads them over MCP.
Install Veilus on Windows 10/11 (x64) or macOS 13.5+ (Apple Silicon), create the profiles and give each one its proxy.
Ask an AI assistant over MCP to write it, or write it yourself. Print what you collect as JSON, and throw when nothing is found so the run shows as failed.
Put the URLs in a consume dataset, approve the script in Veilus Flow, then run it or put it on a schedule. This needs a paid plan or the 7-day Pro trial.
Ready-to-run script: price monitor (GitHub)
Build your own check with Claude over MCP (GitHub)
No. Describe what to collect to an AI assistant connected over MCP, such as Claude Code or Cursor. It writes the Playwright script and trial-runs it on up to 3 profiles; you read it and approve it before it runs on more.
Veilus keeps the last 4096 characters of each profile's output. If you collect more, have the script write it to a file with Node's fs module and print a short summary.
No. Dataset values reach approved scripts only; a trial run of an unapproved script gets none and reserves no rows. Pass the values it needs as run variables instead.
Yes. Cookies and logins stay in the profile, so reuse the same profile for the same site and its session carries over from run to run.
No tool can promise that, and we don't. A profile keeps a consistent fingerprint, proxy and cookies; how a site treats the traffic also depends on how fast and how much you collect.
It depends on the site and where you are. Check each site's terms and robots.txt before you collect from it; some sites prohibit automated collection. Collect public data, keep the pace low, and read our Acceptable Use Policy.
Veilus for e-commerceVeilus for dropshippingVeilus for affiliate marketingVeilus for advertising