Skip to main content
Capell home
Live demo

Choose which optional cookies Capell may use.

Essential cookies are always on for login, security and page rendering.

Read the cookie policy
Optional cookies

See the product through real screens

Use these screens to judge visible output and workflow before opening the demo or a package listing. They come from Capell itself, not customer projects or evidence of independent adoption.

First-party examples Linked sources Visible product output

Tour Capell's content model, Filament workflow, public rendering boundary, operations, and extensions.

Watch on YouTube
Launch film

The launch film: recovery, ownership, and release scope

Every page save appends a full-state revision, so Tuesday's mistaken edit can be compared field by field, rolled back, or rolled forward with its history intact. Page types, layouts, URLs, and publishing rules stay structured records in your own Laravel application, edited in a Filament admin and rendered by your own frontend. Capell arrives as Composer packages: a free, MIT-licensed Foundation plus catalogue extensions reviewed release by release, so you can read what each one migrates, touches, and removes before it ever installs. Capell 1.0 is available today.

Three questions answered in order: recovery, ownership, and what each package changes, ending on caches, queues, scheduler health, and launch readiness on one screen.

Capell film

Websites don't stand still

The film shows Capell the way it behaves. The original site is typed by hand as structured Laravel code. When an urgent feature arrives, Agent Bridge holds the agent's proposal at a typed boundary with schema, policy, and private preview until the developer reviews the diff, the types, and the tests, and approves the release personally. On launch day, cached HTML carries the crowd while the authoring system stays out of every public request, and when the event changes, the dependency map can refresh just the pages that used it while everything else keeps serving. And when someone edits the wrong page, Page history brings it back.

A short film: a coffee-shop brief, a hand-built first site, one urgent feature proposed by an agent and approved by the developer, launch traffic on cached HTML, a selective cache refresh, and a calm recovery.

Every image should justify its place by showing a visible Capell result and linking to the page or listing that explains it. The collection deliberately contains Capell's own product work rather than implying a customer showcase.

Loading footer