Prod

The Production section points at your live deployment, the real running app rather than a mock, so you can verify a release and debug production behavior without leaving the workspace. It is the same section that holds the deploy controls, so shipping and inspecting sit together.

Production follows the first live web deployment for the active project. If there is not one yet, the Production pane reads No deployment: use Deploy. Ship one with Publish to the web.

#The panes

• Deploy holds the deploy controls and build history. See Deploy.
• Production iframes the live deployed app. Click through it the way a user would and compare it against what you see in Dev. It carries Web and iOS tabs, so a project that targets both inspects either surface from the one pane.
• Health combines status and logs. It heads with the deploy’s slug and a state badge, live for a managed deploy and local for a local dev one, and adds last-24h Worker and Durable Object stats for managed Cloudflare Workers. Live logs stream below that, managed deploys through Cloudflare’s Workers Observability telemetry. If the deployment lacks access to that telemetry, the pane says so.

Connect a payment provider and a Revenue pane joins them. See Monetization.

Deleting a deployment clears it from these panes but does not unpublish the live URL.

#When production differs from preview

If the live app behaves differently from your Dev preview, the deploy is usually running older files. Deploys build from main, so:

1. Confirm the change is on main and the Dev preview is correct.
2. Redeploy from the Deploy pane’s Web section.
3. Re-open the Production pane and verify.

If the difference is data, remember that production runs its own database inside the deployment’s Durable Object; it does not share your dev stack’s data.