Test changes in a preview
Check a change against a complete copy of production before applying it to production itself:
deliberate diff --env productiondeliberate apply --env productionRepeating the same apply is safe. Each apply reconciles the Environment to one complete Project revision.
Create a preview
Section titled “Create a preview”A Flow describes which persistent Environments exist and which disposable
Environment names can be created from them. The bundled default provides a
production Environment and a preview-* family derived from it. Teams on plans
that permit custom Flows may change this topology; otherwise the current Flow
remains usable but locked.
Applying to a missing matching name creates the preview and reconciles the complete local desired state onto it:
deliberate apply --env preview-new-checkoutdeliberate open --env preview-new-checkoutAfter testing, apply the accepted desired state explicitly to production and remove the preview:
deliberate apply --env productiondeliberate envs delete preview-new-checkoutFind the deployed application
Section titled “Find the deployed application”After apply, the CLI and console report whether Components became ready and show the relevant public or Private Net routes. A Blueprint’s optional onboarding link is a first-deploy UX nudge, not hidden lifecycle state.
Generated platform hostnames are stable for their resource identity. Use your own domain for a customer-facing production address.