Release With Hugging Bay
Launch open AI models on Hugging Bay with namespace claims, release manifests, cross-source provenance, signed trust bundles, scan status, hashes, runtime notes, and reviewed fallback distribution.
Open model releases should be easy for humans to inspect and easy for agents to cite: namespace claim, public source provenance, license clarity, file hashes, signed manifests, scan status, runtime notes, and optional reviewed fallback distribution.
Release flow
- Claim a lab or creator namespace: Approved publisher namespace and scoped publisher token. web api
- Submit a draft release: Draft artifact row with license, provenance, model card, runtime metadata, and file hashes. web api
- Copy a release manifest template: Starter JSON for source URLs, hashes, runtime notes, cross-source evidence, and optional reviewed fallback metadata. web api
- Upload files or attach a large upload manifest: Content-addressed files or an upload session ready for release checks. web api
- Run release checks: Scan, license, provenance, manifest, hash, and metadata readiness status. api
- Publish after checks pass: Public artifact page, file list, signed manifest, and trust bundle when hosted files exist. api
- Share the launch page: Human and agent-readable release page with source links, run guidance, and trust signals. web api
- Expose a signed trust bundle: Machine-readable SHA-256 hashes, signatures, provenance, license, files, and source metadata. api
- Add optional reviewed magnet/torrent fallback metadata: Peer-assisted fallback metadata only after public visibility, license, hash, provenance, scan, and reviewer evidence pass. api
Trust badges
- Claimed namespace: The lab or creator controls an approved Hugging Bay publisher namespace.
- Matches upstream: Hashes, source URLs, and metadata align with the official upstream release.
- Signed manifest: Hosted files are represented in a signed Hugging Bay manifest.
- Scan passed: File and metadata checks did not find a blocking safety issue. Large files are scanned via head and tail sample windows (coverage is reported per artifact as scanCoverage: full or sampled), plus full-file SHA-256 hashing.
- Reviewed fallback: Magnet/torrent metadata was reviewed before publication.
- Community run verified: Users or reviewers reported successful local/runtime use.
Reviewed fallback policy
Hugging Bay may list reviewed magnet metadata as a fallback. It does not publish unreviewed links and does not use peer distribution to bypass upstream gates.
- public artifact visibility
- redistributable license
- source provenance
- reviewer evidence
- scan not blocked
- hash or info-hash present
Launch kit JSON Publisher workflow JSON Apply to publish Submit release
Open interactive launch kit