EchidnaEvery profile, a real device.
Echidna runs each profile as one coherent computer: its own fingerprint, network, storage and history, on a hardened Chromium that updates itself and verifies every byte it runs.
Separate identities that hold together under inspection.
Fingerprints are not a list of random values. Every number a site can read has to agree with every other one: the hardware with the graphics card, the clock with the network, the fonts with the operating system. Echidna derives all of them from one believable device.
Device
Screen, CPU cores, memory, graphics card, WebGL and WebGPU limits, audio stack, fonts and voices, chosen together from one seed.
Network
One proxy per profile, with timezone, language, geolocation and WebRTC following its exit, and no UDP slipping around it.
Storage
Cookies, local storage, extensions and history stay inside the profile. Import, export and keep sessions across restarts.
Behaviour
Input that moves and types like a person, even when an agent or a script is driving, so automation inherits the stealth instead of breaking it.
One seed. Hundreds of answers that agree.
Each profile carries a persona: a complete, plausible machine. Every surface reads from it, in every process, on every page, for as long as the profile lives.
- Consistent across processes. Workers, iframes and the main page all see the same device.
- Consistent across headers and script. Client hints, user agent and network quality match what JavaScript reports.
- Consistent over time. The same profile is the same device tomorrow, with its own stable canvas and audio signature.
- Real where it matters. Pages render and run on a current Chromium, not a lookalike.
Built for people, scripts and AI agents.
Drive profiles from the desktop app, from code, or let an AI agent work through the built-in MCP server. Every click and keystroke goes through the same human-like input layer.
- Local engine API. Turn on automation in Settings and start, stop and script your profiles over a loopback HTTP API with one stable automation token you can replace at any time. It can't touch your license, saved logins or backups.
- MCP for agents. Connect Claude, Codex or Cursor with the same token: a large tool set for navigation, forms, files, cookies and screenshots.
- Playwright and Puppeteer. Attach over the DevTools protocol to a profile you launched.
- Flows and schedules. Record repeatable flows and run them on a timetable from the app.
import requests # the local engine listens on 127.0.0.1 only; token from Settings > Automation & API api = f"http://127.0.0.1:{port}" auth = {"Authorization": f"Bearer {automation_token}"} requests.post(f"{api}/profiles/amsterdam-studio/start", headers=auth) cdp = requests.get(f"{api}/profiles/amsterdam-studio/cdp", headers=auth).json()["cdp_url"] # attach your own tooling over CDP from playwright.sync_api import sync_playwright with sync_playwright() as p: browser = p.chromium.connect_over_cdp(cdp) page = browser.contexts[0].pages[0] page.goto("https://example.com")
Nothing runs that we did not sign.
Your profiles hold sessions that matter. Echidna treats the browser on your machine like production software, because it is.
Verified on every launch
Every file of the browser engine is listed in a signed inventory and checked before it starts. A modified file means the engine does not run.
Signed, silent updates
App and engine updates come from one signed release feed. The engine updates in the background; the app updates with one click and restarts.
Sandbox stays on
Chromium's sandbox is never switched off, and launch options that would weaken it are refused before the browser starts.
Local first
Profiles, cookies and history live on your computer. The engine listens on loopback only. Scripts use an automation token that you turn on, can replace at any time, and that can't reach your license, saved logins or backups.
No telemetry
No analytics, no crash uploads, no Google services. The browser is built from ungoogled-chromium.
Licence you control
Seats are bound to devices you approve. Move or release a device yourself from the dashboard.
From request to first profile in minutes.
Request access
Tell us about your team and use case. Every account is reviewed by a person.
Install and sign in
Download the app for Windows, macOS or Linux and activate it with your license key.
Create profiles
Add a proxy, pick a device or let Echidna choose one, and launch. Each profile is ready in seconds.
Frequently asked
Who is Echidna for?
Teams that operate many accounts or environments legitimately: agencies managing client accounts, QA and research teams testing how sites behave for different users and regions, and support teams working in customer contexts. Use is governed by our Acceptable Use Policy.
Why is access by request?
Every account is reviewed by a person and bound to an Acceptable Use Policy. That keeps the platform out of the hands of fraud, which protects every legitimate customer's reputation with the sites they use.
Do you see my profiles or browsing?
No. Profiles, cookies and history stay on your computer. The licence server only knows your account, your devices and which version you run.
Which Chromium version does it run?
Chromium 157 today, on all three operating systems. New Chromium versions ship as signed engine updates that install in the background. The release notes list every change.
Can I use my own proxies?
Yes. HTTP, HTTPS and SOCKS5 proxies, with or without authentication, one per profile or rotated from a pool. Timezone, language and location follow the proxy's exit automatically.
Can I automate it?
Yes. Turn on Settings → Automation & API, then use the local engine API, Playwright, Puppeteer or Selenium over CDP, or AI agents through the built-in MCP server. See the automation guide, or coming from another tool if you are moving existing scripts or profiles.
Bring your team to Echidna.
Tell us who you are and what you are building. We review every request personally and reply by email.