Reserve call-ups (Miluim) and Shabbat restrictions create planning gaps no generic scheduler is built for.
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.
This is how you talk to Klacksy — you can see these sentences in the videos:
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.
Israel has no cantonal or regional holiday layer the way other countries do — the legal variety runs along religious affiliation instead, and in Jerusalem even along an ancient walled-city privilege. Klacks captures exactly what purely geography-based tools miss.

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
Crisis-resilient rostering, not a generic 24/7 planner.
The moment a reservist is called up, the Recovery Engine finds the best qualified stand-in from your pool — without touching the reservist's own contract data.
Staff mark their Shabbat availability once; the autofill engine reliably excludes them from Shabbat shifts from then on.
Klacks' typed surcharge engine credits the combined overtime and rest-day premiums as time credits in hours, so your payroll system receives clean hours instead of manual guesswork — the money amounts are calculated there.
Calendar rules handle the Friday/Saturday week and Shabbat start/end times natively.
Klacks already exports hours, overtime and allowances to CSV/Excel; a Hashavshevet-compatible format is next on our roadmap.
Before a schedule change goes live, you can run it as an isolated copy first — rest-day premiums and Shabbat rules get recalculated exactly as they would in the real schedule.
Only once everything checks out do you promote that version; until then, your live roster stays untouched. That way you can prepare a ready-to-go scenario in advance for situations you can see coming — a reserve call-up, a sick call-out, or a demand spike — and switch to it instantly when it happens, instead of improvising under time pressure. There's no artificial cap either — create as many scenarios as your planning needs.
Klacksy isn’t a bolted-on marketing chatbot — it’s embedded directly in the Klacks interface. Staff and schedulers ask about shifts via chat or resolve qualification conflicts within the team. A built-in skills and rules system ensures Klacksy makes traceable suggestions — never a black-box decision.

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.
Klacks combines instant replacement planning against your configured rules with autofill that keeps the free day per week you configure; it does not check the continuous Shabbat rest itself.
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 locks the reservist's slot, surfaces the best qualified replacement from the pool, and leaves the rest of the roster untouched — no manual re-planning.
Try the Playground to see instant replacement planning and Shabbat-aware autofill in action — or run it on your own premises.
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.
The installation package contains the installer and the configuration for the database and HTTPS; the installer pulls the Docker images from the registry at startup. One command starts the installation.
Download the installation packageKlacks is open source under the AGPL-3.0. Backend, frontend, and Docker images are public — inspect it, fork it, contribute.
View the repository