Skip to content

Commit e7bd85d

Browse files
committed
Note that paused sandboxes are not billed
1 parent 692e8f3 commit e7bd85d

1 file changed

Lines changed: 2 additions & 0 deletions

File tree

docs/faq/paused-sandboxes-concurrency.mdx

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,8 @@ sidebarTitle: Paused sandboxes & concurrency
55

66
No. Only running sandboxes count toward your concurrency limit. Paused sandboxes are excluded, so you can keep many paused sandboxes around without affecting how many sandboxes you can run at the same time.
77

8+
Paused sandboxes are also not billed. You are only charged for sandboxes while they are running, so keeping a sandbox paused has no impact on your bill.
9+
810
There is also no time limit on how long a sandbox can remain paused. Paused sandboxes are kept indefinitely, with no automatic deletion or time-to-live, and you can [resume](/docs/sandbox/persistence#resuming-sandbox) them at any time.
911

1012
E2B never kills paused sandboxes on its own. A paused sandbox is only removed when you explicitly call `kill` on it (either via `sandbox.kill()` or `Sandbox.kill(sandboxId)`).

0 commit comments

Comments
 (0)