Skip to main content
Capell home
Live demo

Find a Capell extension

Browse current listings See the suites

A useful extension removes work the team already understands. Open its listing for maturity, supported versions, data and migration impact, visible surfaces, access terms, support, and removal guidance.

Stable listings are current adoption options; a listed Beta requires an explicit decision. Packages still in preview are product direction, not an install option.

Stable or Beta status Visible production impact Public or paid access
CMS capture: package inventory Installed capabilities stay inspectable. The real extensions screen makes package ownership, version state, and operational actions visible inside the CMS.
CMS capture: page structure Page families are defined once. A real Filament screen showing the registered page structures editors use instead of rebuilding content rules inside each page.
Diagnostic capture: operations health Health checks name the problem and the next action. A real Diagnostics package capture showing setup and operational checks before a release becomes a production incident.

Real Capell product screens

Actual Capell CMS extensions screen showing installed packages, package descriptions, versions, and management actions.

Extensions: Actual Capell CMS extensions screen showing installed packages, package descriptions, versions, and management actions.

Add features with Composer packages

A package publishes its own routes, jobs, settings, and Filament resources through Capell's manifest-declared extension points. Composer resolves the dependency; the manifest declares what the package touches, what it caches, and what it costs to render.

Nothing here bypasses Core. A package that outgrows its boundary is a signal to review it, not a reason to fork Core to make room for it.

Find the next useful capability

Choose packages around the work your site needs, then inspect their current scope and evidence.

The extension catalogue shows what can be added to a Capell application. It is most useful when you arrive with a requirement: review a change, arrange approved page components, improve discovery or connect another workflow. Use the filters and package details below to check status, licence and dependencies before adoption.

The buying decision is about the work a package can take off your team's list. Look for the editor action, visitor experience or operating task it supports, then check the configuration and maintenance your application still owns. Each listing brings together its capabilities, product captures and adoption details so you can compare that requirement with the package's published scope. Suites help when several of those capabilities belong to the same workflow.

Extensions: Actual Capell CMS extensions screen showing installed packages, package descriptions, versions, and management actions.
Extensions: Actual Capell CMS extensions screen showing installed packages, package descriptions, versions, and management actions.

Use the marketplace when a repeatable package can remove a named piece of CMS work. The live listing is the adoption contract: current maturity, compatibility, surfaces, data access, migrations, jobs, support, licence, access, and removal guidance.

Capell Foundation is distributed through public MIT-licensed packages. Paid catalogue packages remain proprietary commercial software and use entitlement-scoped Composer access. Stable and explicitly accepted Beta listings are current options; preview-only packages are not.

Marketplace listings can describe install impact and data access. Check the evidence for the exact release against the published review standard; a listing alone does not establish that it passed.

Before installation

  • Confirm the package solves a requirement the team already understands.
  • Inspect what changes for editors, visitors, data, deployment, and operations.
  • Check compatibility, support, advisories, access, and retained data.
  • Test the representative workflow and removal path away from production.

Choose by the job

Keep a reason and an owner for every additional dependency.

A package earns its place when it solves a concrete requirement. Review the current entry, trial the workflow and identify its configuration and ongoing maintenance. A broad catalogue is a range of choices, not a recommendation to install everything.

Inspect permissions and public behaviour with representative records. Screenshots provide orientation, while a non-production trial establishes whether the workflow fits your application. Read dependencies before combining packages.

Extension workflow

See package-led capability in practice

Follow package selection, review signals, an Admin workflow, and the explicit extension boundary that keeps project code maintainable.

A narrated walkthrough of Capell's package-led extension model.

Captions (SRT) Read transcript Watch on YouTube Browse extensions

Read the evidence

Distinguish shipped capability, beta scope and planned work.

Use package status and dated release evidence to decide what you can responsibly depend on. Beta capability may be useful in a controlled trial, but its current limits belong in the project decision. Planned functionality should not be presented as already available.

Review upgrades and removal before installation becomes permanent. Keep an inventory of pages and workflows using the package. That makes future maintenance a bounded task rather than a search through an unfamiliar site.

Package status and requirements

Stable and Beta listings are current install candidates when the project's access allows them. Incomplete work stays preview-only or withheld until its marketplace readiness has been assessed.

Compare extension paths Submit an extension
What a listing is built from: one package manifest 
capell.json                    # capell-app/access-gate, manifest-version 3
  version        "1.0.0"
  product        { group, tier, bundle }          # where it sits commercially
  surfaces       ["admin", …]                     # where it is allowed to appear
  dependencies   { requires, supports, conflicts }
  contributes    [ 14 entries ]                   # every resource, page and widget it adds
  database       { migrations, settings, requiredTables }
  permissions    [ 13 entries ]                   # e.g. "View:Area"
  security       { riskTier, publicSurface, sensitiveData,
                   publicOutput, externalHttpClients, adminSurface }
  performance    { frontendRenderBudgetMs, adminQueryBudget,
                   cacheTags, cacheSafety }
  healthChecks   [ 1 entry ]
  commercial     { proposedLicense, supportPolicy, … }

Real fields from a released package's capell.json, shortened for reading. Because the listing renders this record, install impact, public surfaces, permissions and removal effect can be read before installation instead of discovered after it.

Access Gate on one member area Adopt Access Gate on one member area. Name the requirement: gate one download area behind login. Read the manifest record above: three surfaces, thirteen permissions, its migrations and required tables, and a security block declaring public output and admin surface. Install it, grant the one permission the area needs, gate the page, then check the public response as a signed-out visitor. Removing the package removes the resources and permissions it contributed. See the package lifecycle
Stable or explicitly opted-in Beta Stable is the settled adoption path. Beta needs an explicit acknowledgement. Preview-only packages are not current marketplace installs. Check the maturity boundary
Compatibility and footprint Check supported Capell, Laravel, and Filament versions alongside migrations, jobs, data access, permissions, and visible output. Review a package lifecycle
Capell Foundation or paid catalogue Capell Foundation packages are MIT-licensed and install without Capell credentials. Paid packages use separate commercial terms and require the matching active entitlement for protected access. Check package access
Support, advisories, and removal Confirm the responsible author, support route, maintenance expectation, security notices, and what happens to retained data when the dependency is removed. See the trust checks

Browse by job

Use a group to narrow the search to the area of work you need.

Themes
Foundation visual.
Foundation Start here for common page composition, reusable content, navigation, media, articles, and taxonomy. Adopt only the parts the site's publishing model needs. View this item
A genuine Capell publishing review captured before publication.
Publishing Workflow Suite When Publishing Studio is installed and licensed, it supports coordinated review and release workflows. Document Lifecycle has Stable maturity but remains preview-only until public Marketplace access is approved. View this item
Search and SEO: actual Capell page types screen showing structured page definitions and their public routes.
Search and SEO Choose from search and discovery packages when the site needs stronger metadata, crawl controls, broken-link recovery, internal search, or publish-time checks. View this item
Extensions: Actual Capell CMS Pages index showing its SEO Overview and columns for Page, Publish status, Updated at, Page type, and PageSpeed.
Growth and Marketing Campaign, form, newsletter, analytics, and email packages belong together only when the team owns the complete journey from landing page to follow-up and reporting. View this item
Performance visual.
Performance Performance packages help with public-page caching, invalidation, and asset delivery. Review measured route impact before adding them to an already fast application. View this item
The genuine Foundation public homepage, showing the theme on realistic published content.
Themes Use a theme as a maintainable starting point for a redesign, then check its real previews, tier, supported content shapes, and replacement path. View this item
Actual Capell system health page showing runtime and dependency checks.
Operations and Security Site Monitor is a free first-party package for availability and expiry checks running from your application host. Verify the current release and configure its scheduler, queue worker and notification integration. Privacy Center and Document Lifecycle have Stable maturity; Exception Reports is Beta. Those three remain preview-only. View this item
Agent Bridge Prompt Builder preparing context for an authorised operation; this capture does not demonstrate execution or token enforcement.
AI and Automation Use the current visible marketplace listings to compare AI and automation packages. Agent Delivery, Automation Studio and Public Actions have Stable maturity but remain preview-only, not current Marketplace install options. View this item
Extensions: Actual Capell CMS Pages index showing its SEO Overview and columns for Page, Publish status, Updated at, Page type, and PageSpeed.
Sites and Self-service Use the current visible marketplace listings to compare site and self-service packages. Customer Portal, Knowledge Base and Bookings have Stable maturity but remain preview-only; Content Library is design intent that is not yet in the release catalogue. View this item

Preview packages not yet listed on the marketplace

Use these entries to understand possible future capability and to give roadmap feedback. They are not available marketplace installs. Depend only on packages with an approved visible listing and an explicit Stable or Beta maturity label.

Publish clean content for AI agents Stable, preview-only: Agent Delivery would help teams prepare public-safe structured content for integrations they own. It would not add a Capell-hosted delivery API. View this item
Connect workflows without fragile controllers Stable, preview-only: Automation Studio would connect package events and registered Actions through idempotent, durable, audited orchestration. View this item
Safe public-input boundaries Stable, preview-only: Accept public input through a safe boundary. Public Actions would validate and de-duplicate submissions, screen spam, protect outbound requests, sign webhooks, retry delivery, and record each dispatch attempt. View this item
Run experiments inside Laravel Stable, preview-only: Experiments would add server-side targeting, sticky weighted allocation, conversion tracking, and statistically gated winner reports to Capell pages and campaigns. View this item
Build privacy evidence into the site Stable, preview-only: Privacy Center would record consent, policy acceptance, retention rules, and access, export, or deletion requests as a queryable system of record. View this item
Control document versions and acceptance Stable, preview-only: Document Lifecycle would publish content-hashed document versions and record which actor accepted which version and when. View this item
Give customers one self-service home Stable, preview-only: Customer Portal would assemble billing, documents, registrations, gated resources, newsletter preferences, and support requests contributed by installed packages. View this item
Ship a structured help centre Stable, preview-only: Knowledge Base would add collections, cacheable documentation routes, reader feedback, sanitised HTML, and typed AI-readable payloads without authoring leakage. View this item
Reuse real business content Design intent, not yet in the release catalogue: Content Library would store reusable case studies, testimonials, team members, services, FAQs, resources, partners, locations, and logos. View this item

Role scenarios

What to inspect before adding packages

Checks for package scope, compatibility, ownership, and removal before adding capability.

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

Actual Capell Layout Builder for the agency workflow described.

Check an extension manifest before installation

Inspect a package manifest before installation and verify its declarations for public surfaces, sensitive data and outbound HTTP. The build audit should reject an incompatible API version or unsafe cache claim.

Read more

It reads like an app-store privacy label for a plugin, so agency teams vet a package before it lands near a client. The build audit backs it up: it fails at CI if a cacheable package would poison a shared cache or pins an incompatible API version, catching the mistake before a live site does.

Trade-off to assess: This assumes teams are willing to work in Laravel packages at all. A team that only wants a hosted admin with no code ownership will find the whole model heavier than they want.

Run this yourself in the demo

Agency Director

Evaluator scenario for an agency director

One reviewed Laravel package catalogue

Use a smaller catalogue, reviewed as one Laravel system. First-party, publisher verified, Stable, Beta and Capell reviewed remain separate signals.

Capell reviewed applies only to the exact package release that passed automated checks, AI-assisted analysis and authorised human sign-off. Changed code must pass again, and review reduces risk rather than guaranteeing permanent security.

102 of 102 eligible first-party releases currently carry exact-release review evidence.

  1. No database queries in public views

    Public Blade receives complete hydrated render data without Eloquent, DB access or lazy-loading fallbacks.

    Automated AI-assisted

  2. Declared package boundaries

    Dependencies, contributions, migrations, permissions and removal behaviour must match reachable package code.

    Automated AI-assisted

  3. Exact-release accountability

    Artifact and manifest hashes bind the evidence to one version before a human reviewer owns the release decision.

    Automated AI-assisted Human sign-off
Loading section
Loading footer