Connect Laravel Cloud

A team has one connected Laravel Cloud account. The token controls infrastructure billed in that account, so only the team Owner can connect, replace, or disconnect it. Every team member may see whether a connection exists.

Connect the account

1. Create an API token in the Laravel Cloud dashboard.
2. Open Team settings → Laravel Cloud.
3. Paste the token and select Connect.

Scalpels immediately uses the token to read its Laravel Cloud organization. This verifies that the credential works and records which organization it reaches before the token is stored. A rejected credential is not saved.

The token is encrypted at rest. After submission, the input is cleared and the full token is never rendered back; the settings page shows only a short hint.

What Scalpels reads

Depending on the action you request, Scalpels can read the connected organization, applications, environments, resource status, deployment status, and command status. Inventory scans compare applications and environments with catalog repositories.

When Scalpels describes an environment, it keeps environment variable names but normally drops their values at the API boundary. The only values retained are public URLs for manifest keys explicitly marked as derived, which lets Scalpels detect when a Cloud-provided URL no longer matches the environment's current address. Secret values are never retained.

What Scalpels writes

During an install, Scalpels can create or configure the application and environment, PHP version, build command, database, cache, managed queue, object storage, scheduler, resource attachments, deployment, and allowlisted post-deploy commands required by the product manifest.

Scalpels writes the application-owned environment keys declared by the manifest or a provider recipe, plus two keys of its own that identify what it set up: BUILT_FOR_CLOUD_DEPLOYMENT_ID on every environment it provisions, and BFC_CLIENT_IDENTITY on every application it connects to a provider. Laravel Cloud injects connection details for attached resources through its own managed environment file; Scalpels does not write those managed keys.

Scalpels has no automatic rollback or teardown path. A failed install leaves any resources already created in your Cloud account and lists them on the deployment page.

Replace or disconnect

Replacing the token verifies and records the organization reached by the replacement. Existing deployments retain the organization identity they were created under and refuse to resume against a different account.

Disconnecting removes Scalpels' copy of the token. It does not change or delete anything running in Laravel Cloud.