Fly Sprites to Vakna: SDK calls and vakna commands

Each Sprites 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. Sprites' docs cover its sprite CLI and REST API; the JavaScript calls are from its SDK's README.

Which vakna command replaces each Sprites call?

Sprites	vakna
`client.createSprite(name)` (README)	`vakna create <box>`
`sprite.exec('echo hello')`, `sprite exec -- ls -la` (docs)	`vakna shell <box> -- ls -la`
`client.listSprites()`, `sprite list` (docs)	`vakna list`
`sprite.delete()`, `sprite destroy -s <name>` (docs)	`vakna delete <box>`
none: a sprite suspends itself when idle (docs)	`vakna suspend <box>`, `vakna resume <box>`
`sprite checkpoint create`, `sprite restore <id>` (docs)	`vakna snapshot <box>`
`POST /v1/sprites/{name}/policy/network` (docs)	`vakna net allow <host>`
`PUT /v1/sprites/{name}/fs/write` (docs)	`tar c . \| vakna shell <box> -- tar x`
`client.sprite('my-sprite')` (README)	address the box by name in any command

What has no equivalent in Vakna?

Suspending on its own after about 30 idle seconds, and waking on the next request (docs).
An HTTPS URL for every sprite, public if you choose, and sprite proxy for any TCP port (docs).
A persistent 100 GB volume per sprite (docs).

Where does Sprites do more?

SDKs in JavaScript, Go, Python and Elixir, and adapters for agent frameworks (docs).
Compute billed only while a sprite is active (docs).
Managed services and connectors, and a remote MCP integration (llms.txt).

What does Vakna do that Sprites' docs don't show?

Fork: many boxes from one snapshot with their processes running. A Sprites checkpoint restores files, not processes (docs).
A receipt for every command, with what it cost.