Learn how Logto 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
6 hours agoRepository age
5 yearsVersion
v1.45.0License
MPL-2.0Self-hosted
YesRepository
logto-io/logto
Last 30 days
Last commit
12 hours agoRepository age
2 yearsVersion
v1.17.0License
AGPL-3.0Self-hosted
YesRepository
voidauth/voidauth
Both Logto 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.
Logto significantly outpaces VoidAuth in community adoption with 14,793 stars compared to 2,892 stars on GitHub. This 5.1x difference suggests Logto has a much larger and more active community. In terms of developer contributions, Logto has 1,204 forks, indicating strong developer engagement.
VoidAuth is growing faster, adding 49 stars in the last 30 days (+1.7%) against adding 156 stars for Logto (+1.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 Logto last updated 6 hours ago and VoidAuth 12 hours ago.
Logto has been in development longer, starting 5 years ago, compared to VoidAuth which began 2 years ago. This 3.9-year head start suggests Logto may have more mature features and established processes.
The projects use different licenses: Logto is licensed under MPL-2.0 while VoidAuth uses AGPL-3.0. Consider the licensing requirements when choosing for your project.
Both tools serve similar use cases in Authentication & SSO.
Both Logto 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