> ## Documentation Index
> Fetch the complete documentation index at: https://flex-fields.bjanczak.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Examples target Filament 5. Verify optional dependencies before configuring integrations.
> Upload transfer completion, permanent storage and record acceptance are separate milestones. Native and Spatie image conversions retain the original.

# Licensing questions

> FLEX Fields licensing examples for free internal use, SaaS products, agencies, corporate groups, distribution and upgrades.

These examples explain the current License v2.0. For the exact conditions, read the [full terms](https://flex-fields.bjanczak.com/docs/license-terms.md). Your accepted License Confirmation identifies the purchased scope; expressly agreed Custom terms can vary it.

## Free use and hosted products

> **Is the free version missing components?**
>
> No. The free-use grant limits how the software may be used; it does not describe a smaller component edition. The three standard commercial plans also have the same package features.

> **Is this an open-source license?**
>
> No. It is source-available. You can inspect the source and obtain the official package. GitHub separately permits viewing and service-native forks of its public repositories. Those platform permissions do not grant unrestricted commercial use, customer installations, OEM rights or independent redistribution outside their scope.

> **Can I fork the repository to contribute?**
>
> Yes. You can use GitHub's native fork and pull-request workflow while retaining existing notices. The FLEX license does not require deleting a fork that remains permitted by GitHub's platform terms after the contribution is accepted or closed. Contributing does not itself grant a commercial license. Your contribution remains yours, with the submission rights described in Section 4 of the license.

> **Can a profitable company use an internal app for free?**
>
> Yes, when every internal-use condition is met. Revenue is not the test. The application must serve the eligible entity's own operations rather than constitute or configure the commercial software service supplied to users.

> **Is the free-use test applied per panel or per Laravel application?**
>
> Neither boundary decides the result on its own. Assess what FLEX implements. Internal monitoring, employee records and company accounting can remain free even when they share a Laravel backend with a commercial product. FLEX controls defining the product's comparison rules or calculation parameters are commercial functionality even behind a staff login.
>
> Read-only access does not establish an exemption, and editing records does not automatically require a commercial license. See the [shared-backend examples](https://flex-fields.bjanczak.com/docs/licensing.md#internal-panel-and-commercial-product-in-the-same-application), including how to answer the license guide.

> **Does a small or freemium SaaS need a commercial license?**
>
> A live commercial hosted product needs the appropriate grant regardless of revenue or user count. Its freemium tier is part of that product. Private evaluation before launch is different from a paid pilot or live customer workload.

> **Do more tenants, developers or servers require Enterprise?**
>
> No. Standard plans have no tenant, user, developer or server limit within their scope. Enterprise Group adds qualifying entity coverage, not a larger usage allowance.

> **Do several domains, regions or subscription tiers count as separate products?**
>
> They can remain one product when they are deployments, language editions or tiers of the same service. Separately offered applications with different identities are separate products, even if they share a repository or are sold together.

## Agencies and client work

> **Does an agency's Unlimited Company license cover all clients?**
>
> No. It covers products owned and operated by the named agency entity. A client's own product needs the client's applicable free or commercial entitlement, or an expressly agreed distribution model.

> **Can bespoke client development remain free?**
>
> It can qualify under the work-for-hire conditions when you remain the responsible licensee/operator, the identified client receives runtime access only, and the application serves that client's internal operations rather than a software product or service offered to others. Each engagement must independently meet the conditions.

> **Can the client own the application and license the dependency directly?**
>
> Yes, for a genuine bespoke project. The client obtains the official dependency under its own qualifying free or commercial grant and appoints the agency as Authorized Personnel. The agency can install and maintain it on the client's behalf and hand over its independently written application code without delivering its own package copy or fork.
>
> An eligible client-internal application can remain free. A client's hosted SaaS needs the client's suitable commercial grant. This route does not authorize selling a reusable product to many buyers and calling each installation bespoke.

## Distribution and corporate coverage

> **What if customers install the product in their own cloud?**
>
> Customer-cloud and on-premises delivery of your software-containing product require Custom rights outside applicable permitted exceptions, even if you manage the installation. Source, container, installer and VM delivery count as copies; encryption does not change that.

> **Do customer branding and exported data require OEM rights?**
>
> Ordinary tenant logos, colors and domains can fit hosted use when you retain ownership, operation and the customer service relationship. Normal browser assets, hosted widgets, data exports and PDFs do not by themselves create redistribution rights.
>
> Supplying reusable package code, installable applications or independent reseller or sublicensing rights is different and requires appropriate Custom scope.

> **Does Enterprise Group include OEM or partly owned companies?**
>
> No. Enterprise Group covers the named parent and subsidiaries with 100% ownership interests and voting rights through the qualifying chain. It does not automatically include joint ventures, 99%-owned subsidiaries, independent clients or external distribution rights.

> **What happens when a subsidiary leaves the licensed group?**
>
> It has 90 calendar days to continue existing deployments while obtaining its own license or removing the package. Maintenance and security patches are allowed during that transition; new products and redistribution are not. Entities that remain covered retain group coverage.

> **Can I use my own brand and privately modify the package?**
>
> Yes, within the applicable grant. Retain copyright, license and third-party notices. There is no additional public “Powered by” badge requirement. Private contractor access for your licensed work does not grant contractors rights for their own products.

## Existing purchases and upgrades

> **Do I need to renew a Standard Plan every year?**
>
> No. Standard Plans are one-time purchases with perpetual rights within their scope, subject to compliance. There is no mandatory renewal, tenant fee or update subscription to continue licensed use. Custom duration and fees are individually agreed.

> **Are updates and other FLEX packages included?**
>
> Standard grants cover subsequent official updates, including major versions of this package, under their issued terms. Separate packages such as FLEX Forms are not included. Licensing does not promise future releases, particular compatibility, custom work or a support SLA.

> **Will a new license version change my existing purchase?**
>
> Previously issued licenses retain their agreed price, scope, duration, applicable version and update entitlement. There is no forced repurchase or retroactive increase. Broader group or OEM rights are not added automatically; requested expansion needs an appropriate grant.
>
> Copies validly obtained under an earlier free license remain governed by that version for those copies. Check the accompanying terms for new downloads and releases unless an existing commercial grant covers them.

> **Can my earlier payment count toward an upgrade?**
>
> Standard Plans originally issued under v2.0 have no upgrade deadline. Eligible net license fees can count toward the then-current destination price, subject to scope, consent and confirmation requirements. Taxes and support are excluded; credits have no cash value and cannot be reused.
>
> Read the [upgrade examples](https://flex-fields.bjanczak.com/docs/plans.md#upgrade-without-buying-the-same-scope-twice). Pre-v2.0 and Custom grants need an individual written quote.

> **Can I transfer my license when I sell the product?**
>
> A new legal owner does not automatically inherit your portfolio license. Product sales, entity transfers and incorporation can need transfer approval, a new grant or an agreed transition. Discuss the change before the new operator takes over. A name change of the same legal entity is different from changing the licensee.

> **How do I buy or clarify a plan?**
>
> [Buy Single Product, Unlimited Company or Enterprise Group](https://shop.bjanczak.com/checkout/buy/9035f5b4-c5a2-4b03-867d-109b48d49134) directly and select the matching plan in checkout. You do not need to submit an enquiry first. Use the [license guide](https://flex-fields.bjanczak.com/docs/request-license.md) if you need help choosing. Custom / OEM, unclear scope, upgrades and transfers require individual contact before payment: [barek122@gmail.com](mailto:barek122@gmail.com). A tax receipt alone is not the grant; keep the authenticated License Confirmation as well.

> **[Compare the plans](https://flex-fields.bjanczak.com/docs/plans.md)**
>
> Find current pricing and the scope each plan covers.

> **[Review the full license](https://flex-fields.bjanczak.com/docs/license-terms.md)**
>
> Read the actual grants and conditions.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.