Verdel documentation
Everything you need to publish a release, control who receives it and verify what arrives. Current versions: CLI 4.12.1, agent 4.12.1, Manifest API v1.8, delta format 3.
QuickstartInstall the CLI, push a build and see a device update in about 40 minutes.
Manifest APICheck for updates, list releases, assign devices to rings. Request and response shapes.
Staged rolloutsRings, hold times, halt thresholds and what happens when a release is stopped.
Delta updatesHow tiles work, when a device falls back to a full installer, and how to measure savings.
Signing keysRoot, targets and timestamp roles, rotation, and hardware-backed signing.
Release notesWhat changed in the platform, agent and API, by date.
Choose a path
| You are | Start with | Typical time |
|---|---|---|
| Moving from a self-hosted update feed | Quickstart, then import your feed with verdel import | half a day |
| Building your own updater | Manifest API and Signing keys | 1 to 3 days |
| Running releases for a large fleet | Staged rollouts | 1 hour |
| Trying to reduce delivery cost | Delta updates | 30 minutes |
Limits at a glance
- Largest single artifact: 2 GB on Pilot, 8 GB on Studio, 32 GB on Fleet, 128 GB on Enterprise.
- Manifest API rate limit: 600 requests per minute per device identifier, 6,000 per minute per workspace on Studio, 120,000 per minute on Fleet.
- Signed download URLs expire after 15 minutes by default and can be set between 1 minute and 24 hours.
- Release history is kept for 30 days on Pilot, one year on Studio and three years on Fleet.
Cannot find something? Search the changelog for the version that introduced it, or write to support.