Skip to main content
Firmware management in firmngin tracks what version is available, which devices should receive it, and how rollout progress is observed. Open Dashboard → Firmware to manage artifacts and workflow runs.

​
Dashboard views

​
Firmware concepts

​
Artifact versus policy

Keep firmware artifacts separate from rollout policies.
  • Artifact upload answers: “What binary can be installed?”
  • Rollout policy answers: “Which devices should receive it, when, and under what constraints?”
This separation matters because manual upload, CI/CD upload, and fleet rollout governance do not share the same permissions or review process.

​
Release workflow

  1. Build firmware from a trusted source.
  2. Upload or register the artifact under Artifacts.
  3. Attach or verify OTA policy on the target device template.
  4. Deploy to a device template (fleet) or selected devices (test).
  5. Approve the rollout if policy requires it.
  6. Monitor Workflow runs — fleet %, stages, and device logs.
  7. Expand through staged percents or pause/abort if health checks fail.
For large fleets, deploy via device template so firmngin orchestrates multi-wave rollout automatically. See Fleet rollout.

​
CI/CD path

Automate build and upload with GitHub Actions and the firmngin/ota action. Generate a scoped token from Dashboard → Integrations (scope: Firmware OTA). Do not share dashboard credentials in CI. Use a dedicated API token with the minimum required scope.