Skip to main content
Capell home
Live demo

We use cookies for essential features and optional analytics.

Manage cookie preferences

Choose which optional cookies Capell may use.

Essential
Always on

Required for Capell to work — login, security, page rendering.

Analytics

Anonymous usage telemetry to improve editor performance.

Marketing

Personalization for the Capell marketing site.

Cookie policy

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
Open the live demo Install Capell Foundation
Composer output: core package Capell installs as Laravel packages. Actual composer show output captured from this application, with the local repository path and build reference omitted.
CMS capture: package inventory Installed capabilities stay inspectable. The real extensions screen makes package ownership, version state, and operational actions visible inside the CMS.
Public output: cache hit Public HTML stays separate from the admin. This anonymous frontend capture proves the output boundary: cached public HTML with no editor selectors, model identifiers, or signed authoring URLs.

Redacted terminal capture of Composer showing the installed Capell core package, its PSR-4 namespace, PHP requirement, Filament support, and Laravel dependencies.

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 Foundation from paid package access

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.

Inspect before you adopt Read the Foundation source and install its MIT-licensed Packagist packages without Capell credentials. See the platform
Fetch only entitled packages Protected packages resolve through authenticated Composer access after the team checks compatibility and install impact. Browse the marketplace
Installed packages keep running Expiry does not disable the current installation. New protected downloads, installs, updates and support require active access. If Capell permanently stops trading, existing customers receive protected first-party package source under a perpetual fallback licence allowing continued use, modification, maintenance and deployment. Review pricing terms
Rehearse the route out The operator controls the application data, media, source code, and configuration. Rehearse any move against the target environment, and treat database and media backups as a separate operator responsibility. Read the export-and-exit runbook

Next step

Review the 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.

Read the MIT licence Install Capell Foundation
Loading footer