Getting Started
Choosing a foundation
Match authentication or file-storage requirements to the smallest released BuildBaseKit foundation that fits.
Updated
Authentication
Choose the smallest AuthKit edition whose verified boundary fits the application. Both editions provide password authentication, JWT access tokens, rotating refresh credentials, RBAC, optional passkeys, H2 local startup, and MySQL-compatible Flyway migrations. Pro adds broader account, session, provider, and passwordless workflows.
| Decision | AuthKit-Lite | AuthKit-Pro |
|---|---|---|
| Core JWT authentication | Yes | Yes |
| Rotating refresh credentials | Yes | Yes |
| RBAC | Yes | Yes |
| Passkeys | Yes | Yes |
| Independent session controls | No | Yes |
| Email lifecycle workflows | No | Yes |
| OAuth2/OIDC linking | No | Yes |
| Magic links | No | Yes |
| Security activity history | No | Yes |
| License | MIT | Commercial, one developer |
| Access | GitHub | Gumroad |
| Best fit | Focused authentication foundation | Broader production authentication requirements |
File storage
| Decision | FiloraFS-Lite | FiloraFS-Pro |
|---|---|---|
| Storage | Local filesystem | LOCAL + S3-compatible (AWS S3 / MinIO) |
| Access model | Shared API key | Password, JWT, ROLE_USER / ROLE_ADMIN |
| Ownership | Not included | Owner-scoped files with admin access |
| Database | None | H2 locally; MySQL for persistence |
| Admin provider control | One configured local path | Runtime status, configuration, testing, and explicit switching |
| Provider persistence | Not included | Database-backed configuration and per-file provider tracking |
| Temporary access | Not included | LOCAL tokens and S3 pre-signed GET URLs |
| Best fit | Learning, prototypes, small single-host tools | Authenticated production file APIs |
When to build from scratch
Build the capability yourself when infrastructure is the differentiating product, your authorization or data-lifecycle model is fundamentally different, or a foundation's explicit limitations do not fit the deployment.