Explainer · Licensing
What AGPL actually lets you do with our apps
"The web apps are AGPL" sits on every product page and is the sentence we get the most questions about. Here is what it concretely permits, what it does not, and the one clause people consistently misunderstand.
What you may do, today, without asking us
AGPL-3.0-or-later, the licence in every app's info.xml, permits more than most buyers expect:
- Install it on as many servers as you run, for as many users as you have. There is no seat count in the licence and no activation server to phone home.
- Read the source, all of it, including the parts a commercial vendor would call trade secrets.
- Modify it for your own use: translate a string, change a workflow, fork the whole app. Internal modifications are yours.
- Use it commercially. AGPL does not care that you make money with the software; your accounting department can run ArbeitszeitCheck for a thousand employees without paying us a cent.
- Redistribute it, modified or not, under the same licence, with source.
The clause people get wrong
The "A" in AGPL is the network clause: if you modify the app and offer it to users over a network, including to your own employees, you must offer those users the source of your modified version. This is the difference from plain GPL, which only triggers on distribution of copies. For a company that modifies the app for internal use this simply means: publish your diff, or offer it on request. For a hosting company that wanted to resell our apps as a managed service with secret improvements, it means those improvements stop being secret. That asymmetry is exactly why the licence was written.
What it does not do
It does not make our paid companion licences free. The mobile apps are separate products under separate terms; AGPL covers the server apps' code, not our store listings. It does not give you our brand, the names and logo are not licensed content. And it does not come with a warranty, a support contract, or an SLA, those are what Check Partner sells, explicitly and separately.
Why we chose it
Three reasons, in order of honesty. First, our customers are the kind of organisations that must be able to audit software handling working-time and patrol data, a licence that guarantees source access is a feature they verify, not a posture we signal. Second, the network clause protects the business model: a cloud provider cannot quietly repackage our work into a competing service. Third, it keeps the exit honest, if we ever abandon an app, the community can keep it alive, and your organisation's data was never in our hands to begin with. The licence is the architecture, stated legally.