Managed Kimai hosting
Pilae installs, patches, backs up and monitors Kimai for you, on your own servers or in any of 10+ Pilae Cloud regions, six of them in Switzerland and the EU.
From CHF 449EUR 479USD 559 a month on Starter, hosting and onboarding included.
- Business
- Open source
- Replaces Toggl Track
- Runs on
- Your own hardware, or a Pilae Cloud region
- Replaces
- Toggl Track, Clockify, Harvest
- Licence
- AGPL-3.0-or-later
Kimai among the business apps
CRM, ERP, projects and scheduling. The records you are least willing to rent.
Kimai system requirements
Before anything is deployed, this is what has to exist. We size it with you in the first session, and we say so when your own hardware is already enough.
All 5 requirements, and why each is there
- CPU and memory2 vCPU · 4 GBUpstream publishes no minimum. This is our starting size for Kimai and MariaDB on one machine, and we resize it from what monitoring shows during long reports and large exports.
- DatabaseMariaDB or MySQLKimai supports MariaDB and MySQL only. PostgreSQL is not supported and not planned upstream, so Kimai gets its own database with its own backup.
- Sign-inSAML 2.0 or LDAPBoth are in the open-source core. SAML covers Keycloak and Microsoft Entra ID. There is no OpenID Connect sign-in; it is an open feature request upstream. The official image already includes the LDAP library that a manual install has to add.
- Persistent storagevar/data · var/invoices · var/pluginsGenerated invoices, uploaded invoice templates and plugin code. All three are volumes backed up with the database, because a template kept only inside the container is lost when the container is removed.
- DNS and TLS1 hostnameKimai has to run at the root of its own hostname; a subdirectory is not supported. Behind the Pilae gate on port 443 if people record time from outside the network.
Running Kimai in production: what it takes
Deploy with the data directories on volumes
A Kimai image we have run, on its own MariaDB, with the application secret set by us rather than generated inside the container, and the three data directories on volumes from the first day.
SAML sign-on, roles from groups
SAML sign-on through Keycloak or your existing IdP. Directory groups map to Kimai's team lead and admin roles and are applied again at every sign-in, so a role removed in the directory does not linger in Kimai.
Set rates, teams and a lockdown period
Rates by customer, project and person, teams deciding who sees which projects, and a lockdown period so hours cannot be changed after the month has been invoiced.
Restore onto the same Kimai version
A daily, encrypted copy of the database and the data directories goes offsite. On the Enterprise plan, the monthly drill puts it back into a scratch instance on the same Kimai version and opens an invoice from it.
Upgrade in your window, plugins included
The container migrates the database when it starts, so the way back is the copy taken just before. We check each plugin against the release and the upstream upgrade notes, then the Pilae Agent rehearses the upgrade on a copy and, once you approve, applies it in your window.
From our runbook
What a Kimai restore needs
mariadb/kimaientries, rates and invoice records, 1.8 GB
- kimai2_timesheetevery entry, begin and end
- kimai2_invoicesinvoice numbers and payment state
- migration_versionsschema version, must match the image
- bundle_migration_*schema state of each plugin
/opt/kimai/var/datavolume
- invoices/generated invoice files, 410 MB
- /opt/kimai/var/invoicesuploaded invoice templates, DOCX, ODS or XLSX
/opt/kimai/var/pluginsplugin code, paid ones licensed per installation
- ImportBundleimporter used for the Toggl move
repo: acme/ops/kimaiin your repository
- compose.yamlpinned image, volumes, environment
- local.yamlSAML connection and role mapping
- s3://acme-backups/kimaioffsite, daily, encrypted
Migrating from Toggl Track to Kimai
Toggl Track's CSV export of time entries, a feature of its paid plans, imports into Kimai through the free Importer plugin. Clients become customers, projects stay projects, tasks become activities, and each entry keeps its description, tags, billable flag and amount, though saving an imported entry again recalculates its price from Kimai's rates, so imported history is left unedited. People are matched by email and created if they do not exist yet, so the default time zone for new users is set before the first file goes in. The currency is not imported and the importer creates missing customers itself, so the default currency is set first, or customers are created beforehand with theirs. Toggl has to export with a date format the importer can parse. The Toggl format carries time entries only: project budgets and estimates go in through the same plugin's project CSV, and saved reports and integrations do not come across. Most of the work is in the mapping and the rates, which we check until Kimai's totals match Toggl's for the same months.
- Migration guideHow to migrate from Toggl Track to KimaiMove Toggl Track to self-hosted Kimai: export entries as CSV, set time zones, currency and rates first, import with the free Importer plugin, reconcile totals.
- ServiceSaaS migrationA fixed-scope migration off Google Workspace, Microsoft 365, Zapier, Airtable and ChatGPT to open-source apps, with a parallel run and a cutover plan.
Moving from Toggl Track to Kimai, step by step
- Set up the structure first: The default currency, or customers created beforehand with theirs, the default time zone for new users, and rates by customer, project or person, agreed before any history is imported.
- Import into a scratch copy: The Toggl Track CSV export goes through the Importer plugin into a scratch instance first. Totals per project and month are compared with Toggl reports before anything reaches production.
- Wire sign-on to the imported accounts: Kimai matches the SAML NameID against a username or an email address, so your identity provider sends the email people used in Toggl and they sign in to the account that holds their history.
- Cut over at a month end: History comes across up to the last closed month, and the open month follows as a final import on the night of the switch. Toggl stays readable until the first invoicing run closes on Kimai.
What Kimai is, and who runs it
Time tracking, billable hours and invoices for teams, run on your own hardware or in the Pilae Cloud region you choose, with no per-user fee for the open-source core.
Self-hosted Kimai for time tracking and billable hours
Kimai records time against customers, projects and activities, and turns it into reports, exports and invoices. People start a timer or enter hours afterwards, team leads see their teams, and rates by customer, project or person put a price on every entry. For attendance rather than project time, a time-clock mode limits people to clocking in and out. It covers what most teams use Toggl Track, Clockify or Harvest for.
Timesheets say who worked for whom and on what, and their descriptions often name clients and matters. Kimai runs on a dedicated machine, yours or one in a Pilae Cloud region you choose from 10+, six of them in Switzerland and the EU, and it answers only on your private network.
Read the full briefFold the brief
Kimai in production: MariaDB, SAML sign-on and plugin upgrades
Kimai supports MariaDB and MySQL only, so it gets its own MariaDB even where the rest of your estate runs on PostgreSQL. Sign-on is SAML through Keycloak or Microsoft Entra ID, with directory groups mapped to Kimai roles. Generated invoices, uploaded invoice templates and plugin code sit in three directories on volumes. They are backed up with the database daily, encrypted, to an offsite location in the country your contract names, and on Enterprise restored once a month into a scratch instance on the same Kimai version. Probes check the instance every 60 seconds and alert an engineer.
The Kimai container migrates the database when it starts, so an upgrade is undone by restoring the copy taken just before it, not by starting the old image. Each plugin release names the minimum Kimai version it needs, so we check every installed plugin against a release before the Pilae Agent tests the upgrade on a copy, waits for your approval and applies it in your window.
Kimai licence and paid plugins
Kimai has no per-user fee, and two-factor authentication is in the open-source core as well. Any paid plugin your requirements need is named in the proposal, before anything is installed. Our operation follows the published plans. Talk to us about the time tracking you want to move.
What Pilae is responsible for
The same commitments on every app we run, Kimai included, and what stays yours. How the platform does it.
Ours
- A pinned version: A version we have run, not whatever latest resolves to that day.
- A runbook: What it depends on, how it fails, what to do about it. In your repository.
- Daily backups: Encrypted and offsite, and on Enterprise restored every month. A backup nobody has restored is a file.
- A patch window: Security updates in a window you agreed, with a rollback ready.
- Someone watching: Every endpoint probed on the minute. An alert reaches a person, not a dashboard nobody opens.
Yours
- The credentials: You hold them. Ours are separate, named, logged and revocable with one command.
- The approval: We ask before anything changes outside an agreed window.
- The exit: The machine, the data, the compose files and the runbook are already yours. Nothing stops when our access does.
Who runs it
Engineers who answer for it
Our engineers review every plan the Pilae Agent prepares and answer for the result.
Your data stays where the contract says
On your own servers or in Pilae Cloud. On Business and Enterprise you choose the region, and your contract names each location.
A Swiss company, a Swiss contract
Pilae is a Swiss company, and your contract with it is governed by Swiss law.
Kimai runs on Starter from CHF 449EUR 479USD 559 a month in Pilae Cloud, or on Business with up to three apps on your own servers.
Compare the plansKimai: common questions
Is Kimai open source?
Can Kimai replace Toggl Track?
Does Kimai keep the working-time records Swiss law asks for?
Can Kimai run on PostgreSQL?
Where do our timesheets live?
Ask the engineers who would run your Kimai
Thirty minutes on the deployment you already have, or the one you are about to start.
- Go deeperManaged operations and SLA for open-source appsPatching, daily encrypted backups, monitoring and incident response for your open-source apps, under an SLA with an availability commitment of up to 99.9%.
- CompareSelf-hosting vs managed open source: doing it yourself, or PilaeSelf-hosting gives you the apps and the whole job of running them. Pilae gives you the same open-source apps, operated under a contract, on your premises or in Pilae Cloud.
- CheckData processing agreement (DPA)Our standard DPA under the revised FADP and the GDPR, signed at onboarding, with every sub-processor for your service named in the agreement.
