Learn how Hanko and VoidAuth differ in their key features, development activity, technology stack and community adoption, so you can decide which of these authentication & sso providers is best for you.
Last 30 days
Last commit
8 hours agoRepository age
5 yearsVersion
v3.1.0License
AGPL-3.0Self-hosted
YesRepository
teamhanko/hanko
Last 30 days
Last commit
12 hours agoRepository age
2 yearsVersion
v1.17.0License
AGPL-3.0Self-hosted
YesRepository
voidauth/voidauth
Both Hanko and VoidAuth have their unique strengths and serve similar purposes effectively. Consider your specific needs regarding popularity, growth, activity, maturity, licensing and features when making your decision.
Hanko significantly outpaces VoidAuth in community adoption with 9,047 stars compared to 2,892 stars on GitHub. This 3.1x difference suggests Hanko has a much larger and more active community. In terms of developer contributions, Hanko has 1,021 forks, indicating strong developer engagement.
VoidAuth is growing faster, adding 49 stars in the last 30 days (+1.7%) against adding 10 stars for Hanko (+0.1%). VoidAuth is the smaller project of the two, so it is closing the gap rather than extending a lead.
Both projects show recent activity, with Hanko last updated 8 hours ago and VoidAuth 12 hours ago.
Hanko has been in development longer, starting 5 years ago, compared to VoidAuth which began 2 years ago. This 3.1-year head start suggests Hanko may have more mature features and established processes.
Both projects use the AGPL-3.0 license, providing identical terms for usage and distribution.
Both tools serve similar use cases in Authentication & SSO.
Both Hanko and VoidAuth offer self-hosting capabilities, giving you full control over your data and infrastructure.
vs
vs
vs
vs
vs
vs
vs
vs
vs
vs
vs
vs
vs
vs
vs
vs
vs
vs
vs
vs