fota.systems

EEclipse hawkBit

The update server you run yourself — reached 1.0 in 2026, and it is the backend behind more products than its profile suggests.

OSS update serverAny (device-agnostic)By Eclipse FoundationSince 2015Open source: EPL-2.0
Type
OSS update server
How it works
A rollout and artifact management server, deliberately not a device agent. It handles targets, distribution sets, staged rollouts and reporting over a plain HTTP protocol; how the device applies the update, and whether it can roll back, is entirely your side of the contract.
Targets
Any (device-agnostic)
Deployment
Self-hosted
Rollback
None built in — the device client decides
Pricing*
Free
Free tier
Yes
Open source
EPL-2.0
Best for
Full control with no per-device fee
Notable
Reached production-ready 1.0 in 2026

* Published list pricing at August 2026 (vendor pricing pages, August 2026), not a quote.

Strengths

  • No per-device cost at any scale
  • Mature rollout and campaign model
  • Device-agnostic — pair it with any updater
  • Vendor-neutral Eclipse governance

Trade-offs

  • You operate it, back it up and secure it
  • No device agent — you supply the other half
  • No rollback logic of its own
  • Setup is a project, not an afternoon

Visit Eclipse hawkBit → Documentation

Listed for comparison as of August 2026 — not an endorsement, and Eclipse hawkBit did not pay for placement. See disclosure.

Compare Eclipse hawkBit with…

Eclipse hawkBit vs MenderEclipse hawkBit vs balenaEclipse hawkBit vs Memfault