BuildBaseKit Product Licensing

Free and Lite products

Free and Lite BuildBaseKit boilerplates use the MIT License. This includes AuthKit-Lite and FiloraFS-Lite, and will include StripeKit-Lite when it is released.

The LICENSE file in each product repository remains authoritative. BuildBaseKit does not add commercial restrictions to these MIT-licensed products.

Paid and Pro products

Paid and Pro BuildBaseKit boilerplates use the BuildBaseKit Commercial License. This is the standard model for current and future paid products, including AuthKit-Pro, FiloraFS-Pro, StripeKit-Pro, future Pro boilerplates, and future mixed paid boilerplates.

One purchase licenses one developer. That developer receives a non-exclusive, non-transferable license to use and modify the purchased product in unlimited permitted end products and deployments.

Developer licensing

Every developer who directly accesses or works with the proprietary source code of a paid BuildBaseKit product must have their own valid license. If multiple developers work with that source, each developer requires their own license, including employees, contractors, agency developers, and client developers.

End users, customers who only use a completed application, servers, domains, deployments, CI/CD systems, automated tools, and AI coding assistants acting for a licensed developer do not need separate licenses.

Permitted application use

• personal projects
• commercial projects
• SaaS products
• freelance and client projects
• internal company applications
• production deployments

There are no per-project, server, domain, or deployment-count limits for these permitted uses. Completed products may be deployed as SaaS services, hosted applications, JARs, Docker images, or on-premises installations.

Client and team projects

A licensed developer may build and deliver completed applications for clients. Completed end-product delivery is allowed, including delivery of the integrated application source.

If additional client or team developers directly access or work with the paid BuildBaseKit source, each of those developers needs their own valid license. Clients and customers do not need a license merely to receive or use a completed application.

Prohibited source-code redistribution

• redistribute the paid BuildBaseKit source as a standalone product
• resell it as a boilerplate
• repackage it as a template, starter kit, foundation, or reusable source-code package
• publish the purchased source publicly or upload it to a public repository
• sublicense it as reusable source
• share the original package or source with unlicensed developers
• create or sell a competing reusable boilerplate or template substantially derived from BuildBaseKit source

Completed end-product delivery is allowed. Redistribution of the BuildBaseKit boilerplate itself is not.

Authoritative licenses and ownership

This website page is a human-readable licensing overview. The LICENSE file included with each free or paid product is the authoritative product license and governs that product.

Purchasing a paid product grants usage rights; it does not transfer ownership of the original BuildBaseKit boilerplate. Third-party libraries and dependencies continue to use their own licenses and notices.

Questions

For clarification before purchasing or delivering a client project, email hello@buildbasekit.com. Related commercial terms appear in the Refund Policy and Support & Updates Policy.