Skip to main content
Capell home
Live demo

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

Install Capell Foundation

Choose where Capell should run

Capell is a Laravel CMS built on Filament. It stays inside the Laravel application and infrastructure your team owns, with a guided path for the first setup and direct Composer control when you need it.

Capell Layout Builder showing a page composed from structured containers and widgets in Filament.

Your Laravel application

Keep the application, infrastructure and release process in your hands

Capell installs as Laravel packages. Start with the guided setup for a clear first pass, or use the manual guide when your team wants to review every Composer and Artisan step.

Guided setup

Recommended

Install the browser-based guide, choose the foundation packages, run setup in order and remove the installer when the application is ready.

Use guided setup

Manual Composer install

Follow the package-by-package guide when an experienced Laravel team wants direct control of the application diff.

Read the manual install guide
composer require capell-app/installer

Your Laravel Cloud account

Capell prepares the deployment; you remain the owner

Laravel Cloud hosts and deploys the application. Capell prepares the app, database, environment values and initial deployment inside the Laravel Cloud account you connect.

  • Your organisation owns the Laravel Cloud account and infrastructure.
  • Capell prepares the application, database, environment and initial deployment.
  • Your organisation controls billing, access and ongoing operation.
Set up in Laravel Cloud

Production notes

Compatibility and package access

Foundation source is public in five repositories: Core, Admin, Frontend, Installer and Marketplace. 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.

Core, Admin, Frontend, Installer and Marketplace are public Packagist packages and require no Capell credentials. Use the guided browser installer or take direct Composer control.

Current releases require PHP 8.4 and Laravel 12.41.1+ in the 12.x line or Laravel 13.x. Capell supports Filament 5; Composer resolves the exact supported Filament release from the package constraints for the Capell version you install. Paid marketplace packages come later through authenticated Composer access and an active entitlement.

What Capell changes in the application

Core adds the shared content model, Admin adds the Filament editor workspace, and Frontend connects published content to public delivery. Review migrations, providers, configuration and public render hooks like any other Laravel pull request.

Verification and production reference

Verify that an editor can change one page and that an anonymous visitor receives only public HTML. The supported evaluation target is a working Foundation admin and public Page within 15 minutes in the reference environment. Network and host speed affect elapsed time; the release evidence records each phase rather than presenting the target as a universal guarantee. Use the current install guide for production commands and Laravel Cloud environment guidance for hosted deployments.

Choose the installation route that matches who will operate the Laravel application. Start with Capell Foundation, verify one editor-to-public path, then add optional capability only when the project needs it.

Video overview

See it in 50 seconds

The video follows Composer installation into Filament and then to an anonymous public response. Exact commands remain in the current install guide.

See what Capell adds to an existing Laravel application and how to verify it.

Next step

Install the foundation your team can keep

Start guided, take manual control when you need it, or try the workflow locally first.

Want to see the foundation before choosing a production route? Try the quick demo.

Loading footer