If you've built more than one internal admin panel or back-office tool in Spring Boot, you already know the drill: authentication, role-based access control, a menu that shows/hides based on who's logged in, and CRUD scaffolding — before you've written a single line of the business logic anyone actually asked for.
I've built this same foundation across enterprise Java projects for 10+ years — fleet management systems, call/vehicle registry platforms, financial systems. Eventually I got tired of rebuilding it every time, so I packaged it into a starter kit.
What's in it
Spring Boot Admin Starter Kit — Java 21, Spring Boot 3.3, Spring Security, PostgreSQL, Thymeleaf, Flyway.
Authentication — form login, BCrypt password hashing, wired and working out of the box
Role-based access control — Admin / Manager / User, enforced at the route level, not just hidden in the UI
A dynamic, role-aware sidebar menu — define it once, it filters itself automatically based on who's logged in
Three working CRUD modules (Users, Categories, Products) — including a safe @ManyToOne relationship pattern that avoids the classic LazyInitializationException and ConcurrentModificationException traps most tutorials ignore
A reporting dashboard with a live Chart.js graph
Flyway-managed schema + seed data — clone it, run it, you have a working login screen in minutes
Clean layered architecture — Controller → Service → Repository, DTOs separating your persistence model from your views, constructor injection throughout
Why it's worth paying for instead of building it yourself
You could build all of this yourself — it's maybe a weekend of work if you already know the pitfalls. If you don't, it's longer, and you'll probably hit the same lazy-loading and role-enforcement bugs I already debugged and fixed. This kit skips that weekend.
Get it
$14.99 on Gumroad: https://halimora.gumroad.com/l/sbask
Comes with a full setup guide (prerequisites, database setup, local config, troubleshooting) so you're not stuck debugging environment issues instead of building.
Happy to answer questions about the architecture in the comments — and if you end up using it, I'd genuinely appreciate a review.
Top comments (0)