---
title: "Fly Sprites to Vakna: SDK calls and vakna commands"
description: "Each Fly Sprites call next to the vakna command that does the same, what has no equivalent, and where Sprites does more."
sources_checked: "2026-10-20"
verified:
  cli: "0.0.0-mock"
  date: "2026-10-20"
---

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](https://github.com/superfly/sprites-js)) | `vakna create <box>` |
| `sprite.exec('echo hello')`, `sprite exec -- ls -la` ([docs](https://fly.io/sprites)) | `vakna shell <box> -- ls -la` |
| `client.listSprites()`, `sprite list` ([docs](https://docs.fly.io/sprites/working-with-sprites)) | `vakna list` |
| `sprite.delete()`, `sprite destroy -s <name>` ([docs](https://docs.fly.io/sprites/working-with-sprites)) | `vakna delete <box>` |
| none: a sprite suspends itself when idle ([docs](https://docs.fly.io/sprites/concepts/lifecycle)) | `vakna suspend <box>`, `vakna resume <box>` |
| `sprite checkpoint create`, `sprite restore <id>` ([docs](https://docs.fly.io/sprites/working-with-sprites)) | `vakna snapshot <box>` |
| `POST /v1/sprites/{name}/policy/network` ([docs](https://docs.fly.io/sprites/api/network-policy/set-network-policy)) | `vakna net allow <host>` |
| `PUT /v1/sprites/{name}/fs/write` ([docs](https://docs.fly.io/sprites/api/filesystem/write-file)) | `tar c . \| vakna shell <box> -- tar x` |
| `client.sprite('my-sprite')` ([README](https://github.com/superfly/sprites-js)) | 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](https://docs.fly.io/sprites/concepts/lifecycle)).
- An HTTPS URL for every sprite, public if you choose, and `sprite proxy` for any TCP port ([docs](https://docs.fly.io/sprites/concepts/networking)).
- A persistent 100 GB volume per sprite ([docs](https://fly.io/sprites)).

## Where does Sprites do more?

- SDKs in JavaScript, Go, Python and Elixir, and adapters for agent frameworks ([docs](https://docs.fly.io/sprites/integrations/agent-sdks)).
- Compute billed only while a sprite is active ([docs](https://fly.io/sprites)).
- Managed services and connectors, and a remote MCP integration ([llms.txt](https://docs.fly.io/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](https://docs.fly.io/sprites/working-with-sprites)).
- A receipt for every command, with what it cost.