Eclipse hawkBit 0.2.0 Release Review

End Date of the Review Period

Reviews run for a minimum of one week. The outcome of the review is decided on this date. This is the last day to make comments or ask questions about this review.




First Eclipse hawkBit release including:

  • Core features:
    • Device and Software Repository 
    • Update Management Management UI/Console
    • Artifact Content Delivery
    • Rollout/Campaign Management
  • Interfaces:
    • Management API
    • Direct Device Integration (DDI) API
    • Device Management Federation (DMF) API
API Certification

The project leadership certifies that the APIs in this release are "Eclipse Quality".

Architectural Issues

hawkBit is basically architectural debt free. Especially the component model and the internal APIs have been refactored for this release.

There are a few issues open though:

  • hawkBit is not yet Java >=9 compatible.
  • hawkBit security model/configuration is pretty complicated to adapt to users needs (its all or nothing basically).
  • Certificate based authentication for devices is unnecessarly complicated to get running. The code needs a major refactoring here.
  • DMF authentication API is a leftover from before the initial contribution and should be removed.
Security Issues

There are no security issues known at the time of this writing.

Non-Code Aspects

The project provides:

Conforms To UI/UX Guidelines
Not applicable (project doesn't provide UI)
Usability Details

hawkBit provides a Web UI including usability features like push and drag and drop support.

The user interface guidelines do not apply as the the hawkBit web UI is not based on the Eclipse workbench/IDE.

End of Life

Since this is the first release of hawkBit, there are no deprecated or removed features (yet).


hawkBit does not support any particular standards. APIs and interfaces are based on HTTP and AMQP 0.9.


The hawkBit team is attracting users, adopters and contributors using arbitrary channels.

  • On GitHub ( users can create issues for questions, bugs and enhancements and provide pull requests for improving hawkBit.
  • The hakBit team itself discusses all changes through gitHub pull requests
  • Some of the committers are speaking at conferences, publishing blog entries and/or articles.
  • The team has also done a two screencasts on the Eclipse IoT Meetup group.
  • The team maintains a gitter chat room, where questions from the communities are answered and discussed.