Production Twin

What this feature is for

Production Twin runs an approved journey against production to establish a baseline, then repeats the same steps against an HTTPS preview. It helps teams catch timing and behavior drift before promotion. The important distinction is that PreFlight stores the observation alongside the app, release, provider, or customer path it belongs to. That context is what turns a signal into an operational decision.

Before you open it

A Max workspace, a verified production app, an approved Journey Canary, and an HTTPS preview URL.

Use a real app in the workspace and start with the smallest useful scope. A narrow, representative check gives you a stronger baseline than connecting every environment and every provider at once.

Run the workflow

Choose the journey and preview host, confirm the host boundary, run the comparison, and inspect step-level differences before approving the deploy.

1. Open the feature from the dashboard outcome hub.
2. Choose the app and environment that match the decision you are making.
3. Run or save the configuration, then wait for the evidence state to settle.
4. Assign the next action to an owner before leaving the page.

Read the evidence

The comparison preserves timings, pass or fail state, and visual or browser artifacts for the production and preview runs. A green state means the configured assertion passed at the recorded time. It does not claim that every unconfigured path is healthy. A warning is a useful lead; a failure should have a concrete owner and a verification run.

When the result is not healthy

Private, non-HTTPS, or unapproved hosts should be rejected. A difference is a lead for investigation, not proof that the preview is broken; reproduce the step and inspect its dependency.

Do not erase the failed result after fixing the underlying system. Keep the history, rerun the check, and link the new passing evidence to the deployment or incident that caused the change. This gives the team a useful before-and-after record.

Use it with the rest of PreFlight

Use Production Twin with Release desk, GitHub checks, and Activity to retain the promotion record. Outcome hubs are deliberately connected: Audit finds risk, Deploy decides whether to promote, Health watches the running system, Revenue verifies the money path, Growth manages discoverability, and Trust publishes safe proof. Use the related links below to move between those decisions without losing context.