Blueprint Lifecycle

Start with the Runloop Quickstart to use the examples below.

Launch Parameters

Because Blueprints map to images that launch devboxes, they share some of the same launch parameters as devboxes. See these pages for more customizable parameters:

Deleting Blueprints

By default, Blueprints persist indefinitely and continue to incur storage costs. To optimize resource usage and costs, you can delete Blueprints that are no longer needed.

Deleting a Single Blueprint

To delete a specific Blueprint, use its ID:

blueprint = await runloop.blueprint.from_id(blueprint_id)
await blueprint.delete()

const blueprint = await runloop.blueprint.fromId(blueprintId);
await blueprint.delete();

Cleaning Up Old Blueprint Versions

When you create multiple versions of a Blueprint with the same name, you may want to delete older versions to reduce storage costs. Here’s how to keep only the latest version:

# Create a new blueprint
new_blueprint = await runloop.blueprint.create(
  name="my_blueprint_name",
  launch_parameters={"launch_commands": ["sudo apt install -y jq"]}
)

# Get all blueprints with the same name
blueprints = await runloop.blueprint.list(name='my_blueprint_name')

# Delete all older blueprints, keeping only the newest one
for blueprint in blueprints:
  if blueprint.id != new_blueprint.id:
    await blueprint.delete()

// Create a new blueprint
const newBlueprint = await runloop.blueprint.create({
  name: "my_blueprint_name",
  launch_parameters: { launch_commands: ["sudo apt install -y jq"] }
});

// Get all blueprints with the same name
const blueprints = await runloop.blueprint.list(name='my_blueprint_name');

// Delete all older blueprints, keeping only the newest one
for (const blueprint of blueprints) {
  if (blueprint.id !== newBlueprint.id) {
    await blueprint.delete();
    console.log(`Deleted old blueprint: ${blueprint.id}`);
  }
}

Be careful when deleting Blueprints, as this action cannot be undone. Ensure you’re not deleting Blueprints that you may need later.

Managing Blueprints with the CLI

The CLI provides convenient commands for listing, deleting, and pruning blueprints:

# List all blueprints
rli blueprint list

# Delete a specific blueprint by ID
rli blueprint delete bpt_abc123

# Prune old blueprint versions, keeping only the latest for each name
rli blueprint prune

# Prune with dry-run to see what would be deleted
rli blueprint prune --dry-run

The rli blueprint prune command is particularly useful for cleaning up old versions when you frequently rebuild blueprints with the same name.

Next Steps

Back to Blueprints Overview - Review blueprint basics and best practices
Troubleshoot blueprint builds - Debug failed builds
Learn about Devbox lifecycle - Understand how Devboxes work with Blueprints

Overview

Tools

Components

Benchmarks & Evals

Debugging

Launch Parameters

Deleting Blueprints

Deleting a Single Blueprint

Cleaning Up Old Blueprint Versions

Managing Blueprints with the CLI

Next Steps

​Launch Parameters

​Deleting Blueprints

​Deleting a Single Blueprint

​Cleaning Up Old Blueprint Versions

​Managing Blueprints with the CLI

​Next Steps

Launch Parameters

Deleting Blueprints

Deleting a Single Blueprint

Cleaning Up Old Blueprint Versions

Managing Blueprints with the CLI

Next Steps