Clockify Selfhost Cattr vs Virtual TimeClock

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?
FeatureClockify Selfhost CattrVirtual TimeClock
CategoryTime TrackingTime Tracking
LicenseApache-2.0⊘ Proprietary
LanguagePHPUnknown
Setup difficultyMediumMedium
Min. RAM512 MB512 MB
Deploymentdocker, bare-metalbare-metal
GitHub stars★ 97
First released20192020
ReplacesHubstaff, Time Doctor

Why pick each one

Choose Clockify Selfhost Cattr if…

  • Released under the Apache-2.0 license
  • First-class Docker support for quick deployment
  • Written in PHP
  • Lightweight — runs in 512 MB RAM
Clockify Selfhost Cattr details

Choose Virtual TimeClock if…

  • Released under the ⊘ Proprietary license
  • Written in Unknown
  • Lightweight — runs in 512 MB RAM
Virtual TimeClock details

Frequently asked questions

Is Clockify Selfhost Cattr or Virtual TimeClock better?

Neither is universally better. Clockify Selfhost Cattr has the larger community; both share a medium setup difficulty, so the decision comes down to features and licensing.

Are Clockify Selfhost Cattr and Virtual TimeClock free and open-source?

Yes. Clockify Selfhost Cattr is licensed under Apache-2.0 and Virtual TimeClock under ⊘ Proprietary. Both can be self-hosted at no software cost.

Can I run Clockify Selfhost Cattr and Virtual TimeClock with Docker?

Clockify Selfhost Cattr: yes. Virtual TimeClock: check the project docs for container support.

Related comparisons