This page introduces the release cycle and versioning approach used in Aidbox development

Aidbox release cycle

Aidbox docker images are available on Docker Hub.


The most recent Aidbox build. We highly recommend using the edge channel in staging and dev environments to get access to new functionality and detect potential issues as soon as possible. Every commit into the Aidbox code base after successful CI is published to the edge channel. The edge channel may have issues and/or regressions.


Latest releases contain new functionality, bugfixes, and optimizations and passed all available QA and review processes by the Health Samurai team. If you're actively developing we recommend using latest. These releases are updated monthly.


Stable releases are ready for production. The current stable is the previous latest release. These releases are updated monthly.

Tagged releases

For every :stable release, we also create a tag in the format YYMM (for example it will be 2107 for the 2021 July release) if you want to check out to a specific Aidbox version.

Long-term support releases

Starting in January 2022 we are introducing long-term support releases. The Aidbox team will backport security and critical bug fixes to LTS releases throughout a one-year support window.
Aidbox LTS releases are scheduled to be published twice a year. If you are not interested in getting new features on a monthly basis but want to get critical bug fixes, please consider switching to LTS releases.
Aidbox version
Availability starts
End of life

LTS changelog

Aidbox version
Fixed security issues in Search API.
Fixed critical issue on subscriptions in DB transaction that can break DB connection.