Can I use Klokka commercially?

Yes. The MIT licence allows use, changes and commercial use, as long as the copyright notice and the licence text stay with the code.

Do I need my own server?

No. The service on klokka.se is free to use. Self-hosting is a choice, not a requirement.

What do I need to self-host Klokka?

The API, the web app, PostgreSQL, a Logto instance for sign-in and an SMTP account for invitations. Push notifications need an Expo project and Firebase. There is no install guide yet.

Is there a Docker image?

The repository has a Dockerfile for the API, the web app and the website, so you can build your own images. Ready-made images to pull are not published today.

How is Klokka different from Kimai or solidtime?

In who records the time. In Kimai and solidtime people track their own time, often per project. In Klokka the employer logs the hours for the staff, who see the same month on their phones.

Open source time tracking for employers of hourly staff

Klokka is open source time tracking under the MIT licence, built for employers who log the hours their hourly staff worked, with each employee seeing the same month. The hosted service is free to use with no limit on employees, and it runs on the web and Android, in English and Swedish.

Open source means you can read every line that handles your staff's hours, and Klokka does not disappear with a company. The code is on GitHub, and the version running on klokka.se is built from the same code.

What MIT means here

The MIT licence is one of the most permissive licences there is. You may use Klokka, change the code and run it, in your own business or for others, commercially too. The one condition is that the copyright notice and the licence text travel with the code when you pass it on.

The same code as the hosted service

There is no closed core. Everything the service on klokka.se runs is in the same repository: the API, the web app, the Android app and this website. What is not in there is our passwords and keys, as it should be.

What is in the repository

All of Klokka lives in one repository, split into a few parts:

The API, written in Java 25 with Quarkus, on a PostgreSQL database.
The web app in Next.js and the Android app in Expo (React Native).
One API contract in OpenAPI, from which both the server and the clients are generated.
Sign-in through Logto, and a Dockerfile for the API, the web app and the website.

Run it yourself

To self-host Klokka you need the API, the web app, a PostgreSQL database, your own Logto instance for sign-in and an SMTP account for the invitation emails. Push notifications to the Android app also need your own Expo project and Firebase.

The code and the Dockerfiles are on GitHub. There is no step-by-step self-hosting guide yet: the README covers running Klokka locally for development. For most people the hosted service is the simplest option, and it is free to use.

How Klokka differs from other open source time trackers

Kimai, solidtime and Traggo are good open source tools, but they are built for people tracking their own time, often per project or client, with a timer. Klokka is built for an employer who records the hours for their staff, who then see them.

The licences differ too: Kimai and solidtime are AGPL-3.0, Traggo is GPL-3.0 and Klokka is MIT.

Contribute

The issue list on GitHub is the roadmap. If you find a bug or miss something, open an issue on GitHub. Pull requests are welcome, code and translations alike: read CONTRIBUTING.md first. Security problems are reported as described in SECURITY.md, not in a public issue.

Your data

Any month can be exported as a CSV file whenever you like, so your hours are never stuck in Klokka. If you self-host, the hours sit in your own database. How the hosted service handles data is in the privacy policy, and who builds Klokka is on the about page.