Licensing
Fatleon Commerce is proprietary source code. The same codebase is sold under two commercial licenses. Your purchase archive includes one license file, version 2.2. The receipt names the SKU: Standard or Agency. That file, together with the receipt, governs your rights. This page is a summary of that file.
If this page and the license file disagree, the license file controls software use. Terms of sale control purchase, payment, and refunds. The receipt controls the SKU and the order.
Standard and Agency
| Standard | Agency | |
|---|---|---|
| Buyer | A brand, startup, or in-house team. | A freelancer, studio, or integrator. |
| Scope | Unlimited storefronts that you or your company own and operate. | Unlimited client storefronts that you build and deliver. |
| Term | Perpetual. One-time purchase. | Perpetual. One-time purchase. |
| Client work | Requires the Agency license. | Included. |
| Hand the project repository to the client | — | Yes. You grant an End Client Project License for that one storefront. It is a sublicense from you, not a new license from the seller. |
| Client's maintainers | — | Authorized Maintainers may work on that store only. |
| Hosting | Your infrastructure. | Yours or the client's. Operational and compliance responsibility stays with you. |
| Transfer the license to another company | Written consent required. | Written consent required. |
| Resell the Fatleon Commerce source | Prohibited. | Prohibited. |
Pricing is on the product page. It is not in the license file.
Both licenses
These limits apply to Standard and Agency.
| Limit | Rule |
|---|---|
| Redistribution | Reselling, sublicensing, or redistributing the kit source as a template, boilerplate, starter, or competing product. |
| Public exposure | A public repository or file share that exposes the kit source. |
| Multi-tenant product | A SaaS or site builder that hands out substantially the same Fatleon Commerce functionality without a separate license from the seller. |
| Assignment | Assigning the license to another person or company without written consent. |
What you may do
Standard. Run unlimited storefronts that you operate. Modify the source. Keep it in a private Git repository. Use AI tools. Have your team work in that repository. Use a staging or preview environment per store. Change the domain of an existing store without a new purchase.
Agency. Deliver unlimited customized stores for end clients, including white-label work. Deploy on your AWS account or the client's. Transfer the customized project source for one storefront under the End Client Project License. The client may appoint Authorized Maintainers (employees, operators, or another agency) for that store only. The client does not receive ownership of the kit source and may not start other stores from it. Ownership of custom work between you and the client is set in your contract with them, not in this license.
Termination
The license is perpetual unless it ends for a material breach, such as public redistribution of the kit source.
| After termination | Effect |
|---|---|
| New work | New projects and new deployments that use the kit source stop. |
| Stores already live | They may keep running. An Agency end client's project license continues for a store that was already delivered. |
| Upkeep | Backup, migration, and maintenance of those stores continue. That source is not a base for an unrelated store or a competing product. |
The file in your archive
The archive contains one of these, matching the SKU on the receipt. The same v2.2 text is published here:
| File | SKU | Text |
|---|---|---|
LICENSE-STANDARD | Standard | Standard License (v2.2) |
LICENSE-AGENCY | Agency | Agency License (v2.2) |
The copy in your purchase archive is the one that applies to that order.