Skip to content

kasl-server

Employees run kasl on their machines; managers get dashboards, charts, and reports across the whole team - and every employee gets a personal page.

A door that survives a bad connection

A day at a time on POST /api/v1/days, a backlog on /days/batch, and a task the employee deleted can be deleted here too. Each day is written on its own, so one the server will never accept does not block the rest.

A privacy policy the server enforces

What the server keeps about a person is a setting it recites on request, not a claim in a document. A field a level excludes is dropped before the day is written and never reaches the database.

The whole loop, closed

Agents deliver, employees see their own week, and a manager sees the team’s hours, a live column of who is working right now, the month as a grid, and a band naming who is worth a look and why.

One binary, self-hosted

The same binary serves the API and the web UI on the same port. Installing it is a compose file and a published image rather than a build.