BuildBaseKit provides
One infrastructure capability
Adopt authentication, file storage, or another focused foundation without inheriting an entire application.
Modular
Adopt one capability at a time
Focused Spring Boot foundations without unrelated application infrastructure. The foundation handles a backend capability; the application remains yours.
Capability map
What do you need?
Choose the infrastructure capability first. The matching foundation stays focused on that boundary.
focused scopeclear boundarySelected foundationAuthKit or FiloraFS
focused infrastructureYour application
Domain logicBusiness workflowsProduct features
Adopt the capability. Keep ownership of the application.
Ownership boundary
The application remains yours
BuildBaseKit provides a focused infrastructure foundation. You keep control of the decisions that make the application your product.
Your applicationThe larger system stays in your hands.
Domain behaviorProduct decisionsAuthorization rulesDeploymentEvolution
Questions
Frequently asked questions
What does modular mean here?
Each BuildBaseKit foundation addresses a focused backend capability. It is a starting codebase, not an installable Spring module or a mandatory platform.
What remains in my application?
Your domain logic, business workflows, product features, authorization decisions, and deployment choices remain application responsibilities.
Choose your foundation
Choose a stronger starting point
Start with one documented capability, review its boundary, and build the application-specific behavior on top.
Focused scopeExplicit boundariesReady to adapt
What does your backend need?Released foundations