Klacks schedules shifts automatically, optimises routes and can be controlled through an AI assistant — installed at your site, open source, with the AI model of your choice, optionally hosted locally.
No license fees under the AGPL.
Plan a week - Video 1 of 2
Note on the sample data: All names, places (for example Winterthur), addresses and figures in these recordings are fictitious demo data with a Swiss background, written in Latin script. They only illustrate the product – you do not need to know or be able to read them. In your own installation you enter your own data, and the interface is multilingual.
One platform, many industries: Wherever staff are scheduled in shifts, in the field, and by qualification — Klacks adapts to you, not the other way around.
You quickly assign a colleague who worked a late shift until 10 p.m. yesterday. Klacks flags it immediately: rest period too short — 9 hours instead of the configured 11. You see the problem before the schedule goes out, not only when someone works it out afterwards.
Watch in the video: rest period too shortShort videos from the running app, sorted by topic. Choose a chapter; only the video of the open chapter ever plays.
Note on the sample data: All names, places (for example Winterthur), addresses and figures in these recordings are fictitious demo data with a Swiss background, written in Latin script. They only illustrate the product – you do not need to know or be able to read them. In your own installation you enter your own data, and the interface is multilingual.
In Switzerland, public holidays and rules are a patchwork — different from canton to canton, sometimes even from municipality to municipality. Klacks handles exactly what simple tools get wrong.

Klacks offers countless ways to calculate rules and hour credits for nights, weekends, public holidays and overtime — exactly the way your contracts and company agreements require.
Klacks flags time collisions, rest periods that are too short, too many consecutive working days and work on holidays right as you plan — as an error or warning in the error list.
Rest period too short - Video 1 of 4
From working-time monitoring to your own infrastructure — everything works together.
Klacks continuously monitors the 45-hour and 50-hour weekly limits for each industry and makes any breach visible immediately — on request, Klacks hard-blocks the breach in automatic planning; with manual planning it stays at a warning.
The industry-specific thresholds for overtime premiums can be stored as a reference value; Klacks credits overtime premiums only as time credit and does not calculate amounts.
Klacks automatically factors the 11-hour rest period into planning, and the night hours that attract a premium are documented.
Klacks automatically counts the night shifts in the year and warns from the 25th night — on request, Klacks hard-blocks further night shifts in automatic planning; with manual planning it stays at a warning. You document the statutory time credit yourself.
Klacks arranges assignments and routes so that journeys stay short and time windows are met — usable across industries.
Klacks runs on your own infrastructure, and you choose the AI model yourself — with a locally hosted model, no AI request containing staff data goes to an external AI provider.
The built-in AI assistant Klacksy understands instructions in everyday language and controls Klacks; the plan is calculated by the rule-based planning engine — traceable through defined rules, not an opaque AI decision.
If someone drops out, Klacks immediately shows who is qualified and available — without overturning the whole plan.
Before a plan change goes live, you can run it through as an isolated copy — the 11-hour rest period under the ArG and premiums are calculated live exactly as in the real plan.
Only once everything checks out do you apply the variant; until then, your live schedule stays unchanged. This lets you prepare a suitable scenario in advance for foreseeable situations — such as a staff member off sick or a peak in orders — so you are ready to act immediately when it matters, instead of improvising under time pressure. There is no artificial limit — you create as many scenarios as your planning needs.
Klacksy isn't a bolted-on marketing chatbot but is embedded directly in the Klacks interface. Staff and schedulers use chat to check shift times or clarify availability. A built-in skills and rules system ensures that Klacksy makes traceable suggestions — not black-box decisions. For businesses with strict data protection requirements, the AI model can also be hosted locally.

Note on the sample data: All names, places (for example Winterthur), addresses and figures in these recordings are fictitious demo data with a Swiss background, written in Latin script. They only illustrate the product – you do not need to know or be able to read them. In your own installation you enter your own data, and the interface is multilingual.
That way staff data stays on your own servers; the assessment under the revised Federal Act on Data Protection (revFADP, revDSG) remains with you.
The source code of the backend and the interface is public. Your IT team can check what Klacks does with personnel data — and keep running Klacks independently of us.
Klacks runs on your own servers. Personnel data is held in your infrastructure; the data-protection assessment under the laws of your country remains with you.
Klacksy works with the model of your choice — from external providers to a model you run yourself. You decide on cost, data protection and provider.
Your data lives in your own database (PostgreSQL), the code is open, and you switch the AI provider in the settings.
No license fees does not mean no costs. Servers, operation and maintenance cost money, and so does an external AI model — what you do not pay is a fee per employee.
Your data is stored on your own servers. For address lookup and route calculation, Klacks uses public services based on OpenStreetMap by default; addresses and coordinates are sent there without names. The documentation lists which other external services Klacks calls.
Klacks speaks MCP (Model Context Protocol), the open standard through which AI agents work with software. Any agent that speaks the open standard MCP — such as Claude, Cursor or your own agents — can work directly with Klacks: with the tools Klacksy uses as well, and only with the rights of the connected user.
Operating steps in the interface and sensitive functions such as managing access tokens stay locked, and an agent never receives more than supervisor rights.
How to connect your agentAlso in Klacks:Shift planningRoute optimizationAI assistantScenariosAbsencesRules & surchargesInstalled on your premisesOpen Source
Klacks automatically detects when an assignment triggers the night premium or the maximum weekly working time is reached, and makes it visible straight away — no manual recalculating. On request, Klacks hard-blocks the breach in automatic planning; with manual planning it stays at a warning.
Try the Playground to see how Klacks automates ArG maximum working hours, rest periods and night premiums — installed at your site or in the Playground, without licence fees and without registration.
Klacks is open source under the AGPL-3.0. Host it yourself, keep your data with you, pay no license fees — you stay in full control.
No demo appointments, no sales calls: try Klacks right in your browser — or install it on your own server or an office PC.
A public Klacks instance with sample data — right in your browser, no installation, no registration.
Office PC with Windows: download the setup file and double-click it, no Docker needed. Your own server: the installation package contains the installer and the configuration for the database and HTTPS; the installer pulls the Docker images at startup.
Download the installation package Office PC with Windows: also in the Microsoft StoreKlacks is open source under the AGPL-3.0. Backend, frontend, and Docker images are public — inspect it, fork it, contribute.
View the repository