Seats, devices, and minimums: how our licences actually work
Every companion licence answers the same three questions: what is counted, what is the floor, and what happens when the year ends. The model in plain terms, with real numbers.
Concrete decisions from building the Check apps, what we chose, what we rejected, and where the limits sit. Not a marketing calendar.
Every companion licence answers the same three questions: what is counted, what is the floor, and what happens when the year ends. The model in plain terms, with real numbers.
"The guard was there" can be proven several ways, and they are not equal. TourCheck supports five capture methods, each with a different strength of evidence and a different way it can fail. Here is what each one actually proves.
Every time-tracking vendor claims "compliance". Here is what that actually looks like in code: statutory break tiers as the floor, organisation policy as a second layer, personal working-time models for the contract that fits nobody's template, and an explicit line we will not cross into legal advice.
A care worker documents a visit in a basement flat with no signal. A kiosk terminal stamps while the site Wi-Fi is down. What happens to those records, encrypted outboxes, server-side idempotent replay, and the 24-72 hour skew window, is the difference between a feature and a slogan.
Why we ship a suite of small Nextcloud apps instead of one platform: each app stands alone, siblings only connect when you install both, and a custom absence type invented in ArbeitszeitCheck still blocks the roster in DutyCheck.
The question behind most "should we self-host" debates is really "what does it take." Here is the shopping list for a team of five to fifty, hardware, skills, and the recurring work nobody mentions in the brochure.
In late October, ArbeitszeitCheck shipped five releases in ten days. That cadence is the answer to "how does a team this small ship this much", so here's what that stretch actually looked like, mechanics included, because the polished version would skip everything that makes it true.
"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.
A guard-tour log is only worth something in the dispute, the insurance claim, the incident review, the "prove the night round happened." If the database is the only evidence, whoever can edit the database decides what happened. TourCheck's answer is a journal that makes tampering visible instead of impossible.
Every offline-capable app eventually answers the same question: what happens when the user taps "send" twice, or the network dies mid-request and the client retries? The answer is a small mechanism called an idempotency key, here is how it works, and how it looks in our own code.
Every product page tells you what the software does. This is the other list: real requests we evaluated, priced, and refused, with the reasoning left in the decision docs where you can read it.
12:07, a construction site gate, no bars. The worker clocks in anyway. Here is everything that stamp goes through before it lands in the timesheet, and where it could have gone wrong.
The person who set up your Nextcloud gave notice, or simply stopped answering. The good news first: your data is fine. The server still runs, the apps still work, and nothing is held hostage. Here is what actually needs doing, in order.
A time tracker needs a database. But does it need a new cloud for that? Why we built ArbeitszeitCheck directly as a Nextcloud app, existing users and groups, working-time data on the organisation's server, IT administration keeps control.
The working hours are recorded, and yet the real work starts at month-end. On missing entries, open requests, overtime and payroll exports, and why good software must relieve administration too.
Another tool, another login, another password. Sometimes good user experience starts one step earlier: with the question of whether we need a new application at all.
Payroll offices ask for "the DATEV file" as if it were a single thing. It is not. Here is the file ArbeitszeitCheck produces, byte for byte, and what your payroll office still has to do with it.
Nobody evaluates software by asking "what does it do when something goes wrong later." The question on every demo is what it does on an ordinary Tuesday. Fair enough, but the Tuesday features are all table stakes, and it's the boring recordkeeping underneath that decides how the uncomfortable meeting goes.
Every comparison page on this site argues why you should pick our apps. This one documents how to leave them, because "what happens to my data if I go" comes up on every call, and the answer should be public, not a promise in an email.
That question arrives in some form on most sales conversations. Sometimes politely, "help me understand the licensing model", sometimes as a challenge: the app is AGPL and free, so charging €8 a year for the mobile app looks like a contradiction, or worse, a trick.
Last month a quote request came in that ended with a line I keep thinking about: "Your app is free and Clockify costs us about €90 a month. What's the catch?"
Release countdowns, thought-leadership pieces, or posts written to fill a gap in the calendar. When a new post is worth your time, it appears on this page and in the News section. If you want release-by-release facts instead, the release notes are generated straight from the changelogs.