twig.
Durable workspaces · internal alpha

Temporary compute.
Lasting work.

Give every runner a workspace that stays.
Keep files, dependencies and progress across disposable compute.

Create your organization Read the quickstart
Built for E2B. Designed for compute independence.
twig.
C Acme engineering
Disks
Templates
API keys
Illustrative workspace view
Acme engineering / Disks

Work that stays.

+ New disk
WorkspaceRegionState
react-starterus-west1Template
student-workspaceus-west1Ready
python-labus-west1Ready
Separate compute. Persistent files. Explicit recovery.

A home for your working state

Stop rebuilding
what was already there.

Source code is only part of a workspace. Twig keeps the rest alongside it—from package trees to the last saved change.

Keep the whole workspace

Persist dependencies, virtual environments, ignored files and .git together in a mounted directory.

Start from a branch

Turn a prepared environment into an immutable template. Fork independent workspaces with copy-on-write storage.

Make durability explicit

Separate buffered saves, durable live storage and published recovery checkpoints. Know what your app is acknowledging.

A small API. A separate lifecycle.

Your runner is replaceable.
Your workspace isn’t.

Create a disk from your backend. Deliver scoped credentials to the runner. Checkpoint work before a submission, then restore it on fresh compute.

Explore the E2B integration 
 TypeScript · integration outline
const disk = await twig.disks.create({
  name: 'student-workspace',
  region: 'us-west1',
  size_gib: 8,
});

const attachment = await twig.attachments.create(
  disk.id, { owner: runnerId, role: 'writer' }
);

// Mount using the E2B adapter.
// Publish a checkpoint before accepting submission.

The storage lives outside your runner

Compute comes and goes.
The disk has its own home.

Your runnerMounted workspace
Regional storageLive workspace disk
Checkpoint bucketPublished checkpoints

Keep active writers near their storage region. Templates and checkpoints are immutable; writer access is scoped outside the guest.

Understand the security boundary

Give your next runner
something to come back to.

Start with the API and E2B integration guide. Student access follows the documented qualification gates.

Start building