The release path, organized as infrastructure.
Publish, deliver, present, and govern desktop releases in one system without handing over your signing identity.
A controlled handoff from CI.
Releases begins after the build. Create an app-scoped publish key, keep signing where it already happens, and let the upload Action move artifacts directly into release storage.
Scoped credentials
Issue and revoke publish-only keys for individual apps.
Release automation
Create drafts, upload artifacts, attach notes, and publish from GitHub Actions.
Artifact-aware ingestion
Record target, format, size, signature, and declared SHA-256 for each build.
One release, rendered for each updater.
The stored release stays framework-neutral. Declarative adapters turn it into the exact response the client expects, while edge delivery keeps the update path fast.
Tauri v2
Signed manifests and target-specific updater responses are available today.
Generic REST
A compact JSON contract for custom apps, CLIs, and updater clients.
Edge distribution
Cacheable checks and short-lived artifact links deliver binaries efficiently without exposing storage.
A public home for every app.
The release metadata that powers automatic updates also powers a human-facing download page, so direct distribution does not require a second publishing system.
Hosted download pages
Present the latest build with OS and architecture-aware artifact selection.
Release history
Show retained versions and their notes when the plan includes archive history.
Custom domains
Serve the download experience and update routes from a verified hostname.
Supported update protocols.
Choose a supported adapter with a documented response format for every release.
Tauri v2
Available
Signed updater responses and the production release flow are supported.
Generic REST
Available
A stable JSON release contract for custom clients is supported.
Electron
Not available
Electron auto-updater feeds are not currently supported.
Choose the product area you need first.
Start with one app and one release channel, then add history, domains, and organization controls as distribution grows.