Choose which optional cookies Capell may use.
Essential cookies are always on for login, security and page rendering.
Read the cookie policyCapell prepares the first deployment: it creates the Cloud application, links the database, applies bootstrap variables and waits for the CMS to register back.
Your team still owns the source, billing, domains, secrets and ongoing operations. Everything is created inside your own account, so the hosted evaluation can become a normal Laravel project if the fit is right.
Prepare a Capell application for your own Laravel Cloud account, with checks that go beyond provisioning.
A deployment should leave your team knowing what runs, what it costs and who responds when something fails. Capell can help prepare the Laravel Cloud setup, but your organisation owns the Cloud account and the application. Use the workflow below to connect provisioning to a verified public site.
Use this path when an evaluator needs a real hosted Capell application before the team wants to wire the first environment by hand. Capell coordinates the first setup; Laravel Cloud provides the infrastructure.
After you connect Laravel Cloud and choose a source and region, Capell checks access, creates the application and managed database, links the environment, sets bootstrap variables, starts the first deploy and records registration.
The Laravel Cloud organisation owns and is billed for the resources. Your team remains responsible for source access, domains, secrets, application configuration, package updates, queues, storage, backups, monitoring and future deploys. Capell does not operate the app as a hosted CMS service.
If your team already has a proven Laravel Cloud template and does not need Capell's instance record or guided bootstrap, use Laravel Cloud directly. The guided path should remove first-run work, not replace deployment practices that already serve the project well.
Review resources and configuration before committing to a deployment.
A new environment may need a database, application secrets, built assets and background services. Review the proposed resources and the current Cloud terms before creating them. Keep development and production configuration separate, and do not paste credentials into public support conversations.
Provisioning is not the same as publishing a complete website. Your project still needs content, a domain, application configuration and a maintenance owner. Treat the first deployment as a rehearsal until its checks and recovery path are clear.
Check the deployed visitor journey alongside the application's health endpoint.
After deployment, inspect a public page, its media and its primary action. Check configuration, migrations, background work and logs for the workflows your application uses. A healthy process can still serve a stale page or an incomplete form.
Agree a release decision and rollback path before the production switch. Separate application rollback from content recovery, and verify the canonical response after either. Keep operational checks in the project runbook so deployment is repeatable.
The video follows account connection, source checks, resource creation and registration. It also shows that the resulting infrastructure remains in the customer-owned Laravel Cloud organisation.
See how Capell prepares a customer-owned Laravel Cloud app in minutes.
Each step is recorded against the instance. Owners can see what exists, and developers can retry a failed check from a known point.
Create or open your Capell account. This is where the setup status, instance record, and later operations live.
Verify the Laravel Cloud organization that should own and bill the resources, then confirm it before setup starts.
Select the repository path and target region. Capell checks GitHub and Laravel Cloud source-control access before creating Cloud resources.
Capell asks Laravel Cloud for an application, default environment, and managed database, then links the database to the environment.
Deployment variables are set, the first deploy runs, and the deployed Capell CMS registers back to the Capell account.
From there you can open the new Capell app and manage domains, environment variables, commands, deploys, and diagnostics from the cloud instance screen.
Capell creates a managed database in the selected region and links it to the Laravel Cloud environment.
See backupsAfter the app is live, domain creation and verification can be tracked from the cloud instance screen.
Review securityCapell sets the variables required for the first deploy, bootstrap, registration, and selected packages.
Deployment variablesAfter the quick setup, trigger deploys, run commands, manage domains and variables, and inspect diagnostics from the cloud instance record.
Customer accountsThe questions below describe the customer-owned Laravel Cloud setup path. They do not describe a hosted Capell SaaS.