This website has been mostly translated automatically from the original version. We apologize for any translation errors.

Contribute to the open source development of Kiebitz

We are happy about contributions to Kiebitz. To ensure that they can be used in a legally compliant manner, we ask all contributors who make substantial changes to sign an appropriate license agreement. These have been created using the Harmony Agreements templates used for open source projects worldwide.

Please send the signed license agreement to

Kiebitz context and history

Kiebitz was originally developed by KIProtect as a commissioned work for the team of, through the mediation of the Innovation Network Public Health (InöG). The core idea was the creation of a decentralized, privacy-friendly platform for vaccination appointments. Initial ideas were developed by Lilith Wittmann and Bianca Kastl, among others (concept on Github), a detailed concept was subsequently developed by KIProtect and implemented without the involvement of InöG. This concept was adapted and expanded in essential points during operation to make the mediation of vaccination appointments even more robust and reliable.

For the development of the original Kiebitz version, KIProtect contributed its own proprietary code to the software in many places and made it available to the general public as open source. This contribution was necessary to enable the development of the system in the short implementation time (only two weeks from project start to productive use). The condition for the contribution on the part of KIProtect was the publication of the entire software under an open source license.

In order to ensure that KIProtect can use the contributed, self-created code in its own products and for further developments of the software at its own expense in a legally secure manner, it is necessary due to the selected A-GPL license that contributors sign a license agreement. Code that is contributed under such an agreement will always be available to the public as open source code and can be used by KIProtect in a legally secure way. Conversely, KIProtect makes self-developed code freely available to the public as open source in a legally secure manner.

People and organizations that do not want to grant KIProtect such a right of use can contribute to the services-inoeg, apps-inoeg and vanellus-inoeg repositories without CLA. Code from the services, apps and vanellus repositories can also be contributed (downstream), but conversely no code can be contributed to these repositories (upstream) in order to avoid the licensing problems explained above.

In any case, KIProtect will continue to make code developed at its own expense available to the general public as open source.