Any workspace can publish one file at an immutable path on its public HTTPS origin. Choose the public domain in Artifacts → Custom domain, then publish with an admin token or a publish-capable workload identity.
The CLI computes the SHA-256 before reservation, uploads the file once with a provider checksum and create-only condition, verifies the signed publication receipt, then checks the public object's size and immutable cache headers. Add --verify-download to download and hash the public object. Rerunning the same command recovers the same path when the bytes and media type match. A different file at that path fails with a conflict.
With managed storage, use the BoringCache address shown in Artifacts → Custom domain or enter your own domain. BoringCache configures the domain and HTTPS. For your own domain, copy the exact CNAME target shown in Artifacts → Custom domain and point your download domain's CNAME to it. The target identifies your Artifact storage; use the hostname without https:// or a path. Save your public HTTPS address, such as https://downloads.example.com, without a file path. Storage domain configuration must be confirmed before publication.
With BYOC, you manage the public domain, DNS, HTTPS and public-read policy with your provider. Keep Cache and private Artifact paths protected. BoringCache rejects publication paths inside those prefixes, but your provider controls which objects are public.
Artifacts → Storage shows locations retained by existing Artifacts and publications, including their bucket or container and saved public download address. Storage for new private uploads is configured separately. Existing publications retain their storage and URLs.
The public domain is the address people use to download published files. Private uploads do not become public when you save these settings. BoringCache stores each publication's exact URL; its domain cannot change after the first public path is reserved.
Published files are permanent, cannot be deleted through the Artifact API, use Cache-Control: public, max-age=31536000, immutable, no-transform, and may be at most 5 GiB.
Completing a publication under releases/<product>/<tag>/, such as releases/tool/v1.2.3/tool.tar.zst, creates its release group automatically. Product and tag names may each contain up to 128 characters. In Artifacts → Publications, workspace managers can edit the title and Markdown notes or create a group with another publication path prefix. Existing and future public files under that directory appear together. Publish each file with the same artifact publish command and a path under the prefix.
An unfinished upload reserves its public path. Retry publishing the same file to complete it. If the upload failed and its signed upload request has expired, a workspace manager can select Release public path in Artifacts → Settings. BoringCache releases the path only after checking that no object is stored there. Completed publications cannot be released.
Release groups organize the workspace view. Changing a group's tag, notes or prefix, or removing the group, does not change published files, download URLs or signed receipts. Use All files to find standalone publications. Notes support headings, lists, links and fenced code blocks; HTML and images are not rendered.