Skip to content

Deliver private files and release artifacts

Distribute binaries, documents and other release assets with versioned paths and recipient-level access.

Create a Files registry

Open Registry → Registries and choose the Files format. Its shared host uses your registry slug in the URL; a verified custom domain uses the host directly. The signed-in Registry → Files → Setup page gives the exact upload and download commands for your registry.

Upload a version

Create a Files package, add a version, then upload individual files or a folder from its page. Paths within the version are preserved. You can also publish with curl -T and a publisher key, as shown on the setup page. A path already present must match the stored content digest.

Use channels such as latest to point a stable name at a version. Test the exact object path from a clean client before sharing it with recipients.

Give recipients access

Issue a separate read-only download key for each customer or integration. They can fetch with curl or wget using the setup-page URL and their key. A version page can also issue a short-lived link for one object. A key or link does not grant permission to upload.

Rotate or revoke a key when a recipient leaves. Use the customer portal when recipients should manage their own keys, and download activity when reviewing distribution.

READY WHEN YOU ARE

Put private packages to work.

Start 30-day trial