Skip to main content

Capell uses essential storage for sessions, security, and interface preferences. Analytics and marketing storage stay off unless you accept them.

Cookie Policy

Capell vs a custom Filament admin

A custom Filament admin is enough for small internal editing. Capell is the stronger fit when the public site needs CMS behavior that would otherwise be rebuilt project by project.

Built on Filament Stop rebuilding the basics Extend, never fork

Capell vs a custom build, side by side

Both run on Filament. The difference is how much of a content platform already exists on day one.

Area Capell A custom Filament admin
Starting point A maintained CMS on Filament An empty Filament panel you extend
Pages and layouts Page types and a layout builder included You design and build the schema
Publishing Draft, preview and publish workflow built in You implement states and previews
Operations Redirects, cache, SEO and diagnostics included Wired up per project
Public output Editor-safe rendering proven by tests Your responsibility to get right
Maintenance Upgraded as packages with verified compatibility Owned and maintained by your team forever

New to Capell?

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.

What is Capell?

Capell is a Laravel CMS built on Filament for content-heavy websites: structured pages, reusable layouts, approved widgets, editor-safe publishing, public delivery, and package-led growth.

Tour Capell
Is Capell meant for designers?

Designers can work with Capell through themes, approved layouts, visual direction, and frontend systems while the CMS keeps content structure stable.

View themes
Is Capell made for developers only?

No. Developers get the Laravel architecture, but site owners and editors get the practical value: manageable pages, safer publishing, and visible site operations.

See owner fit
How can Capell help me out?

Capell 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 features
Can I use Capell with my existing website?

Yes, 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 path
What happens when I install Capell?

You install Core, Admin, and Frontend first, verify the Filament workspace and public output path, then add LayoutBuilder, themes, and other extensions only when the site needs them.

Read docs
How can we reach you?

Use the contact path when you need help deciding fit, discussing a project, reporting a concern, or talking through package and marketplace work.

Contact Capell
How can I work with Capell?

You 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 path
How can I help Capell?

Use Core, share feedback, donate, buy first-party packages, purchase marketplace extensions, or author trusted packages for other Capell teams.

Support Capell