Learn how Hackatime and SolidTime differ in their key features, development activity, technology stack and community adoption, so you can decide which of these time tracking tools is best for you.
Last 30 days
Last commit
9 hours agoRepository age
2 yearsLicense
MITSelf-hosted
YesRepository
hackclub/hackatime
Last 30 days

Both Hackatime and SolidTime have their unique strengths and serve similar purposes effectively. Consider your specific needs regarding popularity, growth, activity, technology, maturity, licensing and features when making your decision.
SolidTime significantly outpaces Hackatime in community adoption with 9,116 stars compared to 216 stars on GitHub. This 42.2x difference suggests SolidTime has a much larger and more active community. In terms of developer contributions, SolidTime has 534 forks, indicating moderate developer engagement.
Hackatime and SolidTime are moving at much the same rate, adding 3 stars and adding 132 stars respectively over the last 30 days (+1.4% vs +1.5%). Neither is pulling away from the other on momentum alone.
Both projects show recent activity, with Hackatime last updated 9 hours ago and SolidTime 19 hours ago.
Both tools share common technology foundations, being built with JavaScript, CSS, Bash, Typescript. However, they differ in their additional technology choices: Hackatime uses Ruby while SolidTime leverages PHP, Vue, Laravel.
SolidTime has been in development longer, starting 3 years ago, compared to Hackatime which began 2 years ago. This 1.1-year head start suggests SolidTime may have more mature features and established processes.
Hackatime uses the MIT license, which is more permissive than SolidTime's AGPL-3.0 license, potentially offering greater flexibility for commercial use and integration.
Both tools serve similar use cases in Time Tracking.
Both Hackatime and SolidTime offer self-hosting capabilities, giving you full control over your data and infrastructure.