// the take
SpringBlade is a Java microservices scaffold for building multi-tenant SaaS backends, built on Spring Boot 4, Spring Cloud 2025 and Java 21, with companion Vue3 and React frontends (Saber/Sword). It's aimed at teams building enterprise admin/SaaS systems who want gateway, auth, service discovery and distributed transactions already wired together rather than assembled from scratch.
Nine years in production with documented migration through several Spring Cloud generations and deployment models (fat jar, Docker, k8s), so the architecture isn't speculative. Comes with a working distributed-transaction example (Seata) and circuit-breaking (Sentinel) already integrated, not just name-dropped in the README. Includes a code generator (blade-develop) that scaffolds controller/service/mapper/entity plus the matching Vue CRUD page, which cuts real boilerplate for typical admin-CRUD features. Multi-tenancy is implemented at the framework level rather than bolted on per-service.
Adopting any one piece means buying into the whole BladeTool ecosystem and its conventions — there's no clean path to taking just the auth module or just the gateway. Running the full topology (gateway, auth, Nacos, admin, resource, report, demo services) means real operational overhead before you've written any business logic, which is a lot for a project that doesn't need microservices yet. Primary docs, issue discussion and support channels (QQ groups, Gitee wiki) are Chinese-first, so non-Chinese-speaking teams will struggle to get unblocked. The README pairs the Apache 2.0 license with a paid 'membership plan' and an explicit threat to pursue unauthorized commercial reuse, which is inconsistent with a permissive license and worth clarifying before depending on this commercially.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →