Skip to main content
Capell home
Live demo

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

Leave with a site plan your team can use

The questions turn an early idea into an ordered scope with visible package and theme costs. Nothing is deployed from this introduction: the saved blueprint continues either to a local Laravel handoff or to resources in the Laravel Cloud account your organisation owns.

Start your site: actual Capell page types screen showing the structured content definitions available to a new site.

Work through seven decisions: starting point, site purpose, delivery route, capabilities, page order, theme and colours, then visibility and optional paid additions. The choices stay in the session while you review them. Sign in only when you are ready to save the blueprint and continue to the selected delivery path.

A local route produces a Laravel handoff. The Cloud route prepares a launch in your organisation's own Laravel Cloud account. Your organisation owns the Laravel Cloud resources and pays Laravel Cloud charges. Paid marketplace selections are shown before checkout rather than hidden inside the build.

Optional assisted onboarding

Capell Foundation is a stable 1.x release and can be installed without joining a programme. Assisted onboarding is an optional route for teams that want help assessing package fit, planning installation, or discussing Capell Membership while public online checkout remains closed.

What to include

Tell us about the project, use case, current CMS, delivery preference, target install date, named technical owner, preferred onboarding date, and a suitable follow-up date. A testimonial or permission to publish project details is not required.

What we commit to

When we accept an onboarding request, we agree the scope, support route, response expectations, and any commercial terms before work begins.

Package maturity

Each companion package keeps its own Stable, Beta, or Labs maturity label. Beta access is an explicit opt-in for that package only and does not change the released status of Capell Foundation.

Privacy and next step

Send only the project and contact details needed to assess fit. Read the privacy notice before contacting us. In your message, begin with “Assisted onboarding” and include the relevant fields above.

Loading footer