Keep a model forever. Run it tomorrow.
Website · Getting started · Documentation · Learn the field
darsay preserves models, datasets, and source repositories as pinned, checksummed bundles in a vault you control. Published files retain their formats, with licenses, provenance, and verification evidence recorded beside them. Supported models run offline in isolated environments.
These are foundations for the north star: help engineers own an AI development loop by connecting existing tools through removable project metadata. General loop orchestration is proposed; training, evaluation, and infrastructure keep their native interfaces.
A vault holds archives and curated collections. Browse everything on disk or open a collection to choose files, set priorities, and coordinate work. The browser interface is shared with darsay.io boards; reported progress stays separate from the vault's archive inventory.
Install
Python 3.10+ on macOS or Linux:
pipx install darsay
# or
uv tool install darsay
Try the CLI without a permanent install with uvx darsay --help.
Installation and upgrades covers
Homebrew and other installation paths.
Quick start
darsay estimate Qwen/Qwen3-0.6B
darsay archive Qwen/Qwen3-0.6B
darsay run qwen--qwen3-0.6b "Say hello"
The default vault is ~/darsay; use --vault /path/to/vault to choose another.
Interrupted archives resume with the same command. The first run prepares its
runtime environment; inference then uses the archived files offline.
The guided first bundle explains each step.
Browse an existing vault:
darsay --vault ~/darsay serve --open
Open the private launch URL and use All archives or a named collection. The vault UI guide covers local operation, read-only browsing, collection exports, and agents.
Documentation
The full guides and reference live at darsay.io/docs.
| You want to… | Read |
|---|---|
| Understand vaults, bundles, and collections | Concepts |
| Find a command or workflow | Examples |
| Curate and coordinate a collection | Catalogs · Boards and agents |
| Resume, move, or back up archives | Incremental transfer · FAQ |
| Understand and run a model | Learn the field · Hydration |
| Recover an archive independently of darsay | Manifest · MVB format |
The CLI documentation's source remains in docs/ and
examples/, available offline with this repository.
For development, see Contributing; for changes, see
the changelog.
License
Apache License 2.0. Archived works retain their own upstream licenses, recorded separately in each bundle's manifest.
1 maintainer
Metadata
1 maintainer
Release files for darsay 0.16.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| darsay-0.16.4.tar.gz | 3.6 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| darsay-0.16.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.6 MB
Release files / darsay-0.16.4.tar.gz
| Download URL | darsay-0.16.4.tar.gz |
|---|---|
| Size | 3.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5a8cbd4b07a97295dda42be97327e5a251cbf1e3f66391e0aeec177352ed26de
|
|
BLAKE2b-256 checksum How to use checksums |
e530ea4dac56686e45885999057b68ffef65e3a99a7f08c4fcb1aa5a66a87976
|
| 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 Sep 12, 2026.
Transparency logRelease files / darsay-0.16.4-py3-none-any.whl
| Download URL | darsay-0.16.4-py3-none-any.whl |
|---|---|
| Size | 922.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3ff5540d794d4705c6b75ef3f64ef83cbe89b6c2e4de0d7fff4e66fcd7d571d2
|
|
BLAKE2b-256 checksum How to use checksums |
f6f9cc4a0fd9efc8a4c718fb252a57378894b4daa8aa9c9bea7cfdd9fc82bf8d
|
| 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 Sep 12, 2026.
Transparency log
