kernel · masnwilliams · Feb 9, 2026 · Feb 9, 2026
diff --git a/info/pricing.mdx b/info/pricing.mdx
@@ -50,15 +50,25 @@ With Browser Pools, you pay the standard usage-based price per GB-second while b
 | On-demand browsers | 5 | 10 | 50 | Custom |
 | Invocations | 5 | 10 | 50 | Custom |
 | Invocations (per-app) | 5 | 10 | 20 | Custom |
-| Managed auth profiles | N/A | 3 | 20 | Custom |
+| Managed auth health check interval | N/A | 1 hour minimum | 15 minutes minimum | 5 minutes minimum |
 
-> Note: Limits are org-wide by default unless stated otherwise. `Managed auth profiles` refer to the number of active auth connections that Kernel maintains using your stored [Credentials](/profiles/credentials) or [1Password connection](/integrations/1password).
+> Note: Limits are org-wide by default unless stated otherwise. Managed auth connections are unlimited on all paid plans. Auth sessions are regular browser sessions and count toward your browser usage like any other browser.
 
 ## Managed Auth billing
 
 Managed Auth is included on all paid plans with no per-connection fees. Under the hood, it uses browser sessions to log in and keep your sessions fresh—these count toward your browser usage and concurrency like any other browser session.
 
-Auth sessions are fast (typically 5-30 seconds each). Kernel monitors session health and re-authenticates automatically when sessions expire—most stay valid for days. For example, keeping 100 auth connections logged in typically costs less than $5/month in browser usage.
+Auth sessions are fast (typically 5-30 seconds each). Kernel monitors session health and re-authenticates automatically when sessions expire—most stay valid for days.
+
+The default health check interval is 1 hour. Higher-tier plans can configure more frequent checks:
+
+| Plan | Minimum health check interval |
+|------|-------------------------------|
+| Hobbyist | 1 hour (default) |
+| Startup | 15 minutes |
+| Enterprise | 5 minutes |
+
+Lower intervals detect expired sessions faster but use more browser time. For most use cases, the default 1-hour interval is sufficient.
 
 ## Pricing calculator
 

diff --git a/profiles/managed-auth/faq.mdx b/profiles/managed-auth/faq.mdx
@@ -5,7 +5,15 @@ description: Frequently asked questions about Managed Auth
 
 ## How does re-authentication work?
 
-When you link credentials to a connection, Kernel monitors the session and re-authenticates automatically when it expires. Periodic health checks (default: every hour) detect logged-out sessions and trigger re-auth in the background, so the profile stays logged in without any action on your part.
+When you link credentials to a connection, Kernel monitors the session and re-authenticates automatically when it expires. Periodic health checks detect logged-out sessions and trigger re-auth in the background, so the profile stays logged in without any action on your part.
+
+The default health check interval is 1 hour. You can configure a lower interval when creating a connection—the minimum depends on your plan:
+
+| Plan | Minimum interval |
+|------|-----------------|
+| Hobbyist | 1 hour |
+| Startup | 15 minutes |
+| Enterprise | 5 minutes |
 
 <Warning>
 Automatic re-authentication only works when credentials are complete and don't require human input. If login needs SMS/email OTP, push notifications, or manual MFA selection, you'll need to trigger a new login session manually.
@@ -63,4 +71,4 @@ Managed Auth works with any website. Sites with aggressive bot detection may req
 
 Managed Auth is included on all paid plans with no per-connection fees. It uses browser sessions to log in and keep your sessions fresh—these count toward your browser usage like any other browser session.
 
-Auth sessions are fast (typically 5-30 seconds each). Kernel monitors session health and re-authenticates automatically when sessions expire—most stay valid for days. For example, keeping 100 auth connections logged in typically costs less than $5/month in browser usage. See [Pricing & Limits](/info/pricing#managed-auth-billing) for details.
+Auth sessions are fast (typically 5-30 seconds each). Kernel monitors session health and re-authenticates automatically when sessions expire—most stay valid for days. Lower health check intervals use more browser time, so keep that in mind when choosing an interval. See [Pricing & Limits](/info/pricing#managed-auth-billing) for details.
diff --git a/profiles/managed-auth/hosted-ui.mdx b/profiles/managed-auth/hosted-ui.mdx
@@ -97,7 +97,7 @@ if state.status == "AUTHENTICATED":
 </CodeGroup>
 
 <Info>
-Poll every 2 seconds. The session expires after 5 minutes if not completed.
+Poll every 2 seconds. The session expires after 20 minutes if not completed, and the flow times out after 10 minutes of waiting for user input.
 </Info>
 
 ### 5. Use the Profile

diff --git a/profiles/managed-auth/programmatic.mdx b/profiles/managed-auth/programmatic.mdx
@@ -353,7 +353,7 @@ The `flow_status` field indicates the current flow state:
 | `IN_PROGRESS` | Authentication is ongoing—keep polling |
 | `SUCCESS` | Login completed, profile saved |
 | `FAILED` | Login failed (check `error_message`) |
-| `EXPIRED` | Flow timed out (5 minutes) |
+| `EXPIRED` | Flow timed out (10 minutes for user input, 20 minutes overall) |
 | `CANCELED` | Flow was canceled |
 
 The `status` field indicates the overall connection state: