Know what you can inspect, use and keep
Inspect each Foundation codebase directly: Core, Admin, Frontend, Installer and Marketplace. These five public repositories and their public Packagist packages are released under the MIT licence.
Your application code, content and frontend remain yours, in infrastructure you control. Paid packages use authenticated Composer access linked to the customer organisation and are governed by their applicable commercial terms.
Capell Foundation source Public Packagist packages Customer-owned application and content
Know what you can keep
Distinguish the open-source foundation from paid packages before depending on them.
Capell Foundation uses the MIT licence; paid packages have their own commercial terms. The useful question is what your organisation can install, maintain and retain under the current documents. The explanation below helps you find those documents without replacing or extending their wording.
Capell Foundation consists of five public, MIT-licensed Composer packages: Core, Admin, Frontend, Installer and Marketplace. Paid marketplace packages are separate proprietary commercial software governed by their applicable terms and entitlement.
What remains yours
Your application code, content and frontend remain yours. They stay in the repositories, database and infrastructure your organisation controls. Capell does not become the owner of the customer application.
How Foundation is licensed
Core, Admin, Frontend, Installer and Marketplace are public to inspect and install under the MIT licence.
How paid packages arrive
Paid marketplace packages use authenticated Composer access. The customer organisation needs an active entitlement for new protected downloads, installs, updates and support. Packages already installed keep running after that access expires under the applicable terms.
Before production
- Review the MIT licence and any applicable paid-package terms.
- Confirm the supported PHP, Laravel and Filament versions.
- Check the install impact of every selected package.
- Confirm the customer organisation and environments covered by paid access.
Separate the licences
Check the actual package rather than applying one rule to the whole catalogue.
A Foundation installation and a paid workflow package do not have the same licence. Review each selected package's current entry and the governing terms. Keep the licence record with the application's dependency and handover information.
Do not infer a package's entitlement from its source availability, an old screenshot or a suite name. The catalogue and current terms are the authority. If the proposed use falls outside the published scope, resolve that before adoption.
Plan for continuity
Read the published commitments alongside the application handover.
The continuity commitments explain the product's stated response to retirement; they do not replace the licence or guarantee every future service. Follow the current documents below for the actual wording and dates.
Your organisation still needs an application maintainer, deployment access and a recoverable content environment. Retain the dependency lock and operating guidance so continued use is practical as well as legally understood.
Foundation and paid package access are separate
Foundation packages install from public Composer repositories under the MIT licence. Paid packages remain proprietary commercial software. Composer credentials do not extend paid access beyond the customer organisation and environments covered by the entitlement.
What happens if a package is discontinued
If Capell discontinues a first-party package, that package's source is released under the MIT licence. This is a term, not an intention.
Ending a paid entitlement does not stop an installed package from running. Protected downloads, updates and included support end after the entitlement and its grace period; the software you already installed continues to work.
Foundation is distributed under the MIT licence and does not expire.
Next step
Terms for the packages you choose
Read the Foundation MIT licence and any applicable paid-package terms, then verify compatibility before production use.
Foundation is MIT-licensed. Paid packages have separate commercial terms and entitlement requirements. Review the terms that apply to your package set, then use the install guide to verify the supported stack.