KinuxOTA vs Eclipse hawkBit
hawkBit is the stronger choice when you want to self-host an update server and already have (or will build) the client side, typically SWUpdate or RAUC in your image. KinuxOTA is a complete hosted service with its own agent: nothing to run on a server, one command per device.
Eclipse hawkBit is an open-source back-end for rolling out software updates to devices; each device needs an update client such as SWUpdate or RAUC that talks to its API.
Side by side
| Aspect | KinuxOTA | Eclipse hawkBit |
|---|---|---|
| What it is | A web dashboard and a small agent for Linux devices: OTA updates of packages, files and scripts, remote commands and device health. | A back-end server (with a web UI and APIs) for rolling out software updates; no device agent of its own. |
| What runs on the device | The KinuxOTA agent, from a signed apt repository. | An update client you choose and integrate, e.g. SWUpdate, rauc-hawkbit-updater or your own, using hawkBit's device API. |
| Operating system on the device | The device's own Ubuntu, Debian or Raspberry Pi OS (amd64, arm64, armhf). No special image. | Any, as long as an update client for it exists. |
| What it updates | apt packages, any files with a script, the agent itself. Not full-system images yet. | Whatever the device client installs; with SWUpdate or RAUC, typically full-system images. |
| If an update breaks the device | No automatic rollback of a failed update yet (full-system A/B updates are planned). | Depends on the device client (SWUpdate and RAUC support A/B with rollback). |
| Rolling out | Runs on up to 100 chosen devices at once, offline devices catch up, re-run only the failed ones. No groups or phased rollouts yet. | Rollout management to groups of devices is its main purpose. |
| Hosting | Hosted service (EU). No self-hosted edition. | Self-hosted: a Java server with a SQL database (MySQL/MariaDB or PostgreSQL), also as a Docker image. |
| License and price | Free during the pilot program, up to 3 devices per account for now. | Open source (Eclipse Public License 2.0); you pay for your own servers. |
Choose Eclipse hawkBit when
- You must self-host and want an open-source server you can extend.
- Your devices already use SWUpdate or RAUC and you need rollouts to groups.
Choose KinuxOTA when
- You do not want to run and secure an update server.
- Your devices run a standard Ubuntu, Debian or Raspberry Pi OS and need package, file and script updates.
- You want remote commands, scripts and device health in the same place.
Try KinuxOTA on your own devices
Free during the pilot program (up to 3 devices per account for now). See which kinds of OTA update it does today.