Commercial anti-detect browsers, listed for completeness and for comparison. Every one of them is closed source, which means the only fields this register can check are the ones an HTTP request returns — no push date, no release tag, no licence identifier, no archive flag. That thinness is itself the most useful thing this section prints.
Listed for completeness and for comparison. Closed source, so the only fields that can be checked are the ones a HTTP request returns.
The long-running commercial incumbent; the product most open-source entries are positioned against.
https://multilogin.com/ — printed, not linked
Evidence
Why ACTIVE: No repository. The link check returned 200 at 2026-08-14T09:12:00Z, and 200–399 is ACTIVE for a non-repository entry.
Field
Value at this printing
http_status
200
fetched_at
2026-08-14T09:12:00Z
rubric_edition
2nd, in force
Endpoint: HEAD https://multilogin.com/
No repository, so there is no API field to re-read from a browser. A cross-origin liveness check has to be made server-side; this entry's status comes from the register's own sweep.
Commercial anti-detect browser with public API documentation.
https://gologin.com/ — printed, not linked
Evidence
Why ACTIVE: No repository. The link check returned 200 at 2026-08-14T09:12:00Z, and 200–399 is ACTIVE for a non-repository entry.
Field
Value at this printing
http_status
200
fetched_at
2026-08-14T09:12:00Z
rubric_edition
2nd, in force
Endpoint: HEAD https://gologin.com/
No repository, so there is no API field to re-read from a browser. A cross-origin liveness check has to be made server-side; this entry's status comes from the register's own sweep.
Commercial anti-detect browser aimed at affiliate and multi-account teams.
https://dolphin-anty.com/ — printed, not linked
Evidence
Why ACTIVE: No repository. The link check returned 200 at 2026-08-14T09:12:00Z, and 200–399 is ACTIVE for a non-repository entry.
Field
Value at this printing
http_status
200
fetched_at
2026-08-14T09:12:00Z
rubric_edition
2nd, in force
Endpoint: HEAD https://dolphin-anty.com/
No repository, so there is no API field to re-read from a browser. A cross-origin liveness check has to be made server-side; this entry's status comes from the register's own sweep.
Commercial anti-detect browser with local API and team seats.
https://www.adspower.com/ — printed, not linked
Evidence
Why ACTIVE: No repository. The link check returned 200 at 2026-08-14T09:12:00Z, and 200–399 is ACTIVE for a non-repository entry.
Field
Value at this printing
http_status
200
fetched_at
2026-08-14T09:12:00Z
rubric_edition
2nd, in force
Endpoint: HEAD https://www.adspower.com/
No repository, so there is no API field to re-read from a browser. A cross-origin liveness check has to be made server-side; this entry's status comes from the register's own sweep.
Commercial anti-detect browser with a documented automation API.
https://incogniton.com/ — printed, not linked
Evidence
Why ACTIVE: No repository. The link check returned 200 at 2026-08-14T09:12:00Z, and 200–399 is ACTIVE for a non-repository entry.
Field
Value at this printing
http_status
200
fetched_at
2026-08-14T09:12:00Z
rubric_edition
2nd, in force
Endpoint: HEAD https://incogniton.com/
No repository, so there is no API field to re-read from a browser. A cross-origin liveness check has to be made server-side; this entry's status comes from the register's own sweep.
Commercial anti-detect browser; documentation lives on help.kameleo.io, not /docs.
https://kameleo.io/ — printed, not linked
Evidence
Why ACTIVE: No repository. The link check returned 200 at 2026-08-14T09:12:00Z, and 200–399 is ACTIVE for a non-repository entry.
Field
Value at this printing
http_status
200
fetched_at
2026-08-14T09:12:00Z
rubric_edition
2nd, in force
Endpoint: HEAD https://kameleo.io/
No repository, so there is no API field to re-read from a browser. A cross-origin liveness check has to be made server-side; this entry's status comes from the register's own sweep.
Why ACTIVE: No repository. The link check returned 200 at 2026-08-14T09:12:00Z, and 200–399 is ACTIVE for a non-repository entry.
Field
Value at this printing
http_status
200
fetched_at
2026-08-14T09:12:00Z
rubric_edition
2nd, in force
Endpoint: HEAD https://octobrowser.net/
No repository, so there is no API field to re-read from a browser. A cross-origin liveness check has to be made server-side; this entry's status comes from the register's own sweep.
Commercial anti-detect browser. Note the name collision with the open-source entry in section 01.
https://undetectable.io/ — printed, not linked
Evidence
Why ACTIVE: No repository. The link check returned 200 at 2026-08-14T09:12:00Z, and 200–399 is ACTIVE for a non-repository entry.
Field
Value at this printing
http_status
200
fetched_at
2026-08-14T09:12:00Z
rubric_edition
2nd, in force
Endpoint: HEAD https://undetectable.io/
No repository, so there is no API field to re-read from a browser. A cross-origin liveness check has to be made server-side; this entry's status comes from the register's own sweep.
Multi-session browser aimed at agencies rather than at detection evasion.
https://ghostbrowser.com/ — printed, not linked
Evidence
Why ACTIVE: No repository. The link check returned 200 at 2026-08-14T09:12:00Z, and 200–399 is ACTIVE for a non-repository entry.
Field
Value at this printing
http_status
200
fetched_at
2026-08-14T09:12:00Z
rubric_edition
2nd, in force
Endpoint: HEAD https://ghostbrowser.com/
No repository, so there is no API field to re-read from a browser. A cross-origin liveness check has to be made server-side; this entry's status comes from the register's own sweep.
Why ACTIVE: No repository. The link check returned 200 at 2026-08-14T09:12:00Z, and 200–399 is ACTIVE for a non-repository entry.
Field
Value at this printing
http_status
200
fetched_at
2026-08-14T09:12:00Z
rubric_edition
2nd, in force
Endpoint: HEAD https://ixbrowser.com/en
No repository, so there is no API field to re-read from a browser. A cross-origin liveness check has to be made server-side; this entry's status comes from the register's own sweep.
Commercial anti-detect browser bundled with a cloud scraping service.
https://www.nstbrowser.io/en — printed, not linked
Evidence
Why ACTIVE: No repository. The link check returned 200 at 2026-08-14T09:12:00Z, and 200–399 is ACTIVE for a non-repository entry.
Field
Value at this printing
http_status
200
fetched_at
2026-08-14T09:12:00Z
rubric_edition
2nd, in force
Endpoint: HEAD https://www.nstbrowser.io/en
No repository, so there is no API field to re-read from a browser. A cross-origin liveness check has to be made server-side; this entry's status comes from the register's own sweep.
Commercial anti-detect browser aimed at e-commerce multi-accounting.
https://hidemyacc.com/ — printed, not linked
Evidence
Why ACTIVE: No repository. The link check returned 200 at 2026-08-14T09:12:00Z, and 200–399 is ACTIVE for a non-repository entry.
Field
Value at this printing
http_status
200
fetched_at
2026-08-14T09:12:00Z
rubric_edition
2nd, in force
Endpoint: HEAD https://hidemyacc.com/
No repository, so there is no API field to re-read from a browser. A cross-origin liveness check has to be made server-side; this entry's status comes from the register's own sweep.
What a closed product removes from a catalogue like this one
The whole method of this register is to derive a status from dated fields and publish the fields. A closed product has none of them. There is no commit history to age, no tag to pin, no licence metadata to read, and no archive flag anyone could set. What remains is whether the address answers, which is a real measurement and a very thin one.
Setting that beside the open entries in section 01 is the point of listing these at all. The comparison is not about quality — this register makes no quality claim about anything — it is about what can be established at all. For an open project you can check the claim. For a closed one you can check that the website is up.
What these products are actually sold on
Reading the public surface of this section, the differentiators that recur are rarely about fingerprinting at all: team seats and shared profiles, cloud storage of profile data, bundled proxy or scraping capacity, a documented automation API, a free tier. Those are real product differences and they carry consequences a detection discussion usually skips — chiefly that team features imply a cloud component holding your profiles, and bundled network capacity implies traffic leaving from infrastructure that is not yours.
Establish where profile data lives and where traffic exits before evaluating anything else about a product in this section. Those two answers change the threat model more than any fingerprinting feature list.
State marks used in this section
ACTIVE — Shipping. Safe to build on today.
12 here
Questions about commercial anti-detect browsers
Answered from the fields printed above, and from nothing this register has not checked.
Which commercial anti-detect browser is best?
This register does not answer that and could not honestly try: these products are closed, no field beyond an HTTP status can be checked, and this catalogue publishes no ranking, no score and no detection-test results of any kind.
Why does this registry not link to commercial anti-detect vendors?
Because it is kept by people who work on a browser those vendors compete with, and a link to a competitor's landing page is a referral rather than a citation. Every one of them is still named, described and catalogued on the same rule as everything else; only the outbound link is withheld. The policy is set out in full on the colophon.
Are open-source anti-detect browsers as good as paid ones?
Not a question this register answers. What it can tell you is what is checkable: an open project publishes a licence, a commit history and a release record that this catalogue reads and prints with timestamps, and a closed one publishes a website.
Donut Browser is filed in section 01 of this same catalogue, under the
same rubric, with the same fields printed against it and no exemption:
an open-source anti-detect browser under AGPL-3.0 whose Wayfern Chromium
fork applies fingerprint overrides at engine level over CDP rather than
by patching page JavaScript, with a local REST API and MCP server on your
own machine, self-hostable sync, zero telemetry, and a pre-launch gate
that refuses to start a profile when the proxy's exit geography
contradicts the profile's fingerprint. It is judged here the same way
everything in this section is judged.