Devbox Lifetime Management

Start with the Runloop Quickstart to use the examples below.

Manual Stopping

You can stop a running Devbox any time using the devbox.shutdown call in the client SDK.

devbox = await runloop.devbox.create()
...
await devbox.shutdown()

const devbox = await runloop.devbox.create();
...
await devbox.shutdown();

Devbox Max Lifetime

When you create a Devbox, it is automatically given a maximum lifetime. This prevents unwanted charges by leaving Devboxes running when they are not needed. The default lifetime is 1 hour, but this can be configured when you create the Devbox:

devbox = await runloop.devbox.create(
    launch_parameters={
        "keep_alive_time_seconds": 1800,
    },
)

const devbox = await runloop.devbox.create({
  launch_parameters: {
    keep_alive_time_seconds: 1800,
  },
});

Configure either keep_alive_time_seconds or an idle policy, not both. Use keep_alive_time_seconds when you want a fixed maximum lifetime for the Devbox. Use lifecycle.after_idle with on_idle when you want Runloop to act only after the Devbox becomes idle. Mixed configurations are not recommended for normal use: depending on the API or client path, the request may be rejected or the idle policy may take precedence over the fixed keep-alive timeout.

Idle Behavior

You can also configure your Devboxes to automatically shutdown or suspend when they are idle using the lifecycle.after_idle launch parameter. By default, Runloop will do nothing if your Devbox is idle. on_idle only applies to RUNNING Devboxes and the action won’t be taken if the Devbox is not in RUNNING state.

devbox = await runloop.devbox.create(
    launch_parameters={
        "lifecycle": {
            "after_idle": {"idle_time_seconds": 1800, "on_idle": "suspend"},
        }
    },
)

const devbox = await runloop.devbox.create({
  launch_parameters: {
    lifecycle: {
      after_idle: { idle_time_seconds: 1800, on_idle: "suspend" },
    },
  },
});

Network Access Control

You can restrict what network resources a Devbox can access by applying a Network Policy. This is useful for security, compliance, and controlling costs.

# Create a policy that only allows specific hosts
policy = await runloop.network_policies.create(
    name="restricted-policy",
    allow_all=False,
    allowed_hostnames=["github.com", "api.openai.com"]
)

# Create a devbox with the network policy
devbox = await runloop.devbox.create(
    launch_parameters={
        "network_policy_id": policy.id
    }
)

// Create a policy that only allows specific hosts
const policy = await runloop.networkPolicy.create({
    name: "restricted-policy",
    allow_all: false,
    allowed_hostnames: ["github.com", "api.openai.com"]
});

// Create a devbox with the network policy
const devbox = await runloop.devbox.create({
    launch_parameters: {
        network_policy_id: policy.id
    }
});

See the Network Policies documentation for more details on creating and managing policies.

Overview

Tools

Components

Benchmarks & Evals

Debugging

Manual Stopping

Devbox Max Lifetime

Idle Behavior

Network Access Control

​Manual Stopping

​Devbox Max Lifetime

​Idle Behavior

​Network Access Control

Manual Stopping

Devbox Max Lifetime

Idle Behavior

Network Access Control