Dashboard

Dashboard Overview

The dashboard is your central hub for monitoring and managing releases.

📊 Reading the Analytics

• Update Checks: The number of times a device has requested an update.
• Update Downloads: The number of times a device has successfully downloaded an update.
• Daily Active Devices (DAU): A count of unique devices that have interacted with the server on a given day.

Channels vs. Branches

The platform uses a tiered mental model for targeting updates to devices:

1. Devices: Talk to Channels (e.g., production, staging).
2. Channels: Point to Branches (e.g., main, release-v1.0).
3. Branches: Hold an append-only timeline of Updates.

By switching which Branch a Channel points to, you can instantly change which update all connected devices receive.

Performing Rollbacks

If you discover a critical bug in your latest update, you can perform an Instant Rollback.

How Rollbacks Work

A rollback is simply a special type of update entry that points back to the manifest of a previous, stable update.

• When you trigger a rollback from the dashboard, a new “rollback update” is appended to the branch’s timeline.
• Devices will see this “new” update and download it, effectively reverting to the older, stable state.

Important Note

Why you can’t rollback to a rollback: To prevent confusing update loops, you can only roll back to a “real” update (one that was published via the CLI).

🛡️ Smart Deletion

The system includes built-in protection against orphaning devices.

• Blocking Deletions: You cannot delete a channel if it is currently being used by active devices (tracked via analytics).
• This ensures that you don’t accidentally break the update path for your users.