Spin Up A Claude Code Sandbox in Less Than a Second
Every Sprite is a hardware-isolated Claude Code sandbox with Claude Code preinstalled and ready to go. Sprites spin up with a comprehensive llm.txt file and prebuilt Claude Skills that let Claude understand and control its environment out of the box. No configuration or training required.
create, like, 500 Sprites for free
curl https://sprites.dev/install.sh | bash
sprite login
sprite create my-sprite
claude
Stateful environment
Sprites are fully mutable and persistent between runs. Your data lives on a boring, ext4 filesystem. It's available when your Sprite runs.
Unlimited checkpoints
Write files, install packages, build sqlite databases. Change whatever you need. When you're happy, checkpoint. When you're not, restore.
Granular billing
Sprites come up fast, have a bunch of CPU and RAM available, and run as long as they need to. You pay only for the resources you use.
HTTP Access
Each Sprite has a unique URL. Share what you're building in public, hook up webhooks, serve APIs. If it's HTTP you can do it.
- Disposable Compute
- Sprites get VMs when they need them. Fire one up, do some work, forget about it for 6 months. We make sure it gets compute when you come back.
- Firecracker VMs
- Sprites execute code in Firecracker VMs. Even we have a hard time seeing what they're doing.
- Isolated Networking
- VMs run on isolated networks. Nothing can connect to your Sprite directly.
- Dynamic Resources
- Sprite VMs have access to big chunks of CPU and Memory. Your blobs of code just use what they need, up to 8 CPUs and 16GB of RAM for any given run.
Billing
You pay only for Storage and compute resources while a Sprite is active. Usage is aggregated across your organization.
CPU Time
Minimum 0.0625 CPU while running.
Memory Time
Minimum 256MB RAM while running.
Storage
Prorated to the hour. 1,000 sprites using 10MB data = 10GB total.
All compute resources are billed per second. Storage is billed hourly but aggregated monthly.