Choose which optional cookies Capell may use.
Required for Capell to work — login, security, page rendering.
Anonymous usage telemetry to improve editor performance.
Personalization for the Capell marketing site.
It does not ask you to move the site into a hosted builder, duplicate routing in a separate frontend, or surrender the templates that make the product yours. Developers keep the public output, editors get a structured workspace, and owners keep future redesign work inside the codebase they control.
Capell's frontend promise is simple: the CMS does not take over the frontend. Laravel teams can use Blade, Livewire, Inertia, Vue.js, package themes, or a custom stack while Capell provides the content model and editor workflow.
That matters when the public site has performance, accessibility, brand, or product requirements a generic builder cannot understand. Editors get a real CMS, but visitors still receive HTML the application team controls.
Capell feeds structured content into the frontend. It should not become the frontend.
For frontend teams, the decision is whether the CMS can provide structure without shipping generated markup or taking over the stack.
Keep frontend ownership inside Laravel while Capell adds structured content, Filament editing, and public delivery without forcing a hosted frontend.
Start with the practical question: what does the visitor or editor need to do next? Capell keeps that answer tied to the Laravel app, with shared structures for repeated pages and enough room for custom work when the project genuinely needs it.
Capell provides structured content while Blade, Livewire, Inertia, Vue.js, Vite, and Tailwind CSS remain project choices.
The stack stays recognisable because Capell is installed into the application, not bolted on as a separate platform.
This is the short version. Use the full comparison pages when you need a deeper fit decision.
| Decision | Capell | Hosted builder | Headless CMS |
|---|---|---|---|
| Templates | Laravel project owns the public templates | Builder or hosted platform often owns page composition | Separate frontend app owns templates |
| Content schema | Defined for the Laravel CMS boundary | Often shaped inside the editing tool | Defined in a separate content service |
| Editor changes | Signed-off widgets and page types protect the public design | Editors may shape layout directly in the visual tool | Editors depend on preview and frontend wiring |
| Deploys | Normal Laravel release path | Platform release behavior | CMS deploy plus frontend deploy |
| Best fit | Laravel sites that need editable structured pages | Small sites where visual control matters most | Many channels consuming one content API |
Yes. Editors work with approved page types, widgets, media, previews, URLs, and publishing flow while templates remain in the Laravel project.
Yes. Capell stores CMS records in the Laravel application's database, so application code can work with the content model directly where that is the right boundary.
Capell is not a hosted SaaS CMS. Leaving still takes engineering work, but the content, code, database, and deployment path remain in your Laravel estate.
No. Capell can prepare structured render data for Blade, Livewire, Inertia, Vue.js, cached HTML, APIs, or a custom stack.
No. Headless wins when many channels need one content API. Capell fits when the Laravel app owns the website and needs a real CMS inside that boundary.
If the ownership question is still open, start with the comparison pages and migration guides before installing anything.
Ownership matrix The CMS should support the frontend boundary, not replace it.
Reviews
Short notes on keeping public delivery with the frontend team.
Frontend stays with the delivery team
“Capell Frontend keeps public presentation inside the Laravel build, so a studio can ship structured CMS content without handing design and markup to a hosted platform. The team that sells the frontend still owns it.”
CMS content, your Blade and Tailwind
“For a technical lead, Capell Frontend keeps public rendering in the Laravel build: pages come from CMS structure but ship as the team's own Blade, components and Tailwind, not a locked template engine. Output stays plain HTML the team can inspect.”
A public site that stays fast and yours
“For a site owner, Capell Frontend means visitors get a site built and tuned by your own team rather than a generic hosted renderer. Look, speed and accessibility become decisions your team controls, not platform defaults.”
Capell learning journey
Capell is a Laravel CMS split into four parts: Core, Admin (Filament), Frontend, and Packages. See how they fit your project.
Frontend, rendering, SEO, performance, and deployment.
