Comparing environments

Which build is each environment actually running, and is Live what you tested? The Compare pane answers both, and promotes between them without rebuilding.

What it shows

One card per environment: the version hash it points at, when that build was pushed and by whom. A version hash is derived from content, so identical hashes mean byte-identical builds — which is the only way to answer the question with certainty.

Same hash in Staging and Live means the same bytes. Not “built from the same commit” — the same artifact, which is a stronger statement and the one that matters when something behaves differently in one place.

Promoting

Promotion repoints an environment at a build that already exists. No bytes move, nothing is re-encrypted, and no rebuild happens — which is why what you tested in Staging is exactly what ships.

Pick the source environment, pick the target, promote. It is also how you roll back: promote the previous build and the environment returns to it.

A rollback is a pointer change. There is no re-upload and no rebuild, so it takes as long as a reload — which is the reason a bad deploy is a minor event rather than an incident.

Free tier

Promotion needs a centrally-held artifact to repoint at, and on the free tier there is not one — the encrypted build retires to your own server once it confirms it holds a copy. Push again to the target environment instead.

See Editions for why that trade exists.

Push and reload are separate

Worth knowing, because it is not what most pipelines do. A push uploads a build and moves the environment’s pointer; the fleet keeps serving the previous build until it is reloaded.

So deploying and rolling out are two deliberate acts. You can push at any time and choose when it goes live.

Pushing code Domains