# Deploy and verify Deploy locally tested source to Development, exercise that exact version, then promote it. ## 1. Link your project ```sh browserlayer login https://api.browserlayer.dev browserlayer link --studio https://browserlayer.dev ``` For another installation, substitute its API and dashboard origins. ## 2. Deploy to Development ```sh browserlayer deploy atlas-demo --env development browserlayer connections create atlas-demo --env development --wait browserlayer studio --env development ``` Use a website reachable by the cloud browser. A local loopback tutorial URL is not reachable from the cloud. Local connections and captures are not uploaded. ## 3. Exercise the deployed integration ```sh browserlayer syncs list --env development browserlayer syncs records bookings --env development browserlayer run atlas-demo cancel-booking --env development \ --connection \ --input '{"bookingId":""}' --wait browserlayer runs inspect --env development ``` Verify successful output, MFA and sync updates against a test account. Deployment success only means the artifact was assigned. ## 4. Promote the same artifact ```sh browserlayer promote atlas-demo --version --env production --dry-run browserlayer promote atlas-demo --version --env production browserlayer keys create --env production --name my-app ``` Promotion requires at least one completed Development run of that exact artifact. That gate does not prove every endpoint and failure case was tested. Promotion does not rebuild source. Store the application key on your backend. Production accounts connect separately through [hosted Link](/docs/connect). ## Roll back ```sh browserlayer deployments list atlas-demo --env production browserlayer rollback atlas-demo --to --env production ``` Rollback selects an existing integration artifact. It does not roll back infrastructure or database schemas. Suspended runs remain pinned to their original artifact.