useshards
The Python SDK for shard, the sandbox manager. Create
sandboxes on a shard host, run commands and processes in them, move files, forward ports, and
snapshot, fork or pause them. Shard is for blocking code and AsyncShard is for asyncio. Both
have the same verbs.
Docs · TypeScript SDK · Changelog
Install
pip install useshards
Connect
Point the SDK at your shard server and its API key:
export SHARD_REMOTE=https://shard.example.com
export SHARD_API_KEY=<the API key>
Or pass them in code: Shard(remote=..., api_key=...). No server yet? Connect to a remote host sets one up and
gives you the key.
Quickstart
from useshards import Shard
with Shard() as shard:
sandbox = shard.create("docker.io/library/alpine:3")
result = sandbox.exec(["uname", "-sr"])
print(result.exit_code, result.stdout)
sandbox.files.write("/tmp/hello.txt", "hello\n")
print(sandbox.exec("cat /tmp/hello.txt").stdout)
sandbox.remove(force=True)
Docs
The Python SDK docs cover the rest: sandboxes, commands, processes, files, ports, secrets, policies, snapshots, asyncio and errors.
License
Apache-2.0.
Metadata
Release files for useshards 0.1.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| useshards-0.1.6.tar.gz | 79.6 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| useshards-0.1.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 257.6 kB
Release files / useshards-0.1.6.tar.gz
| Download URL | useshards-0.1.6.tar.gz |
|---|---|
| Size | 79.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5c7f819c605430eb3fb61df080d77f9d40fdc6a029555e0a141e64aa88038aad
|
|
BLAKE2b-256 checksum How to use checksums |
1f4c53a8db7cf1d5d6779e2e89fac6be1f0d43784d3dbcb2b0c2907239265d0d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.
Transparency logRelease files / useshards-0.1.6-py3-none-any.whl
| Download URL | useshards-0.1.6-py3-none-any.whl |
|---|---|
| Size | 178.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
07c35ee0d615fb8db3a4eb92d3df4ab1ec44fa12fcaf912e0042f62096f399a0
|
|
BLAKE2b-256 checksum How to use checksums |
2efdf70b9e6ed403d309398e9422057394da73a484c9b58c30abe59dd362fbed
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.
Transparency logSecurity for useshards 0.1.6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for useshards-0.1.6.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.