Use template names instead of image IDs when creating sandboxes

You can use a template name instead of an IMAGE_ID when creating a sandbox. This keeps code readable and portable across development and production workspaces.

Create from a template name

Pass the deployed template name to the image property:

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

const sandbox = await SandboxInstance.create({
  name: "my-sandbox",
  image: "my-template",
  memory: 4096,
  ports: [
    { name: "nextjs-dev", target: 3000 },
    { name: "another-api", target: 8888 },
  ],
});

Requirements

Deploy the template in every workspace where you use it
Keep the template name consistent across workspaces

Benefits

Using a template name provides:

More readable and maintainable code
Consistent references across environments
No need to retrieve and hardcode workspace-specific image IDs

For example, you no longer need a lookup command like:

bl get sandboxes mytemplate -o json | jq -r '.[0].spec.runtime.image'

Sandbox images

Build, deploy, and use reusable sandbox images.

Sandbox overview

Review sandbox creation and configuration options.

Last modified on October 5, 2026

Get Started

Sandboxes

Agent Drive

Volumes

Batch Jobs

Applications

MCP Servers Hosting

Model Gateway

Observability

Integrations

Administration & security

Troubleshooting

Use template names instead of image IDs when creating sandboxes

Create from a template name

Requirements

Benefits

Sandbox images

Sandbox overview

​Create from a template name

​Requirements

​Benefits

Sandbox images

Sandbox overview

Create from a template name

Requirements

Benefits