Browser runtime
Install the CloakBrowser runtime.
AliasMode manages profiles and launches them in CloakBrowser. The engine is a third-party component included at no extra cost; it keeps its own license, separate from the Apache-2.0 AliasMode desktop app.
Install from AliasMode
Open AliasMode and follow the browser installation prompt. Let the app complete the runtime download and installation before creating the first browser session. The runtime is included at no extra cost, and no separate CloakBrowser purchase, subscription, or account is required.
Why the runtime matters
Websites and protection vendors check whether a browser behaves like a normal human-driven Chrome install. Out-of-the-box automation tools such as Playwright or headless Chrome fail many of these checks. CloakBrowser is patched at the browser source level, so the signals detection scripts read, from the user agent down to the TLS fingerprint, match a genuine Chrome browser. See the full test results below.
License boundary
AliasMode is Apache-2.0 open source, including the complete desktop app. The CloakBrowser engine is a third-party component: included at no extra cost, but under its own license rather than Apache-2.0. AliasMode Cloud is an optional managed service with its own source and service boundary.
Verify the runtime
Create a test profile and open it. A successful setup starts CloakBrowser with the profile’s persistent data directory and selected settings. If installation or launch fails, check the troubleshooting page.
Bot detection test results
Detection test results
Tested against live bot-detection services.
Every AliasMode profile opens in CloakBrowser, a Chrome-based runtime patched at the source, so websites see a normal human-driven browser, not an automation tool. Here is how it compares on the public detection services that platforms use to screen visitors.
| Detection service | Standard automated browser | CloakBrowser | Notes |
|---|---|---|---|
| reCAPTCHA v3 | 0.1 (bot) | 0.9 (human) | Server-side verified |
| Cloudflare Turnstile (non-interactive) | FAIL | PASS | Auto-resolve |
| Cloudflare Turnstile (managed) | FAIL | PASS | Single click |
| ShieldSquare | BLOCKED | PASS | Production site |
| FingerprintJS bot detection | DETECTED | PASS | demo.fingerprint.com |
| BrowserScan bot detection | DETECTED | NORMAL (4/4) | browserscan.net |
| bot.incolumitas.com | 13 fails | PASS | Bot checks passed |
| deviceandbrowserinfo.com | 6 true flags | 0 true flags | isBot: false |
navigator.webdriver | true | false | Source-level patch |
navigator.plugins.length | 0 | 5 | Real plugin list |
window.chrome | undefined | object | Present like real Chrome |
UA string | HeadlessChrome | Chrome/150.0.0.0 | No headless leak |
CDP detection | Detected | Not detected | isAutomatedWithCDP: false |
TLS fingerprint | Mismatch | Identical to Chrome | ja3n/ja4/akamai match |
A standard automated browser is out-of-the-box Playwright or headless Chrome/Chromium, the default setup most automation scripts and bots use.
Point-in-time results from independent public test services; you can reproduce them yourself against a CloakBrowser profile. Detection vendors update their checks continuously, and no browser can guarantee a pass on every service forever.