Understanding sandbox TTL and expiration policies

​

TTL policy types

• ttl-idle: Delete a sandbox after a specified period of inactivity
• ttl-max-age: Delete a sandbox after a maximum age, regardless of activity
• date: Delete a sandbox on a specific date

• ttl: Set a maximum age with simpler syntax
• expires: Set an absolute expiration date

​

Configure TTL policies

import { SandboxInstance } from "@blaxel/core";

const sandbox = await SandboxInstance.create({
  name: "my-sandbox",
  image: "my-image",
  ttl: "24h",
  // OR
  // expires: new Date(Date.now() + 86400000),
  // OR / AND
  lifecycle: {
    expirationPolicies: [
      { type: "ttl-idle", value: "1h", action: "delete" },
    ],
  },
});

​

Policy behavior

​

Idle TTL timing

​

Processing frequency

​

Computed termination time

​

Deletion process

1. Blaxel terminates the sandbox.
2. The sandbox remains in the terminated state for a retention period, which depends on your tier configuration.
3. Blaxel deletes the sandbox completely.

​

Tier limits

• Tier 0: A maximum TTL of 7 days is enforced
• Tier 1: A hard 30-day maximum lifetime is enforced, and expiresIn reflects this limit
• Tier 2 and above: No maximum TTL is enforced, and ttl-idle supports rolling expiration based on activity

​

Idempotent sandbox creation

​

Update an existing sandbox

​

Preview cleanup