Riven Relay
LiveThe download and artifact service — installers, SDKs, model weights, and exports served from Riven-controlled infrastructure.
Relay serves anything a user or machine downloads from Riven: desktop installers, SDK bundles, model weights for the on-prem fleet, generated exports, and release artifacts. It is the answer to "where does this file come from" — a Riven-controlled origin rather than a third-party bucket.
Relay is the downloads service and is distinct from Bifrost. They are separate components with separate responsibilities; do not treat Relay documentation as describing Bifrost or the reverse.
What it serves#
| Artifact | Audience | Access |
|---|---|---|
| Desktop and CLI installers | End users | Public, versioned |
| SDK bundles | Developers | Public, versioned |
| Model weights | On-prem fleet nodes | Authenticated, pinned by digest |
| Generated exports | Account owners | Signed, short-lived URLs |
| Container images | Platform operators | Internal only |
Integrity#
- Every artifact is content-addressed and published with a digest; clients verify before installing.
- Versions are immutable — a published version is never replaced, only superseded.
- Weight pulls for the on-prem fleet are pinned by digest so a node cannot be silently moved to different weights.
- Download events are recorded in Riven Telemetry for capacity and integrity auditing.
Signed URLs for private artifacts#
Account-scoped downloads — data exports, rendered Deliverables — are issued as short-lived signed URLs. The signing key lives in Riven Keymaster, and the URL grants access to exactly one artifact for a bounded window.
Relay sits behind Riven Edge Proxy like every other surface, so TLS termination and routing are handled by Traefik on the same Docker Swarm cluster.