Capell uses essential storage for sessions, security, and interface preferences. Analytics and marketing storage stay off unless you accept them.
Cookie PolicyThe CMS should read like long-term application software, not a pile of hidden page-builder state.
Developers get Laravel-owned CMS boundaries, Actions, service providers, package manifests, render hooks, tests, and upgrade paths.
Extension authoring is one of Capell’s most flexible features. A package can add migrations, models, Filament resources, widgets, render hooks, policies, commands, docs, and marketplace metadata while keeping its install impact reviewable. Start with the documentation, then use the sales pages to understand where package flexibility matters for real projects.
The public product story is backed by repository signals: package inventory, theme inventory, PHPStan level, and the combined Pest tests and assertions reported by the Capell and package workflows.
56
First-party package directories currently tracked in the Capell package library.
11
Theme packages including Foundation Theme and premium theme packages.
3
Static analysis runs through the shared PHPStan configuration before release work is trusted.
991+
Combined test count reported by Capell and Capell package workflows.
5,864+
Combined assertion count reported by Capell and Capell package workflows.
If you landed here without reading the homepage, start with these questions. Each answer is short, and each one points to the deeper Capell page that explains the idea properly.
Capell is a CMS foundation for content-heavy Laravel websites: structured pages, clean admin editing, public delivery, and package-led growth.
Tour CapellDesigners can work with Capell through themes, approved layouts, visual direction, and frontend systems while the CMS keeps content structure stable.
View themesNo. Developers get the Laravel architecture, but site owners and editors get the practical value: manageable pages, safer publishing, and visible site operations.
See owner fitCapell gives repeated CMS work a proper home so teams are not rebuilding pages, URLs, layouts, publishing, redirects, cache, SEO, and package logic from scratch.
Explore featuresYes, when the project is a Laravel app or can move into one. Start with a verified install path, then migrate content and packages deliberately.
Read install pathYou install the Core foundation, verify Admin and Frontend, add LayoutBuilder and theme output, then choose extensions only when the site needs them.
Read docsUse the contact path when you need help deciding fit, discussing a project, reporting a concern, or talking through package and marketplace work.
Contact CapellYou can install Capell, build a site on it, author packages, create themes, or use it as the CMS foundation for long-running Laravel projects.
Developer pathUse Core, share feedback, donate, buy first-party packages, purchase marketplace extensions, or author trusted packages for other Capell teams.
Support Capell