head to head · open source
Sa-Token vs Hexclave
Sa-Token has 19,107 GitHub stars, 2,913 forks, 111 open issues and last shipped 20 days ago. Hexclave has 6,887 stars, 528 forks, 65 open issues and last shipped yesterday. Sa-Token leads on adoption by 177% (19,107 vs 6,887 stars). Sa-Token is written in Java under Apache-2.0; Hexclave is written in TypeScript under a custom or non-standard licence. Sa-Token has attracted 15% as many forks as stars, Hexclave 8%. Hexclave was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (authorization), so they are genuine substitutes rather than adjacent tools.
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 | Hexclave | |
|---|---|---|
| GitHub stars | ★ 19K | ★ 6.9K |
| License | Apache-2.0 | Custom / other |
| Written in | Java | TypeScript |
| Last push | 2026-10-16 | 2026-11-04 |
| Forks | ⑂ 2.9K | ⑂ 528 |
| 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 Hexclave if
- You want the Hexclave feature set and don't need the biggest community
- You prefer the Custom / other license terms
- Your stack matches TypeScript
- You evaluated both and Hexclave fits your workflow better
About Sa-Token
简体中文 繁體中文 English 日本語 한국어 Русский Sa Token v1.46.0 ✨ 开源、免费、一站式 java 权限认证框架，让鉴权变得简单、优雅！ 在线文档： 需求提交 📝 前言： 回望 2020 年初，我为 Sa Token 提交第一行代码之际， 彼时市面上 Java 缺少的不仅是一个简洁好用的鉴权框架，更是一整套清晰、自洽的权限架构设计思想 。 因此，这几年间我将大量时间倾注在 Sa Token 的文档编写，几乎每一章节、每一句话、每一个字都经过反复修改、精细打磨，以求做到最清晰、干练、易懂的表述。 用心阅读文档，你学习到的将不止是 Sa Token 框架本身，更是绝大多数场景下权限认证设计的最佳实践 。 🛠️ Sa Token 介绍 Sa Token 是一个轻量级 Java 权限认证框架，目前拥有五大核心模块：登录认证、权限认证、单点登录、OAuth2.0、微服务鉴权。 你还在手搓以下功能？ Stop，让 Sa Token 来！ 要在 SpringBoot 项目中使用 Sa Token，你只需要在 pom.xml 中引入依赖： 除了支持 SpringBoot2、Sa Token 还为 SpringBoot3/4、Solon、JFinal 等常见 Web 框架提供集成包，做到真正的开箱即用。 简单示例展示： （点击展开 / 折叠） Sa Token…
read the full Sa-Token overview →
About Hexclave
Hexclave The user infrastructure platform. Hexclave handles everything around your users: authentication, teams, payments, emails, analytics, and much more. Get started with our AI prompt below. Website · Docs · Dashboard · Discord Get started Setting up Hexclave is one prompt. Paste this into your coding agent of choice: For AI agents If you're an AI coding agent, use your web fetch tool or curl the skill documentation for up to date integration instructions: What's included Hexclave ships as a catalog of apps you switch on as your product needs them. Each one is built on the same user model, and new apps land…
read the full Hexclave 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 Hexclave more popular?
Sa-Token has 19,107 GitHub stars and Hexclave has 6,887. Sa-Token has the larger community by that measure.
Are Sa-Token and Hexclave free?
Both are open source. Sa-Token is licensed under Apache-2.0, and Hexclave has no licence declared in this registry. Both are free to self-host.
What is the difference between Sa-Token and Hexclave?
Sa-Token is written in Java and Hexclave in TypeScript. 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 Hexclave?
Choose Sa-Token if you want the larger community (19,107 stars) or its Apache-2.0 licence terms. Choose Hexclave if its feature set, stack or Custom / other licence fits better. Both are self-hostable.