Skip to content
AUTO/PILOT
Sign inCreate account

Downloads & updates

How build downloads are gated, and what happens during an update check.

Downloads

Installers live in private object storage. Nothing is publicly listable and no URL is permanent. When you click download:

  1. The server confirms your session and that your account holds a license.
  2. It signs a URL valid for a few minutes.
  3. Your browser is redirected to it.

Old links stop working when they expire. Generate a fresh one instead of bookmarking.

Update checks

An update check is the second — and last — moment the desktop app talks to the server. It does two things in one round trip:

  1. Refreshes the license token (see licensing & offline behaviour).
  2. Asks for the newest build on your channel.
GET /api/v1/builds/latest?platform=mac&channel=stable
Authorization: Bearer <session token>

The response carries the version, size, SHA-256, changelog and a short-lived download URL. Verify the hash before installing — the app does this automatically.

Choosing a channel

Run stable on any machine that goes to a gig. Keep beta on a second machine if you want to help test. Nightly is for people who enjoy finding bugs; never take one to a venue.

Switching channels is just downloading a different build. Your license covers all of them.

Update etiquette before a gig

  • Update at home, not at the venue.
  • Run a full set through the new build before trusting it live.
  • Keep the previous installer on a USB stick. Rolling back is faster than debugging at 10pm.
  • Remember that an update check needs a network. If you are updating in the booth, you are also refreshing your license — which is fine, but do it before doors, not during.