# Site releases

Every release binds a selected source component and immutable revision to one authorized Site. Choose the destination before reviewing readiness; a source with multiple Sites has no implied default production target.

## Release or update

Connect the source, select the component and revision, and review the Site's production configuration, visitor audience, and readiness result. **Release to Site** starts its first activation; **Update Site** changes an existing destination. Wait for the release state and verify the active Site. A submitted request, working preview, or source edit is not an active release.

If activation fails, the prior healthy version remains the serving version. Inspect the error and operational logs before retrying. Recovery can restore code, but it cannot automatically reverse a database migration or an external action. Plan schema and job compatibility as part of the update. See [Project release preparation](/docs/projects/releases) and [Site operations](/docs/sites/operations).

## Example: recover a failed update

If a candidate release fails startup, inspect its reported failure and confirm which release is still serving visitors. Correct the source or configuration responsible, then submit a deliberate update.

If a release changed database data before a later problem appeared, reverting code does not reverse those changes. Review [Databases](/docs/services/databases) and [Operations](/docs/sites/operations) when planning recovery.

## Verify the update

Check the reported active revision and the actual Site address. Repeat the changed user workflow under the intended access, then inspect [Logs](/docs/services/logs) for a reported failure. If the update affects stored records or background work, include [Databases](/docs/services/databases) and [Jobs](/docs/services/jobs) in the review.