arbtt vs TimeCase
A side-by-side comparison of two self-hosted time tracking options — licensing, setup difficulty, resource needs, and what each one replaces.
Not the right match-up?
arbtt
Automatic rule-based time tracker for desktops
VS
TimeCase
Free self-hosted time tracking web application
| Feature | arbtt | TimeCase |
|---|---|---|
| Category | Time Tracking | Time Tracking |
| License | GPL-2.0 | MIT |
| Language | Haskell | PHP |
| Setup difficulty | Medium | Medium |
| Min. RAM | 128 MB | 256 MB |
| Deployment | binary, source | docker, bare-metal |
| GitHub stars | ★ 354 | ★ 21 |
| First released | 2009 | 2020 |
| Replaces | RescueTime, ManicTime | Clockify, Toggl |
Why pick each one
Choose arbtt if…
- Released under the GPL-2.0 license
- Written in Haskell
- Tiny footprint — runs in 128 MB RAM
Choose TimeCase if…
- Released under the MIT license
- First-class Docker support for quick deployment
- Written in PHP
- Tiny footprint — runs in 256 MB RAM
Frequently asked questions
Is arbtt or TimeCase better?
Neither is universally better. arbtt has the larger community; both share a medium setup difficulty, so the decision comes down to features and licensing.
Are arbtt and TimeCase free and open-source?
Yes. arbtt is licensed under GPL-2.0 and TimeCase under MIT. Both can be self-hosted at no software cost.
Can I run arbtt and TimeCase with Docker?
arbtt: check the project docs for container support. TimeCase: yes.