@blindcast/crypto, @blindcast/keys, @blindcast/storage, @blindcast/player), this page maps your existing code to the new tools.
Package → deliverable mapping
Do I need to change my code?
If you use@blindcast/player: No changes. The package and API are the same. Only the docs location moved.
If you use @blindcast/storage in Node.js scripts: Consider switching to the CLI for simpler workflows. Your existing code still works — @blindcast/storage is not deprecated — but the CLI handles encryption, upload, and manifest rewriting in one command.
If you use @blindcast/storage in the browser: Consider switching to @blindcast/uploader for a simpler API. Your existing createUploader + createBrowserTransport code still works.
If you run your own Express key server: Consider switching to the Docker image for less boilerplate. Your existing Express code still works — @blindcast/keys/express is not deprecated.
If you use createWorkerKeyServer: No changes needed. The Worker API is unchanged.
The packages are not deprecated
All existing packages (@blindcast/crypto, @blindcast/keys, @blindcast/storage, @blindcast/player) continue to work and receive updates. The new tools (CLI, Uploader, Key Server Docker) are built on top of them.
The documentation now focuses on the higher-level tools because they cover the most common workflows with less code. If you need lower-level control, the packages are still available.