Automation / OTA
Nishad
🔶STUB — v-PROPOSED, fuller design to follow. This screen sketches the intent so no tile on Cortex Home is a dead door. Full canary-config and rollback-mechanics detail is a future REQ.

Automation / OTA

The platform's automation and update engine — how Cortex ships versioned vertical-pack + platform updates to every install: what's available, canary rollout status, and rollback. Distinct from Om Business's daily-brief automation feature.

Available updates 2 available

UpdateTargetVersionStatus
Om WMS vertical packOm Supply Chainv0.3.1AVAILABLE
Om Business operating suiteall installsv1.1.1CANARY
Cortex platform coreall installsv0.9.2ROLLED OUT

Rollout / canary status

Om Business v1.1.1 — canary group (1 of 4 installs)

25% rolled · 0 errors

Customer edits win over base-pack updates (vertical-packs + continuous OTA model). Full rollout after 48h clean canary.

Rollback

Cortex platform core v0.9.1 → v0.9.2 (rolled out 2026-07-22)

Rollback is a Tier-3 action — confirm + audit-logged; never deletes install data.

What's on this screen

Built from: the live rollout state of every versioned update Cortex is shipping to installs and vertical packs.

On screenWhere it comes fromWhat it means to you
Available updates listevery packaged update waiting to ship, or already shipping, to installssee what's about to change before it lands
Target (per update)which install or company that update is headed toknow who's affected by a given update
Update status (available / canary / rolled out)where that update is in its rollout — not started, limited test, or fully shippedjudge how much of the fleet is running the new version
Canary progress bar + error counthow many installs in the test group are on the new version and whether any brokedecide whether it's safe to keep rolling out or to hold
Rollbackthe last completed update, with a one-click revertundo a bad update quickly, without losing install data