Public Trust Page

What this feature is for

The Public Trust Page turns selected uptime, incident, maintenance, and reliability evidence into a customer-facing status experience. 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

Publicly safe components, current monitors, a brand name, and a decision about how much incident detail customers need.

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 components, preview the page, confirm that no secret or internal hostname appears, publish, and review it after releases and incidents.

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

Public evidence should show status, history, timestamps, and an honest scope so a customer can understand what is covered. 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

Never expose credentials, customer identities, raw internal errors, or private infrastructure. Public proof should explain impact and recovery without widening access.

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 Trust Page with Trust page builder, Reliability Score, Reports, and Health. 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.