Choose a practical first step for your site
Capell adds page editing, preview and history to a Laravel application. Start with the delivery route your team can operate, then agree the pages and capabilities the project needs. Nothing is deployed from this introduction.
The guided site-planning builder is currently unavailable. The installation and Laravel Cloud routes below are available.
Start where your team can succeed
Choose a demo, local installation or deployment trial that answers the next real question.
You do not need a complete production plan to investigate Capell, but the first step should have a purpose. Use the demo to inspect editorial work, install Foundation to test the application fit or prepare deployment when the team is ready to operate a site. Keep assisted onboarding separate from the product's required setup.
Choose whether your developer will install Capell in your Laravel application, your organisation will deploy in its own Laravel Cloud account, or you need to request setup help. Your organisation owns the Laravel Cloud resources and pays Laravel Cloud charges.
The guided site-planning builder is currently unavailable. You can use the installation and deployment guides now; setup help is subject to an agreed scope and availability.
Pick the next question
Choose a starting path that gives you useful evidence.
An editor may first need to see preview and recovery. A developer may need to inspect the dependency and rendering boundary. A site owner may need to understand publishing accountability and ongoing costs. Give each person a concrete task rather than asking everyone to browse the same feature list.
The live demo is a quick way to inspect a configured workflow, while a local installation lets you test your own page model and integrations. Deployment belongs after the application and its operating owner are clear.
Keep the pilot small enough to finish
Define an acceptance result before adding optional packages.
Create a representative page, preview it, inspect the public response and practise a correction. Add the optional capability that answers the next requirement rather than building the whole catalogue into the trial.
Check current licensing and support information before adoption. Assisted onboarding, where offered, is an optional route with its own scope; the application still needs a maintenance owner and a clear handover.
Start with the route you can run
You can install Foundation without a Capell account. Laravel Cloud deployment uses your organisation’s own account and billing. Setup help begins with a conversation about fit and scope.
Optional assisted onboarding
Capell is accepting applications for a limited assisted design-partner beta. It is an optional route for Laravel agencies and product teams that want help assessing package fit, planning installation, or reviewing Publishing Studio for a real project. Participation is by selection and does not guarantee acceptance, production readiness, or a particular outcome.
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, known limitations, support route, response expectations, privacy boundary, 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, then include the relevant fields above in your message.