Deployments

Deployments give you a stateful workflow for pushing changes across many endpoints with control over pace, risk, and observability — and installers built so those changes actually land.

Rollout Strategies

Breeze supports immediate and staggered rollout modes. Immediate is for urgent, low-risk tasks. Staggered uses batch-based progression so teams can validate early impact before full-fleet execution.

Targeting Model

Deployments target explicit devices, device groups, filter expressions, or all devices in scope. Target resolution happens as part of the deployment lifecycle, so execution intent is explicit and auditable.

Control Loop

Operators can initialize, start, pause, resume, cancel, and retry deployments. Failure thresholds and retry settings provide guardrails for large rollouts where partial failure is expected — so a bad cohort stops the rollout instead of taking the fleet with it.

Visibility and Diagnostics

Each deployment includes aggregate progress and per-device records. That makes it easy to isolate failing cohorts, inspect error patterns, and decide whether to continue or stop without leaving the deployment view.

Installer Reliability

A deployment is only as good as the installer behind it. Breeze treats the installer path as a first-class part of the release pipeline:

• macOS uses a native Swift GUI installer with bootstrap tokens. Onboarding a Mac feels like installing any other native app — no scripted enrollment, no terminal.
• Windows MSI installs run through a hardened folder-permissions path so clean installs finish without rollback and the intended ACLs are applied. No more half-installed agents from a generic installer error.
• Release verification combines Developer ID signature checks with Apple notarization on macOS, and the publish pipeline fails closed if notarization rejects an artifact or required assets are missing — a partial upload can’t ship silently.

Schema and Upgrade Safety

Fresh installs apply database migrations in the correct order regardless of when each migration was authored, so a clean install lands in the same state as an incrementally upgraded one. New deployments don’t need manual reconciliation to match older environments.

Why Teams Use It

Deployments turn ad-hoc bulk actions into traceable, controllable rollout workflows — and the installer and release pipeline behind them are built so the rollout itself is the same experience every time, on every platform.