Get started
Stealth practices
Some sites protect themselves from being automated (X, LinkedIn, Amazon, etc.) using key signals: IP, browser fingerprints, cookies and behavior.
Reduck is designed to minimize detection risks in both modes: your own browser through the extension, and cloud browsers.
This page presents what we have built to minimize your agent being detected as a bot, then what you should do on your side.
What Reduck does
On your own browser
Scripts run in the browser you use every day, through the Reduck extension. Sites see the same browser they always see from you:
| Signal | An agent’s own browser | Your browser through Reduck |
|---|---|---|
| IP | Datacenter | Your home or office connection |
| Browser | Automated, often headless | Your real browser and its fingerprint |
| Cookies | None | Your sessions |
So detection risk is minimal.
A script runs in your browser profile, with its sessions and cookies, so your agent works where you are already signed in:
- No login to script and no password to hand over. Your usual 2FA still works.
- No profile copy, no debug port, no “allow remote debugging” switch.
- Your cookies never leave your machine.
The extension connects out to Reduck, so this holds wherever your agent runs, in a terminal, in Docker or on a server: your browser only needs to be open.
On a cloud browser
A cloud browser runs in Reduck’s cloud, 24/7, without your browser.
- Network: we have a region by default, and a residential proxy as an option.
- Browser: we serve stealthy browsers.
What you should do
Reduck lowers the risk; it does not remove it. A site judges what is done with your account on that site, not only the browser it is done from.
- Pace your runs on one site. Too many requests in a short time look like a bot from any browser, and a site answers them with a 429, a captcha or a restriction on your account on that site. Each device runs 4 scripts at a time by default: lower it for a strict site at reduck.ai/devices. See Parallel runs.
- Use a site account that you can afford to have restricted. A script acts as you, with your account on that site, under the site’s rules. On a site that limits automation, start with small volumes.
- On a cloud browser, pick a residential proxy in the site’s country for a site that blocks datacenter IPs.
- Use cloud browsers for public pages that you only read. If a cloud browser can get the content of the page without signing in, use it for pages that block bots, such as a Reddit post.