Updater API
Framework-shaped manifests, cached close to every client.
A release becomes more than a file.
Download pages
Hosted distribution with platform-aware artifact selection.
Public API
The same release metadata for sites and integrations.
From signed build to installed update.
Releases fits after your build. Your existing CI signs the artifact; the platform handles ingestion, delivery, manifests, and the public download surface.
- 01
Keep signing in CI
Private signing keys stay in your workflow. Releases receives the signed artifact and its signature.
- 02
Publish once
The GitHub Action creates the release, uploads directly to object storage, and publishes the channel.
- 03
Serve the right contract
Tauri v2 and Generic REST adapters render the response each client expects.
- 04
Verify on the client
The app verifies the publisher signature against the public key compiled into the client.
The infrastructure around every release.
A focused product, organized like a platform: each area solves a distinct part of operating desktop distribution.
Publish
Scoped keys, direct artifact uploads, CI automation, drafts, channels, and release notes.
Deliver
Edge-cached update checks, signed downloads, framework adapters, and custom hostnames.
Present
Hosted download pages, OS-aware artifact selection, history, and white-label options.
Govern
Organization access, retention policies, quotas, usage metering, and operational alerts.
Distribution without taking custody of trust.
Releases stores and serves your signature, but never needs the private key that created it. Integrity remains anchored between your CI and your app.
Private keys remain in your signing environment
Every artifact records its declared SHA-256
Downloads use short-lived signed storage URLs
Organization and app boundaries are enforced server-side
Read the security modelBuild the release path once.
Create an app, connect CI, and publish your first signed release.