Extension points make a change possible; the package manifest, tests, public surface, and operational owner decide whether it is safe to adopt.

Choose a path

Add one capability without reopening Core

Start with install impact if you are adopting a package, the developer lifecycle if you are building one, or the authority boundary if AI will assist. Each path shows what changes in the application and where the extension must stop.

Packages See how Capell can grow through maturity-labelled Laravel packages for publishing, automation, privacy, self-service, AI delivery, search, and operations. Choose an extension path
Building an extension The developer lifecycle: extend the CMS through packages and extension points instead of forking the application. Choose an extension path
AI-proposed work The authority boundary: typed, permission-aware tools let an agent propose structured work without holding publish rights. Choose an extension path

Prepare a package for reviewed submission

Author applications and package submissions can be prepared now; public third-party listings and paid third-party commerce are not open.

Start with a named customer job, scaffold the package through the supported extension tooling, document install and removal impact, run the package audit, and name the people responsible for support and security. An approved author profile allows submission for review; it does not promise publication, sales, earnings, a commission rate, or a payout date.

The current public catalogue is first-party only. Third-party applications are waitlisted while publication policy, legal responsibility, tax, payouts, support, and removal operations are approved.

Apply for author review Read the package authoring guide

Next step

Add capability when the project needs it

Capell Foundation is MIT-licensed and free. Paid catalogue packages are licensed per project, so the extension budget follows the capability you actually install.

Price the extension catalogue

Role scenarios

What to inspect in Capell Core

Checks for shared content structure, extension boundaries, and change over time.

Role-based checks drawn from product capabilities and fit boundaries.

Laravel developer representing this editorial scenario.

An AI cannot deploy from a single call

Inspect the content schema and Agent Bridge together. A mutating agent call should return a preview and single-use confirmation token, never deploy from the first request.

Every mutating MCP Agent Bridge call uses a two-step handshake: preview plus a single-use token, followed by a destructive-confirm call carrying the same payload fingerprint. Replay is blocked and agent actions enter a secret-scrubbed audit trail; AIOrchestrator is a separate optional provider-calling capability.

Alternative fit: If a couple of stable fields are the whole job, one hand-built Filament resource is lighter. This pays off once the content structure keeps growing and machines start touching it.

Site owner representing this editorial scenario.

Test Capell Core with a site owner

Change a page several times and reconstruct an earlier state from its event history. The record should retain who changed what while the site remains owned Laravel code rather than a lapsed subscription.

Expected evidence: That append-only history means site owners can see who changed what and reconstruct any prior version, which is database-of-record territory most CMSes never touch. No subscription can lapse and take that record with it, and three years out site owners are not hostage to anyone's pricing change.

Choose a lighter option when: Owned code still needs hands. Site owners keep a Laravel developer for upgrades and installs, and if teams want a truly zero-maintenance hosted product this is not that trade.

Agency team member representing this editorial scenario.

Capell Core: an agency director acceptance check

Trace a page through its layout, theme, media and URL relationships, then change one shared dependency. The content graph should show which client surfaces are affected before work begins.

Verify in the product: That content graph means agency teams can reason about what a change reaches before agency teams make it, which keeps scope from creeping across a book of sites. After handover the client owns readable Laravel code with that structure intact, so there is no mystery box waiting to become their problem later.

Trade-off to assess: A one-client shop chasing a single wildly custom build gets less from the repeatability. This pays back across many sites, not on a single novel one.

Manage cookie preferences

Add one capability without reopening Core

Prepare a package for reviewed submission

Add capability when the project needs it

What to inspect in Capell Core

Capell

How it works

Why Capell

Extensions

View all 78 extensions

Extensions

Extension suites