Short answer
Between push and live, your app is checked for obvious problems: broken pages, missing assets, and exposed secrets. Dependencies resolve automatically along the way. Nothing reaches your users in the state you would have caught yourself five minutes after showing a friend.
The three checks, in plain terms
Broken pages. A route that crashes, a page that renders blank, a flow that dies halfway. The check looks for the app visibly failing to do what it should — the bugs that make a first impression fatal, caught before a user finds them.
Missing assets. Images that never load, scripts that 404, styles that silently fail. A page that works but looks broken reads as unreliable even when the logic underneath is fine.
Exposed secrets. Keys and tokens that ended up somewhere users can reach them. This is the serious one: a leaked key is not a cosmetic problem, it is someone else's way into your account, your database, or your bill.
Why this matters more for AI-written code
Code generated by an AI assistant deploys through the exact same pipeline as code you wrote by hand. That matters because AI-assisted builds fail in classic ways: a hard-coded key left in the page, an asset path that exists only in the prompt's imagination, a route the assistant assumed but never wired. These checks exist precisely for that category — the problems that are obvious to whoever clicks around and invisible to whoever wrote the code.
What a failed check means
The deploy does not ship broken to your users. Fix what the check flagged and push again. The cycle stays fast because there is no environment to rebuild between attempts.
What the checks are not
They are not a substitute for testing your business logic. A quote calculator that computes the wrong number will pass every check on this page — the app runs, the pages load, the secrets stay put. The checks catch the ways an app visibly breaks, not the ways it quietly misleads. Test the numbers yourself before the app speaks for your business.
The takeaway
The gap between it works on my machine and it works for the first stranger who visits is exactly what these checks cover. That gap is where most small apps die — and watching it is now somebody else's job.
Related reading: Your first deploy on Forge and How to move an existing app to Forge.