Distributing software to your customers

Distributing software to customers is different from sharing it internally. The people downloading your packages have no Cloudsmith account, you need to control what each of them can access, and the experience should look like part of your product rather than part of ours.

This guide steps through the features that make that possible, in the order you would usually set them up. Each step links to the detailed documentation for that topic.

Step 1: understand entitlement tokens

Entitlement tokens grant read-only access to a repository's contents without requiring the recipient to have a Cloudsmith account, which makes them the foundation of external distribution.

Step 2: create and manage your tokens

Issue a token per customer so you can track their downloads, apply usage restrictions, and revoke access independently of everyone else.

Step 3: require acceptance of your license terms

EULA enforcement makes users accept your End-User License Agreement, tracked by revision, before downloading Raw files. EULA enforcement for entitlement-token downloads in any package format is in Early Access.

Step 4: restrict access by location

Geo/IP rules allow or deny downloads by country, IP range, or individual address, which is often needed for export control or contractual reasons.

Step 5: serve packages from your own domain

Custom domains present your company domain as the download endpoint, so package URLs and installation instructions carry your branding instead of ours.

Step 6: give customers a download page

A broadcast is a public-facing, branded page your customers can use to find and download releases, rather than you sending out raw URLs.

Updated 3 minutes ago