From 72c1e3fcbdd725d51621d1a586c5888e23d78e19 Mon Sep 17 00:00:00 2001 From: ulziibay-kernel <253135130+ulziibay-kernel@users.noreply.github.com> Date: Mon, 27 Apr 2026 16:14:38 +0000 Subject: [PATCH 1/2] docs(auth): mention GPU acceleration in Managed Auth feature list Surface the bot-detection benefit of GPU-enabled browsers for login flows on sites that fingerprint rendering output (canvas/WebGL). --- auth/overview.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/auth/overview.mdx b/auth/overview.mdx index 9a2ba56..9a89fec 100644 --- a/auth/overview.mdx +++ b/auth/overview.mdx @@ -124,6 +124,7 @@ The most valuable workflows live behind logins. Managed Auth provides: - **2FA/OTP handling** - TOTP codes automated with automatic retry on expiry, SMS/email/push OTP are supported - **Post-login URL** - Get the URL where login landed (`post_login_url`) so you can start automations from the right page - **Session monitoring** - Automatic re-authentication when sessions expire with stored credentials +- **[GPU acceleration](/browsers/gpu-acceleration)** - Login flows on sites with rendering-based fingerprinting (canvas, WebGL) clear consistently when paired with GPU-enabled browsers, which produce hardware-rendered output indistinguishable from a real consumer GPU - **Secure by default** - Credentials encrypted at rest, never exposed in API responses, or passed to LLMs ## Security From 9882f89369ece2f5a9f60add33ee8b729253b4d9 Mon Sep 17 00:00:00 2001 From: ulziibay-kernel <253135130+ulziibay-kernel@users.noreply.github.com> Date: Mon, 27 Apr 2026 23:36:43 +0000 Subject: [PATCH 2/2] docs(bot-detection): move GPU acceleration to bot-detection overview MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Drop the GPU bullet from the Managed Auth feature list — it belongs under Kernel Features That Help on the bot-detection overview, where the other anti-detection levers (stealth, proxies, profiles, computer controls) are listed. --- auth/overview.mdx | 1 - browsers/bot-detection/overview.mdx | 3 +++ 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/auth/overview.mdx b/auth/overview.mdx index 9a89fec..9a2ba56 100644 --- a/auth/overview.mdx +++ b/auth/overview.mdx @@ -124,7 +124,6 @@ The most valuable workflows live behind logins. Managed Auth provides: - **2FA/OTP handling** - TOTP codes automated with automatic retry on expiry, SMS/email/push OTP are supported - **Post-login URL** - Get the URL where login landed (`post_login_url`) so you can start automations from the right page - **Session monitoring** - Automatic re-authentication when sessions expire with stored credentials -- **[GPU acceleration](/browsers/gpu-acceleration)** - Login flows on sites with rendering-based fingerprinting (canvas, WebGL) clear consistently when paired with GPU-enabled browsers, which produce hardware-rendered output indistinguishable from a real consumer GPU - **Secure by default** - Credentials encrypted at rest, never exposed in API responses, or passed to LLMs ## Security diff --git a/browsers/bot-detection/overview.mdx b/browsers/bot-detection/overview.mdx index 3859755..90e4f09 100644 --- a/browsers/bot-detection/overview.mdx +++ b/browsers/bot-detection/overview.mdx @@ -47,6 +47,9 @@ Kernel automatically applies Patchright to remove automation fingerprints, inclu Controls the browser without using the Chrome DevTools Protocol (CDP), which can reduce bot detection signals. Emulates native keyboard and mouse input directly at the OS level and includes human-like [bezier curves](/browsers/computer-controls#move-the-mouse) by default. +### [GPU Acceleration](/browsers/gpu-acceleration) +Many detection systems fingerprint canvas and WebGL rendering output and cross-check it against the claimed GPU. Software-rendered browsers produce pixel hashes that don't match any real consumer GPU, which is a strong bot signal on sites with rendering-based fingerprinting. GPU-enabled Kernel browsers render through real hardware, producing output consistent with a normal user's device. + ## Getting Started Before you start automating your workflow, we recommend that you manually test your website to understand how it behaves with Kernel's browsers. Here's how to do that: