kernel · andrewleesteele · Jul 30, 2026 · Jul 30, 2026 · Jul 30, 2026 · Jul 30, 2026
diff --git a/browsers/pools.mdx b/browsers/pools.mdx
@@ -7,6 +7,10 @@ Browser pools let you configure a set of identical browsers ready for immediate
 
 Acquiring from a pool is faster than `browsers.create()` for two reasons. The browser is already running, so you skip start-up and the [Chromium restart](/browsers/performance#troubleshooting-latency) that some settings trigger on a new browser. And `acquire` isn't [rate limited](/info/pricing#rate-limiting) the way browser creation is. Idle browsers in a pool aren't billed, but the pool's capacity counts against your [concurrency limit](/info/pricing#concurrency-limits). See [Scale](/introduction/scale) for how pools fit into production architecture.
 
+<Info>
+New to browser pools? The [Quickstart](/quickstart) walks through creating one and serving a workload from it. This page covers the configuration and behavior.
+</Info>
+
 ## How browser pools work
 
 <Steps>

diff --git a/docs.json b/docs.json
@@ -20,7 +20,6 @@
     { "source": "/browsers/pools/policy-json", "destination": "/browsers/chrome-policies" },
     { "source": "/browsers/pools/overview", "destination": "/browsers/pools" },
     { "source": "/introduction", "destination": "/" },
-    { "source": "/quickstart", "destination": "/" },
     { "source": "/home", "destination": "/" },
     { "source": "/llm.md", "destination": "/integrations/stripe-projects" },
     { "source": "/llm-browser.md", "destination": "/integrations/stripe-projects-browser" }
@@ -83,6 +82,12 @@
               "introduction/scale"
             ]
           },
+          {
+            "group": "Get started",
+            "pages": [
+              "quickstart"
+            ]
+          },
           {
             "group": "Working with your browser",
             "pages": [

diff --git a/index.mdx b/index.mdx
@@ -24,6 +24,8 @@ We build crazy fast, open source infra for AI agents to access the internet. Tru
 
 ## start here
 
+new here? the [quickstart](/quickstart) runs the whole path end to end — install, drive your first browser, then serve a workload from a browser pool. or jump straight to a stage:
+
 <Columns cols={3}>
   <Card title="Create" href="/introduction/create">
     Spin up a browser and pick the shape — headless, stealth, GPU, profiles.
-Original file line number
+Diff line change
@@ Expand Up @@
     Acquiring from a pool is faster than `browsers.create()` for two reasons. The browser is already running, so you skip start-up and the [Chromium restart](/browsers/performance#troubleshooting-latency) that some settings trigger on a new browser. And `acquire` isn't [rate limited](/info/pricing#rate-limiting) the way browser creation is. Idle browsers in a pool aren't billed, but the pool's capacity counts against your [concurrency limit](/info/pricing#concurrency-limits). See [Scale](/introduction/scale) for how pools fit into production architecture.
+    <Info>
+    New to browser pools? The [Quickstart](/quickstart) walks through creating one and serving a workload from it. This page covers the configuration and behavior.
+    </Info>
     ## How browser pools work
     <Steps>
@@ Expand Down @@