Skip to main content
Capell home
Live demo

We use cookies for essential features and optional analytics.

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

Stop maintaining a second CMS inside your Laravel app.

Capell is in assisted design-partner beta. Foundation is £0 under the MIT licence, the live demo is open, and checkout remains closed while the commercial path is validated.

Open the live demo Plan a Capell site
A real Capell review workspace showing a Page ready for an editorial decision.

Capell keeps publishing inside the Laravel application, gives Pages a recoverable history, and leaves the public frontend with the team that builds it.

The real CMS test starts after the first launch

Capell records Page changes because client work rarely fails at the neat moment a CMS comparison table describes.

The other path

The Capell path

  1. Friday, 4:55pm

    The other path

    A rushed edit replaces the last known-good Page and leaves the team comparing screenshots.

    The Capell path

    The save becomes another Page event, so the earlier state remains available.

  2. Who approved this?

    The other path

    Chat logs and memory become the audit trail.

    The Capell path

    The Page history records the sequence; Publishing Studio adds reviewer assignment and approval.

  3. Roll it back

    The other path

    Recovery means reconstructing content or restoring more data than the Page that changed.

    The Capell path

    Preview the Page diff, validate the target state, then restore or roll forward.

  4. Upgrade day

    The other path

    Project-specific glue turns framework updates into archaeology.

    The Capell path

    Installer, upgrade and doctor commands keep the lifecycle explicit and testable.

  5. Handover a year later

    The other path

    The next developer inherits conventions that exist only in the previous developer's memory.

    The Capell path

    Page, layout, package and public-rendering boundaries remain visible in the Laravel codebase.

Keep the smaller path when

  • The site has a few stable pages.
  • The existing CMS already fits the team.
  • A separate content service is a firm requirement.

Choose Capell when

  • Publishing risk belongs inside the Laravel application.
  • Repeated Page families should improve together.
  • Upgrade and recovery work needs a shared contract.

What does controlled publishing look like?

Every Capell site gets drafts, preview, Page History and restore. Publishing Studio adds approvals, assignments and coordinated releases.

01

Draft

Edit the Page in a structured Filament workspace while the public version stays unchanged.

02

Review

Preview the real Page and inspect the proposed change before making a publishing decision.

03

Publish

Release the approved Page through the workflow available to that Capell installation.

04

Evidence and rollback

Read the Page history, compare states, and restore a validated earlier version when needed.

Decision ledger

Which architecture decisions make Capell different?

Six closed decisions explain what Capell optimises for and what it deliberately gives up.

We kept the CMS inside the application on purpose. Each decision is useful only when its trade-off also fits your project.

  1. D-01

    Keep the CMS coupled to the Laravel application on purpose.

    Given up
    One content service feeding unrelated applications.
    Wrong for you if
    A delivery API is a fixed requirement.
    See the frontend boundary
  2. D-02

    Record every Page change as another event instead of overwriting its history.

    Given up
    The simplicity of overwriting one current row.
    Wrong for you if
    Page-level history adds no operational value.
    Follow the publishing workflow
  3. D-03

    Add capability through reviewed Laravel packages rather than anonymous plugins.

    Given up
    One-click anonymous installation.
    Wrong for you if
    Composer review and deployment ownership are unwanted.
    See how packages extend Capell
  4. D-04

    Use a Filament workspace for editors instead of maintaining a bespoke admin system.

    Given up
    A bespoke admin design system.
    Wrong for you if
    Your editors cannot work in Filament.
    Read the Filament CMS comparison
  5. D-05

    Make installation, upgrades and diagnosis explicit commands that teams can test.

    Given up
    Hiding lifecycle work behind a hosted control plane.
    Wrong for you if
    Your team will not own Laravel operations.
    Read the upgrade guidance
  6. D-06

    Remove engineering claims when their dated evidence is no longer current.

    Given up
    Permanent claims based on an old release.
    Wrong for you if
    Dated, removable evidence feels too cautious.
    Review the current trust evidence
Current evidence

Claims with dates on them

Capell.app and the public demo run on Capell. Check the source, follow the dated evidence, and treat an absent metric as an intentionally withdrawn claim. Priority support costs £49 and is refunded automatically if the two-business-day first-response target is missed.

Which capabilities remove the next layer of CMS glue?

Redirect health monitoring Track redirect health as an operating concern instead of discove... Multisite with deletion-impact preview Manage several sites while previewing the effect of destructive... Localised media metadata Keep alt text and related media context aligned with the languag... Reviewed marketplace releases Add optional capability through Composer packages whose release... Theme system with ThemeDoctor Keep presentation replaceable and run explicit checks against th... Agent Bridge Let external agents inspect approved capabilities without granti...

Redirect health monitoring

Track redirect health as an operating concern instead of discovering dead paths from visitors.

See delivery

Multisite with deletion-impact preview

Manage several sites while previewing the effect of destructive site-level work.

Read the owner path

Localised media metadata

Keep alt text and related media context aligned with the language presented to visitors.

See content

Reviewed marketplace releases

Add optional capability through Composer packages whose release state remains visible.

Browse extensions

Theme system with ThemeDoctor

Keep presentation replaceable and run explicit checks against the installed theme contract.

Browse themes

Agent Bridge

Let external agents inspect approved capabilities without granting silent publishing authority.

See the agent boundary

Capell operations health checks covering public delivery and redirects.

Who gets the most value from this shape?

The same architecture pays back differently for delivery teams, product teams and individual developers.

Choose the path closest to the decision you need to make next.

Agencies

Standardise the operating path, not the client's design

Reuse Page, upgrade and handover conventions while each application keeps its own frontend.

Read the agency path

Product teams

Put publishing risk beside the product code

Give editors a bounded workspace and share the live demo with the developer who owns the application.

Read the editor path

Solo developers

Start with Foundation and keep the dependency visible

Install the MIT-licensed base, inspect the contracts, and add paid workflow only when the team needs it.

Install Foundation

Which decisions are still open?

How much deeper should event-sourced history go?

Pages are the supported aggregate today. Other content remains outside that promise.

How composable should blueprints become for editors?

Developer-owned structure remains the current default while the product tests safer composition.

Which operations deserve public evidence next?

New claims should arrive with a current, checkable source and disappear when it expires.

A Capell request moving from a Laravel route through a Page and blueprint into application-owned Blade output.

How does one Capell request stay inside Laravel?

One request moves through Laravel routing, a Page with event history, a blueprint and the application's own presentation. The boundary stays inspectable without a second runtime round trip.

See the frontend boundary
A real Capell readiness report showing versioned checks and their current status.

Why are upgrades a command, not a project?

capell:install, capell:upgrade and capell:doctor give teams one repeatable operating path. Agencies can apply the same checks across a fleet while each application keeps its own code, database and release decision.

The screenshot is a real readiness surface. It is evidence of the command shape, not a promise that every check will pass on every installation.

Read the upgrade guidance

When is Capell the wrong choice?

Use these questions to disqualify Capell before a pilot costs the team time.

Use the full fit guide
Do you need a separate content API?

Choose a separate content platform when several unrelated applications must consume the same content through an API. Capell is coupled on purpose: it belongs inside the Laravel application.

Can you buy Capell today?

Not yet. Capell is in assisted design-partner beta, and public checkout stays closed until the commercial canary is complete. Foundation remains available under the MIT licence.

Is Capell sensible for five client sites?

It can be when the sites share a delivery method and your team values repeatable upgrades, Page recovery and reviewed packages. Confirm the licence and package fit before standardising.

Review licensing
What about the bus factor?

Capell is founder-maintained and early. The Foundation source is MIT licensed, paid-package continuity terms are published, and the current operating limits are stated plainly.

Read about Capell
Why not build the CMS directly with Filament?

Build directly with Filament when a few resources and custom pages are enough. Choose Capell when Pages, URLs, Page history, layouts, themes, publishing and package lifecycle should share one maintained contract.

Compare the approaches
Should we stay with the CMS we already have?

Staying put is a valid outcome. Keep the current CMS when it already fits the team, the migration cost exceeds the maintenance cost, or Capell's early stage adds risk you do not need.

Compare CMS shapes
Capell publishing controls arranged around a recoverable Page history.

Try to break a Page — then restore it

Follow the Foundation recovery track: open a Page, inspect its history, preview the difference and trace the restore path.

A specific test Inspect the recovery path rather than taking a rollback claim on trust.

Open the recovery demo

Inspect the workflow, then decide whether it belongs in your Laravel app

The live demo is open; site planning is available during the assisted design-partner beta.

Agencies can use the demo as a shared evaluation path. If the timing is wrong, follow the newsletter for release evidence and checkout readiness. Foundation is £0 under the MIT licence; public checkout remains closed.

Open the live demo Plan a Capell site
Loading footer