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

How to read each state

  • Open for voting is exploratory and gathering evidence.
  • Planned means the need is accepted while timing and interfaces remain open.
  • In progress means implementation has started and details can still change.
  • Shipped means a release is available to evaluate.

The live status strip combines open and planned items in one count.

Live status

See the balance of shipped and unfinished work

Use the figures for orientation, then open the individual item for its current state and date. Votes show which problems matter most to the community.

1
Shipped

Available to evaluate, with release detail in What's New and the changelog.

1
In progress

Work has started, but scope and release timing can still change.

12
Open or planned

Open for voting or accepted for planning, with current context on each item.

0
Community votes

Interest recorded by the community to help Capell understand priority.

Roadmap

Available, planned, or still exploratory?

Check the current state and milestone date, then add your vote when the problem matters to your work.

A team working at computers beneath a branching diagram of connected website page layouts.
Open
3
Planned
10
Votes
0
Show
For
Community priority

Items with the most votes

13 items
In progress Owners

Marketplace trust ledger per extension

Each extension gets a visible ledger for compatibility, support terms, security review, update notices, advisories, install telemetry, and licence state.

Planned Developers

AI and agent delivery

Agent-assisted delivery capabilities grouped around safe discovery, validation, preview, and controlled application workflows.

Planned Developers

Automation and integrations

Automation and integration capabilities for connecting content operations to the wider Laravel application and delivery stack.

Planned Owners

Experimentation and growth

Experimentation, measurement, and growth capabilities that preserve structured content and developer-owned delivery.

Planned Agencies

Trust, compliance, and operations

Operational trust, compliance, governance, and recovery capabilities for teams running long-lived Laravel applications.

Planned Owners

Customer self-service

Customer-facing account and self-service capabilities that remain integrated with the application the customer owns.

Planned Package authors

Verified author program

Authors get a clear route for submitting packages, proving support coverage, passing review, and earning trusted extension status.

Planned Developers

Extension compatibility matrix

Package pages show supported Capell, Laravel, Filament, PHP, and dependency versions so teams can check fit before installing.

Planned Developers

Security advisory inbox

Customers can see relevant package advisories, update notices, affected instances, and recommended action from their account.

Planned Owners

Marketplace install-impact review panels

Package detail and install-flow screens show migrations, routes, data access, support path, and compatibility before a buyer installs.

Open for voting Developers

Install dry-run receipts

Before install, Capell produces a receipt for migrations, routes, permissions, widgets, configuration, and rollback expectations.

Open for voting Owners

Licence and entitlement dashboard

Customers can inspect package access, licences, renewal state, install approval, private docs access, and suspected unlicensed use signals.

Open for voting Agencies

Guided migration assistant launch path

A guided path for importing existing marketing content, mapping records, reviewing redirects, and proving public output before launch.

Release channel

Read the package release channel

Stable means a package is generally available as a tagged release. Beta is an explicit opt-in to that individual package's changing behaviour. Labs and unlisted packages are not install options.

Check the package listing, compatibility, and release record before adoption.

Verify a shipped release
Shipped

Available

A tagged release is available to evaluate and carries dated release detail.

  • Check What's New and the changelog

    Confirm the version, compatibility, and any required action before adoption.

In progress

Under way

Implementation has started, but scope, interfaces, and release timing may still change.

  • Follow implementation progress

    Use the item for current context while the scope and interfaces take shape.

Not available

Planned or exploratory

Planned items have an accepted need; open items are still gathering evidence and votes.

  • Planned means the need is accepted

    Priority, scope, and timing can move as dependencies and research change.

  • Open means exploratory

    Vote or add context when the underlying problem matters to your team.

Loading footer