Secrets and shipping live

The Secrets tab

If an app needs to talk to an outside service, it usually needs keys or environment variables to do it. The Secrets tab lets you add those to the build, so the app carries its own integration secrets. You add, reveal, and remove values right here. Treat a real production key like the key to your bank: hand it over only when the real work starts, never to the test rehearsal. Keep live keys out of a build you are only poking at, and add them when you are genuinely ready to go live.

The Deploy tab

Deploy is where you ship a build to a live URL. The pipeline is complete end to end: shipping links the build to a hosting project and gives it a white-labeled URL, and the tab carries a log tail, an error inspector, an auto-fix action for common build errors, and a take-offline control to pull the app back down.

The honest state of deploy

This part is built, but it is new. In production, no app has actually been shipped live through this pipeline yet. Everything above exists in the product and is wired together, but treat deploy as available rather than proven. If you are the first to ship something real, go slowly: test in preview, read the logs right after the first deploy, and keep that take-offline control within reach.

Credits and cost

Shipping and running an app can carry its own cost, separate from the credits you spent generating it. Check your plan and the per-build cost before you lean on deploy for anything that matters, and watch your credit balance the same way you would for any other run.