Self-host Kimai with Levelrail
A self-hosted time tracking tool for freelancers and teams, with invoicing and reporting.
- Authorkimai
- LicenceAGPL-3.0-or-later
- Memory512 MiB
- Archarm64
- Services2
How to self-host Kimai
-
Pull the images
2 images are pulled on your server.
Show images
mysql:8kimai/kimai2:apache
-
Create the app
2 services start in a single Compose app, with 2 named volume mounts for your data, on port 8001.
-
Fill in the secrets
4 secrets are generated and stored encrypted, 3 settings are preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
Kimai requirements
- Memory
- About 512 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 8001
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- AGPL-3.0-or-later, network copyleft (agpl) license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 8001 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Kimai. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the Kimai docs page.
Deploy Kimai your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Kimai from the CLI
levelrail-cli templates deploy kimai --name my-kimai Deploy Kimai with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/kimai/deploy Kimai configuration
Kimai services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| db | mysql:8 | none | kimai_db_data -> /var/lib/mysql |
| kimai | kimai/kimai2:apache | 8001 | kimai_data -> /opt/kimai/var |
Kimai environment variables
| Variable | Service | Value |
|---|---|---|
| MYSQL_DATABASE | db | Preset by the template |
| MYSQL_PASSWORD | db | Generated at deploy |
| MYSQL_ROOT_PASSWORD | db | Generated at deploy |
| MYSQL_USER | db | Preset by the template |
| ADMINMAIL | kimai | Preset by the template |
| ADMINPASS | kimai | Generated at deploy |
| DATABASE_URL | kimai | Generated at deploy |
Ports and volumes
- Ports
- 8001
- Volumes
- 2 named mounts: kimai_db_data -> /var/lib/mysql, kimai_data -> /opt/kimai/var
Kimai FAQ
How much memory does Kimai need?
The catalog lists about 512 MiB of memory for Kimai across its 2 services.
Does Kimai run on arm64?
For Kimai, an arm64 image is published; amd64 is image published.
What licence is Kimai under?
Kimai is licensed under AGPL-3.0-or-later, which is network copyleft, so source sharing also applies when it is offered as a hosted service.
Does Kimai need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which database does Kimai bundle?
The template includes MySQL, running as its own service.
Which ports does Kimai use?
Kimai listens on port 8001 inside the stack.
Where does Kimai keep its data?
In named volumes: kimai_db_data mounted at /var/lib/mysql and kimai_data mounted at /opt/kimai/var.
Can I deploy Kimai on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id kimai for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image mysql:8, kimai/kimai2:apache is what you deploy there.