Skip to main content

Deployments

Ship a new software version to the right devices, watch it roll out, and know it landed. Deployments in Avocado Connect orchestrate OTA updates across your fleet, targeting a versioned software artifact (a Runtime) published to your project.

Connect builds on the atomic update architecture in Avocado OS: updates apply to A/B partitions and roll back automatically if a boot fails, so a bad update can't brick a device.

Every runtime is cryptographically signed, and each device verifies that signature before it installs anything, so a device only ever applies software your organization actually published. Connect builds this on The Update Framework (TUF), the industry standard for securing software distribution, and it works out of the box: signing is set up when your organization is created, with no key ceremony to run yourself.

A Runtime is the versioned artifact you deploy. Publish runtimes to your project, assign them to cohorts, and deploy or deprecate them from one place.

The Runtimes tab: published software versions with their status, target cohorts, and deploy or deprecate actions.

Creating a deployment is a short form: name it, pick the runtime and cohort, and optionally target specific devices or filter by tag under advanced options.

The New Deployment form: name, runtime, and cohort selection with advanced options to target specific devices or filter by tag.
  • Staged rollouts: Promote a release through cohorts, for example canary before production, and optionally target specific devices or devices by tag. Convergence tracking reports on-target percentage, pending devices, and stale device counts so you can see exactly how far a rollout has progressed before promoting it further.
  • Cohort and tag targeting: Push updates to specific device groups: update a factory pilot line without touching production, or roll out to one region first. Tag and specific-device targeting let you reach exactly the devices you mean.
  • Delta updates: Avocado OS and its update agent transmit only the changed bytes rather than a full image, which Connect builds on. This is critical over metered cellular or satellite links. See atomic updates for how the underlying mechanism works.
  • Audit trail: Every deployment records what was deployed, when, to which devices, and the outcome, giving you a complete history of how your fleet reached its current state.
A deployment rollout in progress: convergence tracking with on-target, pending, and stale counts, plus per-device update status.