head to head · open source
Sa-Token vs KeePassDX
Sa-Token has 19,051 GitHub stars, 2,914 forks, 111 open issues and last shipped 2 days ago. KeePassDX has 7,340 stars, 403 forks, 541 open issues and last shipped 5 days ago. Sa-Token leads on adoption by 160% (19,051 vs 7,340 stars). Sa-Token is written in Java under Apache-2.0; KeePassDX is written in Kotlin under GPL-3.0. Sa-Token has attracted 15% as many forks as stars, KeePassDX 5%. Sa-Token was the more recently maintained of the two, and both are self-hostable with no licence fee.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| Sa-Token | KeePassDX | |
|---|---|---|
| GitHub stars | ★ 19K | ★ 7.3K |
| License | Apache-2.0 | GPL-3.0 |
| Written in | Java | Kotlin |
| Last push | 2026-09-18 | 2026-09-15 |
| Forks | ⑂ 2.9K | ⑂ 403 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick Sa-Token if
- You weight community size — 19K stars and counting
- You want the Apache-2.0 license terms
- Your stack matches Java
- You value the larger contributor base for long-term maintenance
pick KeePassDX if
- You want the KeePassDX feature set and don't need the biggest community
- You prefer the GPL-3.0 license terms
- Your stack matches Kotlin
- You evaluated both and KeePassDX fits your workflow better
About Sa-Token
Sa Token is a free, open source, one stop Java authentication and authorization framework, licensed under Apache 2.0, that gives Java and Spring Boot developers login authentication, permission checks, distributed sessions, single sign on, OAuth2.0, gateway authentication, JWT integration, API key authorization and API parameter signing from a single dependency.
read the full Sa-Token overview →
About KeePassDX
KeePassDX is a free, open source and ad free password and passkey manager for Android that keeps credentials in a single encrypted local database file in KeePass format and fills login forms through autofill and its own keyboard.
read the full KeePassDX overview →
More in Security & Privacy
Related comparisons
More Identity & Access Management (IAM) projects
Compare either of these against the rest of the Identity & Access Management (IAM) field.
Frequently asked questions
Is Sa-Token or KeePassDX more popular?
Sa-Token has 19,051 GitHub stars and KeePassDX has 7,340. Sa-Token has the larger community by that measure.
Are Sa-Token and KeePassDX free?
Both are open source. Sa-Token is licensed under Apache-2.0 and KeePassDX under GPL-3.0. Neither carries a licence fee.
What is the difference between Sa-Token and KeePassDX?
Sa-Token is written in Java and KeePassDX in Kotlin. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, Sa-Token or KeePassDX?
Choose Sa-Token if you want the larger community (19,051 stars) or its Apache-2.0 licence terms. Choose KeePassDX if its feature set, stack or GPL-3.0 licence fits better. Both are self-hostable.