One reviewed release.
Every paired X52.

The X52 master runs with open capabilities. Paired devices can discover the shared stable release and verify its signatures before offering an update.

1. Pair each device privately. The owner provisions its individual credential through the supported local setup. Never paste tokens, keys or customer information into this page.
2. Promote only reviewed releases. Build one candidate, retain actual device and data preservation evidence, sign its manifest and tested attestation, then promote that same candidate to stable.
3. Check from the X52. An update becomes available only when the paired service is reachable and the pinned release key verifies the candidate. Follow the device’s installation confirmation.

Missing pairing, an offline origin, or no stable release means updates are unavailable. Local open capabilities remain available.