Review behavior, not screenshots
A preview is a real deployment with its own URL, logs, environment configuration, and version ID. Reviewers can test forms, authentication, APIs, and responsive behavior without sending traffic to production.
Isolation by default
- Separate preview variables from production secrets.
- Use synthetic or masked datasets for sensitive workflows.
- Keep preview URLs out of public indexing when the application contains non-public content.
- Delete temporary resources on merge or after a retention window.
Promotion without rebuild
Once a preview is approved, Apex can promote the tested artifact through the release pipeline. Keeping the artifact stable between environments reduces the chance that a dependency or build step changes after review.
The review contract
Teams get the most value when the preview has an explicit acceptance checklist: functional smoke tests, accessibility checks, analytics verification, and the route or API cases most likely to regress.
Enable branch previews
Connect your Git provider and create your first branch-based preview.