Migrations

Daytona to Vakna: SDK calls and vakna commands

Note
This page is generated from a mock CLI, and its numbers are placeholders.

Verified against vakna 0.0.0-mock on

Each Daytona SDK call maps to one vakna command below. Their calls are from their public docs, checked on 20 October 2026, with the page for each. Vakna is a CLI; they are SDKs, so a row maps a call to a command, not a function to a function.

Which vakna command replaces each Daytona call?

Daytona (TypeScript SDK) vakna
daytona.create({ snapshot }) (docs) vakna create
sandbox.process.executeCommand("ls -la") (docs) vakna shell <box> -- ls -la
daytona.list() (docs) vakna list
sandbox.delete() (docs) vakna delete <box>
sandbox.pause(), then sandbox.start() (docs) vakna suspend <box>, vakna resume <box>
sandbox.createSnapshot(name), sandbox.fork() (docs) vakna snapshot <box>, vakna fork <box> --count <n> -- <command>
daytona.create({ networkBlockAll }), domainAllowList (docs) lockdown by default, vakna net allow <host>
sandbox.fs.uploadFile(buffer, path) (docs) tar c . | vakna shell <box> -- tar x
daytona.get(sandboxIdOrName) (docs) address the box by name or id in any command

What has no equivalent in Vakna?

  • Automatic stop, archive and delete intervals: autoStopInterval and its siblings (docs).
  • A preview URL for a port: sandbox.getPreviewLink(port) (docs).
  • CPU, memory and disk set per sandbox (docs).

Where does Daytona do more?

  • GPU sandboxes, up to eight GPUs, and nested virtualization (docs).
  • Computer use on Linux and Windows desktops (docs).
  • Shared US and EU regions, dedicated regions and bring-your-own-cloud (docs).

What does Vakna do that Daytona's docs don't show?

  • A fork of many boxes is one command with one receipt, failures grouped by signature.
  • Lockdown is the default for every box, not a setting per sandbox.

View as Markdown