Sandboxes

Daytona provides full composable computers — sandboxes — for AI agents. Sandboxes are isolated runtime environments you can manage programmatically to run code. Each sandbox runs in isolation, giving it a dedicated kernel, filesystem, network stack, and allocated vCPU, RAM, and disk. Agents get access to a full composable computer where they can install packages, run servers, compile code, and manage processes.

Sandboxes have 1 vCPU, 1GB RAM, and 3GiB disk by default. Organizations get a maximum sandbox resource limit of 4 vCPUs, 8GB RAM, and 10GB disk.

Sandboxes can use snapshots to capture a fully configured environment (base operating system, installed packages, dependencies and configuration) to create new sandboxes.

Each sandbox has its own network stack with per-sandbox firewall rules. By default, sandboxes follow standard network policies, but you can restrict egress to a specific set of allowed destinations or block all outbound traffic entirely.

Sandbox types
Linux Container Default Linux container runtime.
Linux VM Linux guest in a virtual machine for running Linux-specific tools and workflows.
Windows Windows OS runtime in a virtual machine for running Windows applications and tooling.
GPU NVIDIA GPU for model inference, fine-tuning, and CUDA-accelerated compute.

Create Sandboxes

Daytona provides methods to create sandboxes.

1. Navigate to Daytona Sandboxes ↗
2. Click Create Sandbox
3. Click Create to create a sandbox

Python

from daytona import Daytona

daytona = Daytona()
sandbox = daytona.create()

TypeScript

import { Daytona } from '@daytona/sdk'

const daytona = new Daytona()
const sandbox = await daytona.create()

Ruby

require 'daytona'

daytona = Daytona::Daytona.new
sandbox = daytona.create

Go

package main

import (
  "context"
  "github.com/daytonaio/daytona/libs/sdk-go/pkg/daytona"
)

func main() {
  client, _ := daytona.NewClient()
  ctx := context.Background()
  _, _ = client.Create(ctx, nil)
}

Java

import io.daytona.sdk.Daytona;
import io.daytona.sdk.Sandbox;

public class App {
    public static void main(String[] args) {
        try (Daytona daytona = new Daytona()) {
            Sandbox sandbox = daytona.create();
        }
    }
}

CLI

daytona create [flags]

API

curl 'https://app.daytona.io/api/sandbox' \
  --request POST \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --data '{}'

GPU Sandboxes

Daytona provides methods to create GPU sandboxes.

Daytona supports NVIDIA GPU devices for creating GPU sandboxes. Use GPU sandboxes for workloads such as model inference, fine-tuning, and CUDA-accelerated compute.

• NVIDIA H100
• NVIDIA RTX Pro 6000

Daytona provides a pre-built daytona-gpu snapshot for creating GPU sandboxes. Each GPU sandbox is ephemeral and supports up to 16 vCPUs, 192GB RAM, and 512GB disk.

1. Navigate to Daytona Sandboxes ↗
2. Click Create Sandbox
3. Select a GPU snapshot (daytona-gpu)
4. Select us-east-1 region
5. Select ephemeral or set auto-delete interval to 0
6. Click Create to create a GPU sandbox

Python

from daytona import Daytona, DaytonaConfig, CreateSandboxFromSnapshotParams

daytona = Daytona(DaytonaConfig(target="us-east-1"))
sandbox = daytona.create(
        CreateSandboxFromSnapshotParams(
            snapshot="daytona-gpu",
            auto_delete_interval=0
        ),
)

TypeScript

import { Daytona } from "@daytona/sdk";

const daytona = new Daytona({
  target: "us-east-1",
});
const sandbox = await daytona.create({
  snapshot: "daytona-gpu",
  ephemeral: true,
});

Ruby

require 'daytona'

config = Daytona::Config.new(
  target: "us-east-1"
)
daytona = Daytona::Daytona.new(config)
sandbox = daytona.create(
  Daytona::CreateSandboxFromSnapshotParams.new(
    snapshot: 'daytona-gpu',
    ephemeral: true
  )
)

Go

package main

import (
  "context"
  "github.com/daytonaio/daytona/libs/sdk-go/pkg/daytona"
  "github.com/daytonaio/daytona/libs/sdk-go/pkg/types"
)

func main() {
  client, _ := daytona.NewClientWithConfig(&types.DaytonaConfig{
    Target: "us-east-1",
  })
  ctx := context.Background()
  params := types.SnapshotParams{
    Snapshot: "daytona-gpu",
    SandboxBaseParams: types.SandboxBaseParams{
      Ephemeral: true,
    },
  }
  _, _ = client.Create(ctx, params)
}

Java

import io.daytona.sdk.Daytona;
import io.daytona.sdk.DaytonaConfig;
import io.daytona.sdk.Sandbox;
import io.daytona.sdk.model.CreateSandboxFromSnapshotParams;

public class App {
    public static void main(String[] args) {
        DaytonaConfig config = new DaytonaConfig.Builder()
                .apiKey(System.getenv("DAYTONA_API_KEY"))
                .target("us-east-1")
                .build();

        try (Daytona daytona = new Daytona(config)) {
            CreateSandboxFromSnapshotParams params = new CreateSandboxFromSnapshotParams();
            params.setSnapshot("daytona-gpu");
            params.setAutoDeleteInterval(0);
            Sandbox sandbox = daytona.create(params);
        }
    }
}

CLI

daytona create --snapshot daytona-gpu --target us-east-1 --auto-delete 0

API

curl 'https://app.daytona.io/api/sandbox' \
  --request POST \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --data '{
  "target": "us-east-1",
  "snapshot": "daytona-gpu",
  "autoDeleteInterval": 0
}'

To create a GPU sandbox with custom GPU count and types:

1. Create a sandbox from an image

2. Set the auto-delete interval to 0 (ephemeral)

3. Set the GPU count to the number of GPUs you want

4. Specify the GPU type(s): H100 RTX-PRO-6000

   The GPU type field accepts a single value or an ordered list of preferred types.

Python

from daytona import Daytona, CreateSandboxFromImageParams, Image, Resources, GpuType, DaytonaConfig

daytona = Daytona(DaytonaConfig(target="us-east-1"))
sandbox = daytona.create(
    CreateSandboxFromImageParams(
        image=Image.debian_slim("3.12"),
        auto_delete_interval=0,
        resources=Resources(
            gpu=1,
            gpu_type=[GpuType.H100, GpuType.RTX_PRO_6000],
        ),
    )
)

TypeScript

import { Daytona, GpuType, Image } from "@daytona/sdk";

const daytona = new Daytona({
  target: "us-east-1",
});
const sandbox = await daytona.create({
  image: Image.debianSlim("3.12"),
  autoDeleteInterval: 0,
  resources: {
    gpu: 1,
    gpuType: [GpuType.H100, GpuType.RTX_PRO_6000],
  },
});

Ruby

require 'daytona'

daytona = Daytona::Daytona.new(
  Daytona::Config.new(
    target: "us-east-1"
  )
)
sandbox = daytona.create(
  Daytona::CreateSandboxFromImageParams.new(
    image: Daytona::Image.debian_slim('3.12'),
    auto_delete_interval: 0,
    resources: Daytona::Resources.new(
      gpu: 1,
      gpu_type: [Daytona::GpuType::H100, Daytona::GpuType::RTX_PRO_6000]
    )
  )
)

Go

package main

import (
  "context"
  "github.com/daytonaio/daytona/libs/sdk-go/pkg/daytona"
  "github.com/daytonaio/daytona/libs/sdk-go/pkg/types"
)

func main() {
  client, _ := daytona.NewClientWithConfig(&types.DaytonaConfig{
    Target: "us-east-1",
  })
  ctx := context.Background()
  autoDelete := 0
  _, _ = client.Create(ctx, types.ImageParams{
    Image: "python:3.12",
    SandboxBaseParams: types.SandboxBaseParams{
      AutoDeleteInterval: &autoDelete,
    },
    Resources: &types.Resources{
      GPU:     1,
      GpuType: []types.GpuType{types.GpuTypeH100, types.GpuTypeRtxPro6000},
    },
  })
}

Java

import io.daytona.sdk.Daytona;
import io.daytona.sdk.DaytonaConfig;
import io.daytona.sdk.Sandbox;
import io.daytona.sdk.model.CreateSandboxFromImageParams;
import io.daytona.sdk.model.Resources;
import io.daytona.api.client.model.GpuType;
import java.util.List;

final class CreateGpuSandbox {
    public static void main(String[] args) {
        DaytonaConfig config = new DaytonaConfig.Builder()
                .apiKey(System.getenv("DAYTONA_API_KEY"))
                .target("us-east-1")
                .build();

        try (Daytona daytona = new Daytona(config)) {
            CreateSandboxFromImageParams params = new CreateSandboxFromImageParams();
            params.setImage("python:3.12");
            params.setAutoDeleteInterval(0);
            Resources resources = new Resources();
            resources.setGpu(1);
            resources.setGpuType(List.of(GpuType.H100, GpuType.RTX_PRO_6000));
            params.setResources(resources);
            Sandbox sandbox = daytona.create(params);
        }
    }
}

API

curl 'https://app.daytona.io/api/sandbox' \
  --request POST \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --data '{
  "target": "us-east-1",
  "image": "python:3.12",
  "autoDeleteInterval": 0,
  "gpu": 1,
  "gpuType": ["H100", "RTX-PRO-6000"]
}'

VM Sandboxes

Daytona provides methods to create VM sandboxes.

VM sandboxes run in a virtual machine and use the Linux and Windows sandbox classes. VM sandboxes support VM-only capabilities such as pause/resume and hot/cold snapshots.

• Linux VM: linux-vm
• Windows: windows

Current limitation

VM sandboxes can currently only be created from existing snapshots. Dynamic builds through the declarative builder are supported for container sandboxes only.

Linux VM Sandboxes

Daytona provides methods to create Linux VM sandboxes.

Linux VM sandboxes run a Linux guest in a virtual machine and provide consistent environments for running Linux-specific tools and workflows.

1. Create a Linux VM snapshot
2. Create a VM sandbox from the Linux VM snapshot

Python

from daytona import (
    Daytona,
    DaytonaConfig,
    CreateSnapshotParams,
    CreateSandboxFromSnapshotParams,
    SandboxClass,
)

daytona = Daytona(DaytonaConfig(target="us-west-2"))

# 1. Create a VM snapshot (linux-vm class)
daytona.snapshot.create(
    CreateSnapshotParams(
        name="my-vm-snapshot",
        image="ubuntu:22.04",
        sandbox_class=SandboxClass.LINUX_VM,
    )
)

# 2. Create a VM sandbox from the snapshot
sandbox = daytona.create(CreateSandboxFromSnapshotParams(snapshot="my-vm-snapshot"))

TypeScript

import { Daytona, SandboxClass } from "@daytona/sdk";

const daytona = new Daytona({ target: "us-west-2" });

// 1. Create a VM snapshot (linux-vm class)
await daytona.snapshot.create({
  name: "my-vm-snapshot",
  image: "ubuntu:22.04",
  sandboxClass: SandboxClass.LINUX_VM,
});

// 2. Create a VM sandbox from the snapshot
const sandbox = await daytona.create({ snapshot: "my-vm-snapshot" });

Ruby

require 'daytona'

config = Daytona::Config.new(target: 'us-west-2')
daytona = Daytona::Daytona.new(config)

# 1. Create a VM snapshot (linux-vm class)
daytona.snapshot.create(
  Daytona::CreateSnapshotParams.new(
    name: 'my-vm-snapshot',
    image: 'ubuntu:22.04',
    sandbox_class: DaytonaApiClient::SandboxClass::LINUX_VM
  )
)

# 2. Create a VM sandbox from the snapshot
sandbox = daytona.create(Daytona::CreateSandboxFromSnapshotParams.new(snapshot: 'my-vm-snapshot'))

Go

package main

import (
  "context"

  "github.com/daytonaio/daytona/libs/sdk-go/pkg/daytona"
  "github.com/daytonaio/daytona/libs/sdk-go/pkg/types"
)

func main() {
  client, _ := daytona.NewClientWithConfig(&types.DaytonaConfig{
    Target: "us-west-2",
  })
  ctx := context.Background()

  // 1. Create a VM snapshot (linux-vm class)
  sandboxClass := types.SandboxClassLinuxVM
  _, logCh, _ := client.Snapshot.Create(ctx, &types.CreateSnapshotParams{
    Name:         "my-vm-snapshot",
    Image:        "ubuntu:22.04",
    SandboxClass: &sandboxClass,
  })
  for range logCh {
  }

  // 2. Create a VM sandbox from the snapshot
  _, _ = client.Create(ctx, types.SnapshotParams{
    Snapshot: "my-vm-snapshot",
  })
}

Java

import io.daytona.sdk.Daytona;
import io.daytona.sdk.DaytonaConfig;
import io.daytona.sdk.Sandbox;
import io.daytona.api.client.model.SandboxClass;
import io.daytona.sdk.model.CreateSandboxFromSnapshotParams;

public class App {
    public static void main(String[] args) {
        DaytonaConfig config = new DaytonaConfig.Builder()
                .apiKey(System.getenv("DAYTONA_API_KEY"))
                .target("us-west-2")
                .build();

        try (Daytona daytona = new Daytona(config)) {
            // 1. Create a VM snapshot (linux-vm class)
            daytona.snapshot().create("my-vm-snapshot", "ubuntu:22.04", SandboxClass.LINUX_VM);

            // 2. Create a VM sandbox from the snapshot
            CreateSandboxFromSnapshotParams params = new CreateSandboxFromSnapshotParams();
            params.setSnapshot("my-vm-snapshot");
            Sandbox sandbox = daytona.create(params);
        }
    }
}

CLI

# 1. Create a VM snapshot (linux-vm class)
daytona snapshot create my-vm-snapshot --image ubuntu:22.04 --sandbox-class linux-vm --region us-west-2

# 2. Create a VM sandbox from the snapshot
daytona create --snapshot my-vm-snapshot --target us-west-2

API

# 1. Create a VM snapshot (linux-vm class)
curl https://app.daytona.io/api/snapshots \
  --request POST \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --data '{
    "name": "my-vm-snapshot",
    "imageName": "ubuntu:22.04",
    "sandboxClass": "linux-vm",
    "regionId": "us-west-2"
  }'

# 2. Create a VM sandbox from the snapshot
curl 'https://app.daytona.io/api/sandbox' \
  --request POST \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --data '{
    "snapshot": "my-vm-snapshot",
    "target": "us-west-2"
  }'

Windows Sandboxes

Daytona provides methods to create Windows sandboxes.

Windows sandboxes are Windows OS runtime environments used to run Windows applications. Use Windows sandboxes to run Windows-specific tools and workflows on a consistent Windows baseline.

Daytona provides a pre-built windows snapshot for creating Windows sandboxes. The snapshot uses 2 vCPU, 8GiB memory, and 30GiB disk.

1. Navigate to Daytona Sandboxes ↗
2. Click Create Sandbox
3. Select a Windows snapshot (windows)
4. Select us region
5. Click Create to create a Windows sandbox

Python

from daytona import Daytona, DaytonaConfig, CreateSandboxFromSnapshotParams

daytona = Daytona(DaytonaConfig(target="us"))
sandbox = daytona.create(
    CreateSandboxFromSnapshotParams(
        snapshot="windows",
    )
)

TypeScript

import { Daytona } from "@daytona/sdk";

const daytona = new Daytona({
  target: "us",
});
const sandbox = await daytona.create({
  snapshot: "windows",
});

Ruby

require 'daytona'

config = Daytona::Config.new(
  target: "us"
)
daytona = Daytona::Daytona.new(config)
sandbox = daytona.create(
  Daytona::CreateSandboxFromSnapshotParams.new(
    snapshot: 'windows'
  )
)

Go

package main

import (
  "context"
  "github.com/daytonaio/daytona/libs/sdk-go/pkg/daytona"
  "github.com/daytonaio/daytona/libs/sdk-go/pkg/types"
)

func main() {
  client, _ := daytona.NewClientWithConfig(&types.DaytonaConfig{
    Target: "us",
  })
  ctx := context.Background()
  params := types.SnapshotParams{
    Snapshot: "windows",
  }
  _, _ = client.Create(ctx, params)
}

Java

import io.daytona.sdk.Daytona;
import io.daytona.sdk.DaytonaConfig;
import io.daytona.sdk.Sandbox;
import io.daytona.sdk.model.CreateSandboxFromSnapshotParams;

public class App {
    public static void main(String[] args) {
        DaytonaConfig config = new DaytonaConfig.Builder()
                .apiKey(System.getenv("DAYTONA_API_KEY"))
                .target("us")
                .build();

        try (Daytona daytona = new Daytona(config)) {
            CreateSandboxFromSnapshotParams params = new CreateSandboxFromSnapshotParams();
            params.setSnapshot("windows");
            Sandbox sandbox = daytona.create(params);
        }
    }
}

CLI

daytona create --snapshot windows --target us

API

curl 'https://app.daytona.io/api/sandbox' \
  --request POST \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --data '{
  "target": "us",
  "snapshot": "windows"
}'

Linked Sandboxes

Daytona provides methods to create linked sandboxes.

Linked sandboxes are attached to an existing parent sandbox at creation time.

Create the parent sandbox first, then create one or more children whose create request references the parent’s sandbox ID. This records the relationship on the child sandbox as the linked sandbox ID. Omitting the linked sandbox parameter yields an unlinked sandbox.

• Lifecycle

  Linked sandboxes are always ephemeral and cannot be persisted or resumed after stop. The auto-delete interval must be exactly 0 on create; this is enforced, not a default. The auto-stop interval sets the idle period in minutes after which the child sandbox stops. Once stopped, linked children are auto-deleted. Deleting the parent deletes all of its linked children (cascade). One parent may have many linked children (1:N).

• Networking

  Linked sandboxes share an internal link network. Connections work in both directions: the parent can reach each child and each child can reach the parent. Every sandbox on the link network is registered under its sandbox name and ID as DNS aliases, so either works as the host. For example: telnet LINKED_SANDBOX_ID 5555 from the parent reaches port 5555 on the linked child sandbox.

Python

from daytona import CreateSandboxFromSnapshotParams, Daytona

daytona = Daytona()

parent = daytona.create()

child = daytona.create(
    CreateSandboxFromSnapshotParams(
        linked_sandbox=parent.id,
        ephemeral=True,
    )
)

# The link network registers each sandbox under its name as a DNS alias
response = child.process.exec(f"curl http://{parent.name}:3000/")

TypeScript

import { Daytona } from "@daytona/sdk";

const daytona = new Daytona();

const parent = await daytona.create();

const child = await daytona.create({
  linkedSandbox: parent.id,
  ephemeral: true,
});

// The link network registers each sandbox under its name as a DNS alias
const response = await child.process.executeCommand(
  `curl http://${parent.name}:3000/`
);

Ruby

require 'daytona'

daytona = Daytona::Daytona.new

parent = daytona.create

child = daytona.create(
  Daytona::CreateSandboxFromSnapshotParams.new(
    linked_sandbox: parent.id,
    ephemeral: true
  )
)

# The link network registers each sandbox under its name and ID as DNS aliases.
# The Ruby SDK does not expose the sandbox name, so address the parent by ID.
response = child.process.exec(command: "curl http://#{parent.id}:3000/")

Go

package main

import (
  "context"
  "fmt"

  "github.com/daytonaio/daytona/libs/sdk-go/pkg/daytona"
  "github.com/daytonaio/daytona/libs/sdk-go/pkg/types"
)

func main() {
  client, _ := daytona.NewClient()
  ctx := context.Background()

  parent, _ := client.Create(ctx, types.SnapshotParams{})

  child, _ := client.Create(ctx, types.SnapshotParams{
    SandboxBaseParams: types.SandboxBaseParams{
      LinkedSandbox: parent.ID,
      Ephemeral:     true,
    },
  })

  // The link network registers each sandbox under its name as a DNS alias
  response, _ := child.Process.ExecuteCommand(ctx, fmt.Sprintf("curl http://%s:3000/", parent.Name))
  fmt.Println(response.Result)
}

Java

import io.daytona.sdk.Daytona;
import io.daytona.sdk.Sandbox;
import io.daytona.sdk.model.CreateSandboxFromSnapshotParams;
import io.daytona.sdk.model.ExecuteResponse;

public class App {
    public static void main(String[] args) {
        try (Daytona daytona = new Daytona()) {
            Sandbox parent = daytona.create();

            CreateSandboxFromSnapshotParams childParams = new CreateSandboxFromSnapshotParams();
            childParams.setLinkedSandbox(parent.getId());
            childParams.setAutoDeleteInterval(0); // linked sandboxes must be ephemeral
            Sandbox child = daytona.create(childParams);

            // The link network registers each sandbox under its name as a DNS alias
            ExecuteResponse response = child.getProcess()
                    .executeCommand("curl http://" + parent.getName() + ":3000/");
        }
    }
}

API

# Create parent sandbox
curl 'https://app.daytona.io/api/sandbox' \
  --request POST \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --data '{}'

# Create linked child sandbox (replace PARENT_SANDBOX_ID with the id from the first response)
curl 'https://app.daytona.io/api/sandbox' \
  --request POST \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --data '{
  "linkedSandbox": "PARENT_SANDBOX_ID",
  "autoDeleteInterval": 0
}'

Ephemeral Sandboxes

Daytona provides methods to create ephemeral sandboxes.

Ephemeral sandboxes are automatically deleted once they are stopped. They are useful for short-lived tasks or testing purposes.

To create an ephemeral sandbox, set the ephemeral parameter to True when creating a sandbox. Setting autoDeleteInterval: 0 (ephemeral) has the same effect.

Python

from daytona import Daytona, CreateSandboxFromSnapshotParams

daytona = Daytona()
params = CreateSandboxFromSnapshotParams(
    ephemeral=True,
    auto_stop_interval=5,  # delete after 5 minutes of inactivity
)
sandbox = daytona.create(params)

TypeScript

import { Daytona } from "@daytona/sdk";

const daytona = new Daytona();
const sandbox = await daytona.create({
  ephemeral: true,
  autoStopInterval: 5, // delete after 5 minutes of inactivity
});

Ruby

require 'daytona'

daytona = Daytona::Daytona.new
params = Daytona::CreateSandboxFromSnapshotParams.new(
  ephemeral: true,
  auto_stop_interval: 5 # delete after 5 minutes of inactivity
)
sandbox = daytona.create(params)

Go

package main

import (
  "context"
  "github.com/daytonaio/daytona/libs/sdk-go/pkg/daytona"
  "github.com/daytonaio/daytona/libs/sdk-go/pkg/types"
)

func main() {
  client, _ := daytona.NewClient()
  ctx := context.Background()

  autoStopInterval := 5 // delete after 5 minutes of inactivity
  params := types.SnapshotParams{
    SandboxBaseParams: types.SandboxBaseParams{
      Language:         types.CodeLanguagePython,
      Ephemeral:        true,
      AutoStopInterval: &autoStopInterval,
    },
  }
  _, _ = client.Create(ctx, params)
}

Java

import io.daytona.sdk.Daytona;
import io.daytona.sdk.Sandbox;
import io.daytona.sdk.model.CreateSandboxFromSnapshotParams;

public class App {
    public static void main(String[] args) {
        try (Daytona daytona = new Daytona()) {
            CreateSandboxFromSnapshotParams params = new CreateSandboxFromSnapshotParams();
            params.setAutoDeleteInterval(0); // same effect as ephemeral: true
            params.setAutoStopInterval(5); // delete after 5 minutes of inactivity
            Sandbox sandbox = daytona.create(params);
        }
    }
}

CLI

# --auto-delete 0 has the same effect as ephemeral: true
daytona create --auto-delete 0 --auto-stop 5

API

curl 'https://app.daytona.io/api/sandbox' \
  --request POST \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --data '{
  "autoDeleteInterval": 0,
  "autoStopInterval": 5
}'

Resources

Sandboxes have 1 vCPU, 1GB RAM, and 3GiB disk by default. Organizations get a maximum sandbox resource limit of 4 vCPUs, 8GB RAM, and 10GB disk.

Resource	Unit	Default	Minimum	Maximum
CPU	vCPU	1	1	4
Memory	GiB	1	1	8
Disk	GiB	3	1	10

Pre-built snapshots

Daytona provides pre-built snapshots with fixed resource sizes for creating sandboxes.

Snapshot	vCPU	Memory	Storage	GPU
daytona-small	1	1GiB	3GiB
daytona-medium	2	4GiB	8GiB
daytona-large	4	8GiB	10GiB
daytona-gpu	1	1GiB	1GiB	1
windows	2	8GiB	30GiB

Python

from daytona import Daytona, CreateSandboxFromSnapshotParams

daytona = Daytona()
sandbox = daytona.create(
    CreateSandboxFromSnapshotParams(
        snapshot="daytona-medium",
    )
)

TypeScript

import { Daytona } from "@daytona/sdk";

const daytona = new Daytona();
const sandbox = await daytona.create({
  snapshot: "daytona-medium",
});

Ruby

require 'daytona'

daytona = Daytona::Daytona.new
sandbox = daytona.create(
  Daytona::CreateSandboxFromSnapshotParams.new(
    snapshot: 'daytona-medium'
  )
)

Go

package main

import (
  "context"
  "github.com/daytonaio/daytona/libs/sdk-go/pkg/daytona"
  "github.com/daytonaio/daytona/libs/sdk-go/pkg/types"
)

func main() {
  client, _ := daytona.NewClient()
  ctx := context.Background()
  params := types.SnapshotParams{
    Snapshot: "daytona-medium",
  }
  _, _ = client.Create(ctx, params)
}

Java

import io.daytona.sdk.Daytona;
import io.daytona.sdk.Sandbox;
import io.daytona.sdk.model.CreateSandboxFromSnapshotParams;

public class App {
    public static void main(String[] args) {
        try (Daytona daytona = new Daytona()) {
            CreateSandboxFromSnapshotParams params = new CreateSandboxFromSnapshotParams();
            params.setSnapshot("daytona-medium");
            Sandbox sandbox = daytona.create(params);
        }
    }
}

CLI

daytona create --snapshot daytona-medium

API

curl 'https://app.daytona.io/api/sandbox' \
  --request POST \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --data '{
  "snapshot": "daytona-medium"
}'

Custom resources

Daytona provides methods to create sandboxes with custom resources.

Use the Resources class to set custom sandbox resources. All resource parameters are optional and must be integers. If not specified, Daytona will use the default values. Maximum values are per-sandbox limits set at the organization level.

Python

from daytona import Daytona, CreateSandboxFromImageParams, Image, Resources

daytona = Daytona()
sandbox = daytona.create(
    CreateSandboxFromImageParams(
        image=Image.debian_slim("3.12"),
        resources=Resources(cpu=2, memory=4, disk=8),
    )
)

TypeScript

import { Daytona, Image } from "@daytona/sdk";

const daytona = new Daytona();
const sandbox = await daytona.create({
  image: Image.debianSlim("3.12"),
  resources: { cpu: 2, memory: 4, disk: 8 },
});

Ruby

require 'daytona'

daytona = Daytona::Daytona.new
sandbox = daytona.create(
  Daytona::CreateSandboxFromImageParams.new(
    image: Daytona::Image.debian_slim('3.12'),
    resources: Daytona::Resources.new(
      cpu: 2,
      memory: 4,
      disk: 8
    )
  )
)

Go

package main

import (
  "context"
  "github.com/daytonaio/daytona/libs/sdk-go/pkg/daytona"
  "github.com/daytonaio/daytona/libs/sdk-go/pkg/types"
)

func main() {
  client, _ := daytona.NewClient()
  ctx := context.Background()
  _, _ = client.Create(ctx, types.ImageParams{
    Image: "python:3.12",
    Resources: &types.Resources{
      CPU:    2,
      Memory: 4,
      Disk:   8,
    },
  })
}

Java

import io.daytona.sdk.Daytona;
import io.daytona.sdk.Sandbox;
import io.daytona.sdk.model.CreateSandboxFromImageParams;
import io.daytona.sdk.model.Resources;

final class CreateSandboxResources {
    public static void main(String[] args) {
        try (Daytona daytona = new Daytona()) {
            CreateSandboxFromImageParams params = new CreateSandboxFromImageParams();
            params.setImage("python:3.12");
            Resources resources = new Resources();
            resources.setCpu(2);
            resources.setMemory(4);
            resources.setDisk(8);
            params.setResources(resources);
            Sandbox sandbox = daytona.create(params);
        }
    }
}

CLI

daytona create --cpu 2 --memory 4 --disk 8

API

curl 'https://app.daytona.io/api/sandbox' \
  --request POST \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --data '{
  "image": "python:3.12",
  "cpu": 2,
  "memory": 4,
  "disk": 8
}'

Start Sandboxes

Daytona provides methods to start sandboxes.

1. Navigate to Daytona Sandboxes ↗
2. Click the start icon (▶) next to the sandbox you want to start

Python

sandbox.start()

TypeScript

await sandbox.start()

Ruby

sandbox.start

Go

sandbox.Start(ctx)

Java

sandbox.start();

CLI

daytona start [SANDBOX_ID] | [SANDBOX_NAME] [flags]

API

curl 'https://app.daytona.io/api/sandbox/{sandboxIdOrName}/start' \
  --request POST \
  --header 'Authorization: Bearer YOUR_API_KEY'

Get Sandbox

Daytona provides methods to get a sandbox by ID or name.

Python

sandbox = daytona.get("my-sandbox-id-or-name")

TypeScript

const sandbox = await daytona.get("my-sandbox-id-or-name");

Ruby

sandbox = daytona.get('my-sandbox-id-or-name')

Go

sandbox, err := client.Get(ctx, "my-sandbox-id-or-name")

Java

Sandbox sandbox = daytona.get("my-sandbox-id-or-name");

CLI

daytona info [SANDBOX_ID] | [SANDBOX_NAME] [flags]

API

curl 'https://app.daytona.io/api/sandbox/{sandboxIdOrName}' \
  --header 'Authorization: Bearer YOUR_API_KEY'

List Sandboxes

Daytona provides methods to list sandboxes.

Python

for sandbox in daytona.list():
    print(sandbox.id)

TypeScript

for await (const sandbox of daytona.list()) {
  console.log(sandbox.id)
}

Ruby

daytona.list.each { |sandbox| puts sandbox.id }

Go

iter := client.List(ctx, nil)
defer iter.Close()
for iter.Next() {
    sandbox := iter.Value()
    fmt.Println(sandbox.ID)
}
if err := iter.Err(); err != nil {
    log.Fatal(err)
}

Java

Iterator<Map<String, Object>> iter = daytona.list();
while (iter.hasNext()) {
    Map<String, Object> sandbox = iter.next();
    System.out.println(sandbox.get("id"));
}

CLI

daytona list [flags]

API

curl 'https://app.daytona.io/api/sandbox' \
  --header 'Authorization: Bearer YOUR_API_KEY'

Stop Sandboxes

Daytona provides methods to stop sandboxes.

Stopped sandboxes maintain filesystem persistence while their memory state is cleared. They incur only disk usage costs and can be started again when needed. Sandboxes in a stopping or stopped state will no longer accept requests.

The stopped state should be used when a sandbox is expected to be started again. Otherwise, it is recommended to stop and then archive the sandbox to eliminate disk usage costs.

1. Navigate to Daytona Sandboxes ↗
2. Click the stop icon (⏹) next to the sandbox you want to stop

Python

sandbox.stop()

TypeScript

await sandbox.stop()

Ruby

sandbox.stop

Go

sandbox.Stop(ctx)

Java

sandbox.stop();

CLI

daytona stop [SANDBOX_ID] | [SANDBOX_NAME] [flags]

API

curl 'https://app.daytona.io/api/sandbox/{sandboxIdOrName}/stop' \
  --request POST \
  --header 'Authorization: Bearer YOUR_API_KEY'

If you need a faster shutdown, use force stop (force=true / --force) to terminate the sandbox immediately. Force stop is ungraceful and should be used when quick termination is more important than process cleanup. Avoid force stop for normal shutdowns where the process should flush buffers, write final state, or run cleanup hooks.

Common use cases for force stop include:

• you need to reduce stop time and can accept immediate termination
• the entrypoint ignores termination signals or hangs during shutdown

Pause Sandboxes

Daytona provides methods to pause sandboxes.

Pausing a sandbox preserves filesystem state and memory, and does not consume CPU. To resume a paused sandbox, start it again; processes continue from where they were paused.

Pause is available for VM-based sandbox classes: linux-vm and windows.

• Use pause for workloads that hold active in-memory context across an idle period
• Use stop instead when memory state is not needed

Python

sandbox.pause()

TypeScript

await sandbox.pause()

Ruby

sandbox.pause

Go

sandbox.Pause(ctx)

Java

sandbox.pause();

CLI

daytona pause [SANDBOX_ID] | [SANDBOX_NAME]

API

curl 'https://app.daytona.io/api/sandbox/{sandboxIdOrName}/pause' \
  --request POST \
  --header 'Authorization: Bearer YOUR_API_KEY'

Archive Sandboxes

Daytona provides methods to archive sandboxes.

A sandbox must be stopped before it can be archived. When a sandbox is archived, the entire filesystem state is moved to a cost-effective object storage, making it available for an extended period.

Starting an archived sandbox takes more time than starting a stopped sandbox, depending on its size. It can be started again in the same way as a stopped sandbox.

Python

sandbox.archive()

TypeScript

await sandbox.archive()

Ruby

sandbox.archive

Go

sandbox.Archive(ctx)

CLI

daytona archive [SANDBOX_ID] | [SANDBOX_NAME] [flags]

API

curl 'https://app.daytona.io/api/sandbox/{sandboxIdOrName}/archive' \
  --request POST \
  --header 'Authorization: Bearer YOUR_API_KEY'

Recover Sandboxes

Daytona provides methods to recover sandboxes.

Python

sandbox.recover()

TypeScript

await sandbox.recover()

Ruby

sandbox.recover

API

curl 'https://app.daytona.io/api/sandbox/{sandboxIdOrName}/recover' \
  --request POST \
  --header 'Authorization: Bearer YOUR_API_KEY'

When a sandbox enters an error state, it can sometimes be recovered using the recover method, depending on the underlying error reason. The recoverable flag indicates whether the error state can be resolved through an automated recovery procedure.

Recovery actions are not performed automatically because they address errors that require further user intervention, such as freeing up storage space.

Python

# Check if the sandbox is recoverable
if sandbox.recoverable:
    sandbox.recover()

TypeScript

// Check if the sandbox is recoverable
if (sandbox.recoverable) {
  await sandbox.recover()
}

Ruby

# Check if the sandbox is in an error state before recovering
if sandbox.state == 'error'
  sandbox.recover
end

API

curl 'https://app.daytona.io/api/sandbox/{sandboxIdOrName}/recover' \
  --request POST \
  --header 'Authorization: Bearer YOUR_API_KEY'

Resize Sandboxes

Daytona provides methods to resize sandbox resources after creation.

On a running sandbox, you can increase CPU and memory without interruption. To decrease CPU or memory, or to increase disk capacity, stop the sandbox first. Disk size can only be increased and cannot be decreased.

Resizing updates the sandbox resource allocation (cpu, memory, and disk) for that sandbox only. CPU and memory control compute capacity for running workloads, while disk controls persistent filesystem capacity. Values must be integers and stay within your organization’s per-sandbox resource limits.

Python

# Resize a started sandbox (CPU and memory can be increased)
sandbox.resize(Resources(cpu=2, memory=4))

# Resize a stopped sandbox (CPU and memory can change, disk can only increase)
sandbox.stop()
sandbox.resize(Resources(cpu=4, memory=8, disk=20))
sandbox.start()

TypeScript

// Resize a started sandbox (CPU and memory can be increased)
await sandbox.resize({ cpu: 2, memory: 4 })

// Resize a stopped sandbox (CPU and memory can change, disk can only increase)
await sandbox.stop()
await sandbox.resize({ cpu: 4, memory: 8, disk: 20 })
await sandbox.start()

Ruby

# Resize a started sandbox (CPU and memory can be increased)
sandbox.resize(Daytona::Resources.new(cpu: 2, memory: 4))

# Resize a stopped sandbox (CPU and memory can change, disk can only increase)
sandbox.stop
sandbox.resize(Daytona::Resources.new(cpu: 4, memory: 8, disk: 20))
sandbox.start

Go

// Resize a started sandbox (CPU and memory can be increased)
err := sandbox.Resize(ctx, &types.Resources{CPU: 2, Memory: 4})

// Resize a stopped sandbox (CPU and memory can change, disk can only increase)
err = sandbox.Stop(ctx)
err = sandbox.Resize(ctx, &types.Resources{CPU: 4, Memory: 8, Disk: 20})
err = sandbox.Start(ctx)

API

curl 'https://app.daytona.io/api/sandbox/{sandboxIdOrName}/resize' \
  --request POST \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --data '{
  "cpu": 2,
  "memory": 4,
  "disk": 20
}'

To verify CPU and memory limits inside the sandbox after resizing, read cgroup values directly. Tools such as nproc, free, top, htop, /proc/cpuinfo, and /proc/meminfo read host-level values and do not reflect sandbox resource limits.

cat /sys/fs/cgroup/cpu.max      # "<quota> <period>" (cores = quota / period)
cat /sys/fs/cgroup/memory.max   # bytes
df -h /                         # disk

Fork Sandboxes

Daytona provides methods to fork sandboxes.

Forking creates a duplicate of your sandbox’s filesystem and memory, and copies it into a new sandbox. The new sandbox is fully independent: it can be started, stopped, and deleted without affecting the original. The sandbox must be in started state before forking.

Daytona tracks the parent-child relationship in a fork tree, so you can always trace a fork’s lineage back to the sandbox it was created from. You can fork a fork, building out branches as needed. The parent sandbox cannot be deleted while it has active fork children.

1. Navigate to Daytona Sandboxes ↗
2. Click the three-dot menu (⋮) next to the sandbox you want to fork
3. Select Fork

Python

# Fork sandbox through the Sandbox instance
forked = sandbox._experimental_fork(name="my-forked-sandbox")

TypeScript

// Fork sandbox through the Sandbox instance
const forkedSandbox = await sandbox._experimental_fork({ name: "my-forked-sandbox" });

// Or use the Daytona helper method
const forkedSandbox = await daytona._experimental_fork(sandbox, { name: "my-forked-sandbox" });

Ruby

# Fork sandbox through the Sandbox instance
forkedSandbox = sandbox.experimental_fork(name: "my-forked-sandbox")

Go

// Fork sandbox through the Sandbox instance
name := "my-forked-sandbox"
forkedSandbox, err := sandbox.ExperimentalFork(ctx, &name)
if err != nil {
    return err
}

Java

// Fork sandbox through the Sandbox instance
Sandbox forkedSandbox = sandbox.experimentalFork("my-forked-sandbox", 60);

API

curl 'https://app.daytona.io/api/sandbox/{sandboxIdOrName}/fork' \
  --request POST \
  --header 'X-Daytona-Organization-ID: YOUR_ORGANIZATION_ID' \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --data '{
  "name": "my-forked-sandbox"
}'

To view the fork tree for a sandbox and all its related sandboxes:

1. Navigate to Daytona Sandboxes ↗
2. Click the three-dot menu (⋮) next to a sandbox
3. Select View Fork Tree

The fork tree displays each sandbox in the hierarchy along with its current state and creation time, allowing you to trace the lineage of any fork back to its origin.

Label Sandboxes

Daytona provides methods to set sandbox labels.

Setting labels replaces the full label set for the sandbox. Include all labels you want to keep in the request. If you omit an existing label, it will be removed.

Python

sandbox.set_labels({
    "team": "platform",
    "env": "staging",
})

TypeScript

await sandbox.setLabels({
  team: "platform",
  env: "staging",
});

Ruby

sandbox.labels = {
  team: 'platform',
  env: 'staging'
}

Go

err := sandbox.SetLabels(ctx, map[string]string{
  "team": "platform",
  "env":  "staging",
})

Java

Map<String, String> labels = new HashMap<>();
labels.put("team", "platform");
labels.put("env", "staging");
sandbox.setLabels(labels);

API

curl 'https://app.daytona.io/api/sandbox/{sandboxIdOrName}/labels' \
  --request PUT \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --data '{
  "labels": {
    "team": "platform",
    "env": "staging"
  }
}'

Create Snapshot from Sandbox

Daytona provides methods to create a snapshot from an existing sandbox.

A snapshot captures a point-in-time copy of a sandbox that you can use as a base to create new sandboxes, templating a known-good environment for reuse.

The snapshot inherits the source sandbox’s class: a container sandbox produces a container snapshot and a VM sandbox produces a VM snapshot. The resulting snapshot can only create sandboxes of that same class.

Daytona provides the includeMemory parameter to select between a cold and a hot snapshot:

• Cold snapshot (includeMemory: false, default): captures filesystem state only. Available for container and VM sandboxes.
• Hot snapshot (includeMemory: true): captures filesystem state and memory state. VM sandboxes only. Running applications are preserved and instantly available on any new sandbox created from the snapshot.

VM sandboxes require a specific state for each snapshot type:

Include memory	Snapshot type	Snapshot contents	Required sandbox state
false (default)	Cold	Filesystem only	Stopped
true	Hot	Filesystem and memory	Started

Python

# Cold snapshot (filesystem only, sandbox stopped)
sandbox._experimental_create_snapshot("my-sandbox-snapshot")

# Hot snapshot (filesystem and memory, sandbox running)
sandbox._experimental_create_snapshot("my-sandbox-snapshot", include_memory=True)

TypeScript

// Cold snapshot (filesystem only, sandbox stopped)
await sandbox._experimental_createSnapshot("my-sandbox-snapshot");

// Hot snapshot (filesystem and memory, sandbox running)
await sandbox._experimental_createSnapshot("my-sandbox-snapshot", 60, true);

Ruby

# Cold snapshot (filesystem only, sandbox stopped)
sandbox.experimental_create_snapshot(name: "my-sandbox-snapshot")

# Hot snapshot (filesystem and memory, sandbox running)
sandbox.experimental_create_snapshot(name: "my-sandbox-snapshot", include_memory: true)

Go

// Cold snapshot (filesystem only, sandbox stopped)
err := sandbox.ExperimentalCreateSnapshot(ctx, "my-sandbox-snapshot")
if err != nil {
    return err
}

// Hot snapshot (filesystem and memory, sandbox running)
err = sandbox.ExperimentalCreateSnapshotWithMemory(ctx, "my-sandbox-snapshot", 60*time.Second)
if err != nil {
    return err
}

Java

// Cold snapshot (filesystem only, sandbox stopped)
sandbox.experimentalCreateSnapshot("my-sandbox-snapshot");

// Hot snapshot (filesystem and memory, sandbox running)
sandbox.experimentalCreateSnapshot("my-sandbox-snapshot", 60, true);

API

# Set "includeMemory": true for a hot snapshot (sandbox must be running)
curl 'https://app.daytona.io/api/sandbox/{sandboxIdOrName}/snapshot' \
  --request POST \
  --header 'X-Daytona-Organization-ID: YOUR_ORGANIZATION_ID' \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --data '{
  "name": "my-sandbox-snapshot",
  "includeMemory": false
}'

Delete Sandboxes

Daytona provides methods to delete sandboxes.

1. Navigate to Daytona Sandboxes ↗
2. Click the Delete button next to the sandbox you want to delete.

Python

sandbox.delete()

TypeScript

await sandbox.delete()

Ruby

sandbox.delete

Go

err = sandbox.Delete(ctx)

Java

sandbox.delete();

CLI

daytona delete [SANDBOX_ID] | [SANDBOX_NAME] [flags]

API

curl 'https://app.daytona.io/api/sandbox/{sandboxIdOrName}' \
  --request DELETE \
  --header 'Authorization: Bearer YOUR_API_KEY'

Sandbox lifecycle

A sandbox can have several different states. Each state reflects the status of your sandbox.

Sandbox states

State	Description
Creating	The sandbox is provisioning and will be ready to use.
Pulling Snapshot	The sandbox is pulling a snapshot to provide a base environment.
Building Snapshot	The sandbox is building a snapshot to provide a base environment.
Pending Build	The sandbox build is pending and will start shortly.
Build Failed	The sandbox build failed and needs to be retried.
Starting	The sandbox is starting and will be ready to use.
Started	The sandbox has started and is ready to use.
Stopping	The sandbox is stopping and will no longer accept requests.
Stopped	The sandbox has stopped and is no longer running.
Pausing	The sandbox is pausing while its filesystem and memory state are preserved.
Paused	The sandbox is paused with its filesystem and memory state preserved.
Resuming	The sandbox is resuming from a paused state and will be ready to use.
Archiving	The sandbox is archiving and its state will be preserved.
Archived	The sandbox has been archived and its state is preserved.
Restoring	The sandbox is being restored from archive and will be ready to use shortly.
Resizing	The sandbox is being resized to a new set of resources.
Snapshotting	The sandbox is creating a snapshot of its filesystem and memory.
Forking	The sandbox is being forked into a new independent sandbox.
Deleting	The sandbox is deleting and will be removed.
Deleted	The sandbox has been deleted and no longer exists.
Error	The sandbox is in an error state and needs to be recovered.
Unknown	The default sandbox state before it is created.

Show more

The diagram demonstrates the states and possible transitions between them.

State transitions

A sandbox can transition between states in response to various actions. The following table lists the initial state, target state, and trigger for the transition.

State transitions

Initial state	Target state	Trigger
Unknown	Pulling Snapshot	The base snapshot is being pulled to provide the sandbox environment.
Unknown	Building Snapshot	The sandbox uses a declarative image build, which begins building.
Pending Build	Building Snapshot	The queued image build starts.
Building Snapshot	Build Failed	The image build fails or times out.
Pulling Snapshot	Creating	The snapshot is available and the sandbox container is created.
Building Snapshot	Creating	The snapshot finishes building and the sandbox container is created.
Creating	Started	The sandbox container finishes initializing and is running.
Stopped	Starting	A start is requested and the sandbox boots.
Stopped	Restoring	A start is requested and the sandbox is restored from a backup.
Archived	Restoring	A start is requested and the archived filesystem is restored from object storage.
Restoring	Started	The restore completes and the sandbox is running.
Starting	Started	The sandbox is running and ready to accept requests.
Started	Stopping	A stop is requested, or the auto-stop interval is exceeded.
Stopping	Stopped	The sandbox process exits and its memory state is cleared.
Started	Pausing	A pause is requested.
Pausing	Paused	The filesystem and memory state are preserved.
Paused	Resuming	A start is requested on a paused sandbox.
Paused	Stopping	A stop is requested on a paused sandbox.
Resuming	Started	The sandbox resumes from memory and is running.
Stopped	Archiving	An archive is requested, or the auto-archive interval is exceeded.
Archiving	Archived	The backup completes and the filesystem is moved to object storage.
Started	Resizing	CPU or memory is increased on a running sandbox.
Stopped	Resizing	Resources are changed on a stopped sandbox.
Resizing	Started	The running sandbox returns to service after resizing.
Resizing	Stopped	The stopped sandbox completes resizing.
Started	Snapshotting	A snapshot of the filesystem and memory is created.
Stopped	Snapshotting	A snapshot of the filesystem is created.
Snapshotting	Started	The snapshot completes and the sandbox returns to service.
Snapshotting	Stopped	The snapshot completes and the sandbox remains stopped.
Started	Forking	The sandbox is forked into a new independent sandbox.
Forking	Started	The fork completes and the sandbox returns to service.
Started	Deleting	A delete is requested, or the auto-delete interval is exceeded.
Stopped	Deleting	A delete is requested.
Archived	Deleted	An archived sandbox is deleted directly without being restored.
Deleting	Deleted	The sandbox is removed and its resources are released.
Started	Error	An operation fails or times out.
Error	Restoring	A recover is requested for a recoverable error and the sandbox is restored.
Error	Archiving	An errored sandbox with a completed backup is archived to preserve its state.

Show more

Multiple runtime support

Daytona sandboxes support Python, TypeScript, and JavaScript programming language runtimes for direct code execution inside the sandbox. The language parameter controls which programming language runtime is used for the sandbox:

• python
• typescript
• javascript

If omitted, the Daytona SDK will default to python. To override this, explicitly set the language value when creating the sandbox.

Automated lifecycle management

Sandboxes can be automatically stopped, archived, and deleted based on user-defined intervals. The intervals act as a TTL (time-to-live) mechanism for the sandbox. You can also refresh the last activity timestamp to explicitly signal activity when lifecycle behavior depends on inactivity intervals.

Update sandbox last activity

Daytona provides methods to update a sandbox’s last activity timestamp.

This updates the sandbox’s recorded activity time without changing its runtime state. It is useful when your workflow is driven by external systems or background orchestration that may not reset inactivity tracking.

For example, if you run long-lived automation around a sandbox and want to avoid unintended auto-stop behavior, call this operation periodically to indicate that the sandbox is still actively used.

Python

sandbox.refresh_activity()

TypeScript

await sandbox.refreshActivity();

Ruby

sandbox.refresh_activity

API

curl 'https://app.daytona.io/api/sandbox/{sandboxId}/last-activity' \
  --request POST \
  --header 'Authorization: Bearer YOUR_API_KEY'

Auto-stop interval

Daytona provides methods to set the auto-stop interval.

The auto-stop interval sets the amount of time after which a running sandbox will be automatically stopped. The auto-stop triggers even if there are internal processes running in the sandbox.

The system differentiates between “internal processes” and “active user interaction”. Merely having a script or background task running is not sufficient to keep the sandbox alive.

• What resets the timer
• What does not reset the timer

The parameter can either be set to:

• a time interval in minutes
• 0: disables the auto-stop functionality, allowing the sandbox to run indefinitely

If the parameter is not set, the default interval of 15 minutes will be used.

Python

sandbox = daytona.create(CreateSandboxFromSnapshotParams(
    snapshot="my-snapshot-name",
    # Disables the auto-stop feature - default is 15 minutes
    auto_stop_interval=0,
))

TypeScript

const sandbox = await daytona.create({
  snapshot: 'my-snapshot-name',
  // Disables the auto-stop feature - default is 15 minutes
  autoStopInterval: 0,
})

Ruby

sandbox = daytona.create(
  Daytona::CreateSandboxFromSnapshotParams.new(
    snapshot: 'my-snapshot-name',
    # Disables the auto-stop feature - default is 15 minutes
    auto_stop_interval: 0
  )
)

Go

// Create a sandbox with auto-stop disabled
autoStopInterval := 0
params := types.SnapshotParams{
    Snapshot: "my-snapshot-name",
    SandboxBaseParams: types.SandboxBaseParams{
        AutoStopInterval: &autoStopInterval,
    },
}
sandbox, err := client.Create(ctx, params)

Java

import io.daytona.sdk.Daytona;
import io.daytona.sdk.Sandbox;
import io.daytona.sdk.model.CreateSandboxFromSnapshotParams;

public class App {
    public static void main(String[] args) {
        try (Daytona daytona = new Daytona()) {
            CreateSandboxFromSnapshotParams params = new CreateSandboxFromSnapshotParams();
            params.setSnapshot("my-snapshot-name");
            // Disables the auto-stop feature - default is 15 minutes
            params.setAutoStopInterval(0);
            Sandbox sandbox = daytona.create(params);
        }
    }
}

API

curl 'https://app.daytona.io/api/sandbox/{sandboxIdOrName}/autostop/{interval}' \
  --request POST \
  --header 'Authorization: Bearer YOUR_API_KEY'

What resets the timer

The inactivity timer resets only for specific external interactions:

• Updates to sandbox lifecycle states
• Network requests through sandbox previews
• Active SSH connections
• API requests to the Daytona Toolbox SDK

What does not reset the timer

The following do not reset the timer:

• SDK requests that are not toolbox actions
• Background scripts (e.g., npm run dev run as a fire-and-forget command)
• Long-running tasks without external interaction
• Processes that don’t involve active monitoring

If you run a long-running task like LLM inference that takes more than 15 minutes to complete without any external interaction, the sandbox may auto-stop mid-process because the process itself doesn’t count as “activity”, therefore the timer is not reset.

Auto-archive interval

Daytona provides methods to set the auto-archive interval.

The auto-archive interval sets the amount of time after which a continuously stopped sandbox will be automatically archived. The parameter can either be set to:

• a time interval in minutes
• 0: the maximum interval of 30 days will be used

If the parameter is not set, the default interval of 7 days will be used.

Python

sandbox = daytona.create(CreateSandboxFromSnapshotParams(
    snapshot="my-snapshot-name",
    # Auto-archive after a sandbox has been stopped for 1 hour
    auto_archive_interval=60,
))

TypeScript

const sandbox = await daytona.create({
  snapshot: 'my-snapshot-name',
  // Auto-archive after a sandbox has been stopped for 1 hour
  autoArchiveInterval: 60,
})

Ruby

sandbox = daytona.create(
  Daytona::CreateSandboxFromSnapshotParams.new(
    snapshot: 'my-snapshot-name',
    # Auto-archive after a sandbox has been stopped for 1 hour
    auto_archive_interval: 60
  )
)

Go

// Create a sandbox with auto-archive after 1 hour
autoArchiveInterval := 60
params := types.SnapshotParams{
    Snapshot: "my-snapshot-name",
    SandboxBaseParams: types.SandboxBaseParams{
        AutoArchiveInterval: &autoArchiveInterval,
    },
}
sandbox, err := client.Create(ctx, params)

Java

import io.daytona.sdk.Daytona;
import io.daytona.sdk.Sandbox;
import io.daytona.sdk.model.CreateSandboxFromSnapshotParams;

public class App {
    public static void main(String[] args) {
        try (Daytona daytona = new Daytona()) {
            CreateSandboxFromSnapshotParams params = new CreateSandboxFromSnapshotParams();
            params.setSnapshot("my-snapshot-name");
            // Auto-archive after a sandbox has been stopped for 1 hour
            params.setAutoArchiveInterval(60);
            Sandbox sandbox = daytona.create(params);
        }
    }
}

API

curl 'https://app.daytona.io/api/sandbox/{sandboxIdOrName}/autoarchive/{interval}' \
  --request POST \
  --header 'Authorization: Bearer YOUR_API_KEY'

Auto-delete interval

Daytona provides methods to set the auto-delete interval.

The auto-delete interval sets the amount of time after which a continuously stopped sandbox will be automatically deleted. By default, sandboxes will never be automatically deleted. The parameter can either be set to:

• a time interval in minutes
• -1: disables the auto-delete functionality
• 0: the sandbox will be deleted immediately after stopping

If the parameter is not set, the sandbox will not be deleted automatically.

Python

sandbox = daytona.create(CreateSandboxFromSnapshotParams(
    snapshot="my-snapshot-name",
    # Auto-delete after a sandbox has been stopped for 1 hour
    auto_delete_interval=60,
))

# Delete the sandbox immediately after it has been stopped
sandbox.set_auto_delete_interval(0)

# Disable auto-deletion
sandbox.set_auto_delete_interval(-1)

TypeScript

const sandbox = await daytona.create({
  snapshot: 'my-snapshot-name',
  // Auto-delete after a sandbox has been stopped for 1 hour
  autoDeleteInterval: 60,
})

// Delete the sandbox immediately after it has been stopped
await sandbox.setAutoDeleteInterval(0)

// Disable auto-deletion
await sandbox.setAutoDeleteInterval(-1)

Ruby

sandbox = daytona.create(
  Daytona::CreateSandboxFromSnapshotParams.new(
    snapshot: 'my-snapshot-name',
    # Auto-delete after a sandbox has been stopped for 1 hour
    auto_delete_interval: 60
  )
)

# Delete the sandbox immediately after it has been stopped
sandbox.auto_delete_interval = 0

# Disable auto-deletion
sandbox.auto_delete_interval = -1

Go

// Create a sandbox with auto-delete after 1 hour
autoDeleteInterval := 60
params := types.SnapshotParams{
    Snapshot: "my-snapshot-name",
    SandboxBaseParams: types.SandboxBaseParams{
        AutoDeleteInterval: &autoDeleteInterval,
    },
}
sandbox, err := client.Create(ctx, params)

// Delete the sandbox immediately after it has been stopped
zeroInterval := 0
err = sandbox.SetAutoDeleteInterval(ctx, &zeroInterval)

// Disable auto-deletion
disableInterval := -1
err = sandbox.SetAutoDeleteInterval(ctx, &disableInterval)

Java

import io.daytona.sdk.Daytona;
import io.daytona.sdk.Sandbox;
import io.daytona.sdk.model.CreateSandboxFromSnapshotParams;

public class App {
    public static void main(String[] args) {
        try (Daytona daytona = new Daytona()) {
            CreateSandboxFromSnapshotParams params = new CreateSandboxFromSnapshotParams();
            params.setSnapshot("my-snapshot-name");
            // Auto-delete after a sandbox has been stopped for 1 hour
            params.setAutoDeleteInterval(60);
            Sandbox sandbox = daytona.create(params);

            // Delete the sandbox immediately after it has been stopped
            sandbox.setAutoDeleteInterval(0);

            // Disable auto-deletion
            sandbox.setAutoDeleteInterval(-1);
        }
    }
}

API

curl 'https://app.daytona.io/api/sandbox/{sandboxIdOrName}/autodelete/{interval}' \
  --request POST \
  --header 'Authorization: Bearer YOUR_API_KEY'

Running indefinitely

Daytona provides methods to run sandboxes indefinitely.

By default, Daytona sandboxes auto-stop after 15 minutes of inactivity. To keep a sandbox running without interruption, set the auto-stop interval to 0 when creating a new sandbox:

Python

sandbox = daytona.create(CreateSandboxFromSnapshotParams(
    snapshot="my_awesome_snapshot",
    # Disables the auto-stop feature - default is 15 minutes
    auto_stop_interval=0,
))

TypeScript

const sandbox = await daytona.create({
  snapshot: 'my_awesome_snapshot',
  // Disables the auto-stop feature - default is 15 minutes
  autoStopInterval: 0,
})

Ruby

sandbox = daytona.create(
  Daytona::CreateSandboxFromSnapshotParams.new(
    snapshot: 'my_awesome_snapshot',
    # Disables the auto-stop feature - default is 15 minutes
    auto_stop_interval: 0
  )
)

Go

// Disables the auto-stop feature - default is 15 minutes
autoStopInterval := 0
params := types.SnapshotParams{
    Snapshot: "my_awesome_snapshot",
    SandboxBaseParams: types.SandboxBaseParams{
        AutoStopInterval: &autoStopInterval,
    },
}
sandbox, err := client.Create(ctx, params)

Java

import io.daytona.sdk.Daytona;
import io.daytona.sdk.Sandbox;
import io.daytona.sdk.model.CreateSandboxFromSnapshotParams;

public class App {
    public static void main(String[] args) {
        try (Daytona daytona = new Daytona()) {
            CreateSandboxFromSnapshotParams params = new CreateSandboxFromSnapshotParams();
            params.setSnapshot("my_awesome_snapshot");
            // Disables the auto-stop feature - default is 15 minutes
            params.setAutoStopInterval(0);
            Sandbox sandbox = daytona.create(params);
        }
    }
}