call it developer preview as a middle ground for the pricing not figured out

matthewlouisbrockman · matthewlouisbrockman · commit 83a34916fc23 · 2026-02-27T15:10:43.000-08:00
diff --git a/docs/agents/amp.mdx b/docs/agents/amp.mdx
@@ -299,7 +299,7 @@ python build.py
 
 <CardGroup cols={3}>
   <Card title="Sandbox persistence" icon="clock" href="/docs/sandbox/persistence">
-    Auto-pause, resume, and manage sandbox lifecycle
+    Developer Preview: auto-pause, resume, and manage sandbox lifecycle
   </Card>
   <Card title="Git integration" icon="code-branch" href="/docs/sandbox/git-integration">
     Clone repos, manage branches, and push changes
diff --git a/docs/agents/claude-code.mdx b/docs/agents/claude-code.mdx
@@ -451,7 +451,7 @@ python build.py
     Connect Claude Code to 200+ MCP tools
   </Card>
   <Card title="Sandbox persistence" icon="clock" href="/docs/sandbox/persistence">
-    Auto-pause, resume, and manage sandbox lifecycle
+    Developer Preview: auto-pause, resume, and manage sandbox lifecycle
   </Card>
   <Card title="Git integration" icon="code-branch" href="/docs/sandbox/git-integration">
     Clone repos, manage branches, and push changes
diff --git a/docs/agents/codex.mdx b/docs/agents/codex.mdx
@@ -355,7 +355,7 @@ python build.py
 
 <CardGroup cols={3}>
   <Card title="Sandbox persistence" icon="clock" href="/docs/sandbox/persistence">
-    Auto-pause, resume, and manage sandbox lifecycle
+    Developer Preview: auto-pause, resume, and manage sandbox lifecycle
   </Card>
   <Card title="Git integration" icon="code-branch" href="/docs/sandbox/git-integration">
     Clone repos, manage branches, and push changes
diff --git a/docs/agents/openclaw.mdx b/docs/agents/openclaw.mdx
@@ -386,9 +386,9 @@ sandbox.kill()
 
 OpenClaw has a built-in [web UI and chat interface](https://openclaw.ai) served by its gateway. Start it inside a sandbox and connect from your browser.
 
-<Warning>
-This sandbox is created with a 10-minute timeout and auto-pause enabled — after 10 minutes of inactivity it pauses and can be resumed later. See [Sandbox Persistence](/docs/sandbox/persistence) and [Sandbox Lifecycle](/docs/sandbox) for more details.
-</Warning>
+<Warning>
+This sandbox is created with a 10-minute timeout and auto-pause enabled. After 10 minutes of inactivity it pauses and can be resumed later. Pause/resume persistence and auto-resume are currently in **Developer Preview**. See [Sandbox Persistence](/docs/sandbox/persistence) and [Sandbox Lifecycle](/docs/sandbox) for more details.
+</Warning>
 
 <CodeGroup>
 ```typescript JavaScript & TypeScript
@@ -499,7 +499,7 @@ python build.py
 
 <CardGroup cols={3}>
   <Card title="Sandbox persistence" icon="clock" href="/docs/sandbox/persistence">
-    Auto-pause, resume, and manage sandbox lifecycle
+    Developer Preview: auto-pause, resume, and manage sandbox lifecycle
   </Card>
   <Card title="Git integration" icon="code-branch" href="/docs/sandbox/git-integration">
     Clone repos, manage branches, and push changes
diff --git a/docs/agents/opencode.mdx b/docs/agents/opencode.mdx
@@ -277,7 +277,7 @@ python build.py
 
 <CardGroup cols={3}>
   <Card title="Sandbox persistence" icon="clock" href="/docs/sandbox/persistence">
-    Auto-pause, resume, and manage sandbox lifecycle
+    Developer Preview: auto-pause, resume, and manage sandbox lifecycle
   </Card>
   <Card title="Git integration" icon="code-branch" href="/docs/sandbox/git-integration">
     Clone repos, manage branches, and push changes
diff --git a/docs/billing.mdx b/docs/billing.mdx
@@ -93,7 +93,7 @@ Check your usage and costs in the [dashboard usage tab](https://e2b.dev/dashboar
 
   <Accordion title="How do I optimize costs?">
     - **Always kill sandboxes when done** - Use `sbx.kill()` to stop billing immediately
-    - **Enable autopause** - Automatically pause sandboxes after a period of inactivity to stop billing while preserving state
+    - **Enable auto-pause (Developer Preview)** - Automatically pause sandboxes after inactivity to stop billing while preserving state
     - **Allocate only what you need** - Start with default resources (2 vCPU, 1 GB RAM) and increase only if necessary
     - **Implement automatic timeouts** - Set max session lengths to prevent forgotten sandboxes from running
     - **Monitor actively running sandboxes** - Use the [CLI](/docs/cli/list-sandboxes) or [dashboard](https://e2b.dev/dashboard?tab=usage) to track active sandboxes
diff --git a/docs/sandbox.mdx b/docs/sandbox.mdx
@@ -7,14 +7,15 @@ When you start the sandbox, it stays alive for 5 minutes by default but you can
 After the time passes, the sandbox will be automatically shutdown.
 
 For timeout lifecycle behavior like pausing and auto-resume policies on create, see [AutoResume](/docs/sandbox/auto-resume).
+Pause/resume persistence and auto-resume are currently in **Developer Preview**.
 
 <Warning>
 The maximum time sandbox can be kept running without being paused is 
 - 24 hours on the Pro Tier
 - 1 hour on the Base Tier
 
-For more details, please refer to [sandbox persistance page](/docs/sandbox/persistence#limitations-while-in-beta).
-</Warning>
+For more details, please refer to the [sandbox persistence page](/docs/sandbox/persistence#current-limitations-subject-to-change).
+</Warning>
 
 <CodeGroup>
 ```js JavaScript & TypeScript highlight={6}
diff --git a/docs/sandbox/auto-resume.mdx b/docs/sandbox/auto-resume.mdx
@@ -3,6 +3,12 @@ title: "AutoResume"
 sidebarTitle: AutoResume
 ---
 
+<Note>
+`AutoResume` and `pause/resume` persistence are available as **Developer Preview**.
+
+Behavior and limits may change as we iterate. Review [Sandbox persistence limitations](/docs/sandbox/persistence#current-limitations-subject-to-change).
+</Note>
+
 Many workloads don't need a sandbox running all the time, but when they do need it, it should just work, whether it was paused or not.
 
 `AutoResume` handles this automatically: a paused sandbox wakes up when traffic arrives, so your code never has to check or manage sandbox state.
diff --git a/docs/sandbox/persistence.mdx b/docs/sandbox/persistence.mdx
@@ -4,9 +4,9 @@ sidebarTitle: Persistence
 ---
 
 <Note>
-Pause and resume are available to all users for a limited time.
+`Pause/resume` and `AutoResume` are available as **Developer Preview**.
 
-We're still actively testing and improving persistence behavior and performance, so details may change. Review the [current limitations](#current-limitations-subject-to-change).
+We're actively testing and improving persistence behavior and performance, so details may change. Review the [current limitations](#current-limitations-subject-to-change).
 </Note>
 
 The sandbox persistence allows you to pause your sandbox and resume it later from the same state it was in when you paused it.
diff --git a/docs/use-cases/coding-agents.mdx b/docs/use-cases/coding-agents.mdx
@@ -48,9 +48,9 @@ Since each sandbox is a full Linux environment, you can run any coding agent —
   <Card title="Git Integration" icon="code-branch" href="/docs/sandbox/git-integration">
     Clone repos, manage branches, and push changes from sandboxes
   </Card>
-  <Card title="Sandbox Persistence" icon="floppy-disk" href="/docs/sandbox/persistence">
-    Pause and resume sandboxes to preserve state across sessions
-  </Card>
+  <Card title="Sandbox Persistence" icon="floppy-disk" href="/docs/sandbox/persistence">
+    Developer Preview: Pause and resume sandboxes to preserve state
+  </Card>
   <Card title="Custom Templates" icon="cube" href="/docs/template/quickstart">
     Build your own sandbox templates with custom tools and dependencies
   </Card>
diff --git a/snippets/Concepts.jsx b/snippets/Concepts.jsx
@@ -11,7 +11,7 @@ export const Concepts = () => {
       href: "/docs/sandbox/persistence",
       title: "Sandbox persistence",
       description:
-        "Learn how to achieve data persistence by pausing and resuming sandboxes.",
+        "Developer Preview: Pause and resume sandboxes to preserve state.",
       icon: "rotate-reverse",
     },
     // {
