The supported stack before installation
Install Capell Foundation from Packagist, then verify the application against the same runtime and package constraints used by production. Paid packages have published terms, while public checkout is open.
Marketplace packages can have narrower compatibility requirements. Review the listing and keep an active entitlement before adding a paid package.
PHP 8.4 Laravel 13.x PHP-FPM and Octane
Know what you will operate
Check the supported stack and agree who owns maintenance before adopting Capell.
A CMS decision includes the application and people around it. Capell runs within Laravel, so hosting, dependencies and deployment remain part of your team's operating responsibilities. Use the current requirements below to establish compatibility, then decide where product support ends and project maintenance begins.
The current stable 1.x release requires PHP 8.4 and supports Laravel 13.x with Filament 5. Composer resolves the exact supported Filament release from the package constraints for the Capell version you install. It supports PHP-FPM and Laravel Octane.
Support for 1.x targets the current stable Capell release and the latest patch of each supported PHP and Laravel minor.
Publishing Studio has published annual terms, while public checkout is open. Paid marketplace packages require an active entitlement and may publish narrower compatibility requirements.
Check the actual environment
Compare supported versions with the application you will maintain.
Inspect the application's PHP runtime, dependency lock, database and required services. A development machine and a deployment server can run different versions, so verify both rather than relying on one successful install. Use the published requirements as the source of truth when they change.
Trial the intended package set together and run the relevant application checks. Optional packages may introduce their own configuration or service needs. Record those requirements in the project handover so another developer can reproduce the environment.
Make support responsibilities clear
Give the team a practical route from a problem to a reproducible report.
Separate a package defect from application customisation, hosting configuration and editorial questions. A useful support report includes the affected version, the intended behaviour, a minimal reproduction and the relevant error details without credentials or personal data.
Read the current support terms for scope and entitlement; this guide does not replace them. Agree who can investigate the application and who can apply a correction. Keep urgent public-content recovery distinct from a longer technical support conversation.
Support during the 1.x release line
Support for the 1.x line targets the current stable Capell release and the latest patch of each supported PHP and Laravel minor. Upgrade to the current stable release before requesting a defect or security fix.
Next step
Support has a route for each need
Marketplace entitlement questions and project implementation work have different boundaries.
Capell Foundation source is public, and its packages are available through public Packagist releases. Public MIT-licensed Composer packages. An active entitlement provides protected downloads, installs, updates and support. Versions already downloaded or installed remain usable after expiry under the applicable terms.
Use the support request flow for account, entitlement or package support. Use the public repositories for reproducible foundation issues, and use the security disclosure route for vulnerabilities. Read the support terms for response targets and boundaries. For architecture, migration or implementation work, contact Capell with the Laravel and Capell versions involved.