Sandboxes for agents On your own hardware
Give each agent an isolated sandbox on hardware you control. Run it, pause it, snapshot it, or fork it into a copy, all through one API.
curl -fsSL https://useshards.com/install | sh A sandbox for every task
Set up a workspace once, then give every agent its own copy of it.
- 01Set up the workspace once.
- 02Forks carry over memory and files.
- 03Neither sees the other’s files.
- 04Nothing outlives the task.
Keys stay on the host
Agents need API keys and the network. The host decides what they get.
- Credential brokering
- The sandbox receives a placeholder. The host proxy adds the real secret to HTTPS request headers for approved destinations.
- Network egress control
- Set policies that allow or deny outbound requests. Private networks, cloud metadata included, are always blocked.
agentrunning
The whole lifecycle, one command each
The same commands on every runtime. One that can’t pause or fork says so, and never falls back.
shard runKeeps running after its command exits, until you stop it.
shard stop · startFiles stay. Processes start fresh.
shard snapshot createSaves a stopped sandbox’s files to start new ones from.
shard pause · resumeMemory is saved too. Processes pick up where they left off.
shard forkCopies a running sandbox, memory included. The source keeps going.
More commands
- shard exec
- Run a command in a running sandbox
- shard shell
- Open an interactive shell inside one
- shard cp
- Copy files between your machine and a sandbox
- shard logs
- Show output from the main command
- shard list
- List active sandboxes
- shard inspect
- Show the details of one sandbox
- shard secret
- Manage secrets and sandbox access to them
- shard policy
- Set outbound network rules and read network logs
- shard remove
- Remove sandboxes and their files
- shard capabilities
- Show which commands the runtime supports
- shard setup
- Configure a local host or a remote connection
- shard serve
- Serve the HTTP API with token authentication
Five runtimes, one API
- user-space kernelcatches system calls
- sandboxnamespaces · cgroups
- hostyour server · Linux kernel
- your Macto your server over HTTPS · API key
- guest kernelits own, per sandbox
- microVMhardware virtualization
- hostyour server · Linux kernel · KVM
- your Macto your server over HTTPS · API key
- guest kernelLinux, per sandbox
- Linux VMApple silicon
- hostyour Mac · macOS · Virtualization framework
- system containerDocker runs inside
- hostyour server · shared Linux kernel
- your Macto your server over HTTPS · API key
- containernamespaces · cgroups
- hostyour server · shared Linux kernel
- your Macto your server over HTTPS · API key
Questions
More in the docsIs it open source?
Yes. shard is licensed under Apache 2.0, and the CLI, the daemon and both SDKs live in one repository on GitHub.
How is it different from hosted sandboxes?
It runs on your own hardware. You control the infrastructure, the data, the access and the isolation, with no hosted service in between.
Do I need /dev/kvm or bare metal?
No. Without /dev/kvm, shard uses gVisor, which runs on an ordinary cloud VM. Only Firecracker needs it.
Where does it run?
On a Linux server on x86-64, or on an Apple silicon Mac with macOS 14 or later. On Windows, run it inside WSL 2.
Does every runtime support every command?
No. runc and Sysbox cannot pause, resume or fork, and say so instead of falling back. shard capabilities shows what a server supports.
How is it different from Docker?
Docker containers share the host kernel. shard adds user-space kernels and VMs, a pause that keeps memory on disk, forks of a running sandbox, egress control and credential brokering.
Your agent’s new home
Three commands from here to your first sandbox.
curl -fsSL https://useshards.com/install | sh $shard setup# inspects this host and installs a runtime
$shard create python:3.12# sudo on Linux
icy-river-7ae2