Four steps, one direction.
From a build that isn't public to one that is — with nothing exposed a moment before you choose. Here's the whole path.
The path, one step at a time.
Stage your build
Put the site somewhere private the moment it exists. It lives on a dedicated staging host, separate from production and away from the public web — not on a guessable subdomain of the site you're about to replace.
Share a private preview
Hand a client or collaborator a way in without opening the door to everyone. They see the work in progress; search engines, scrapers, and passers-by don't. The preview is for the people you choose and no one else.
Review off the record
Iterate in the open with the people who matter and in the dark to everyone else. Nothing about an unfinished draft ends up indexed, cached, or discoverable while you're still deciding what it should be.
Launch when you're ready
The build stays sealed until the decision is yours to make. When it is, you launch — deliberately, on your own timing — and not a moment before.
Speaks your language, not a sales deck.
No public UI to fake, no dashboard screenshot to stage. Staging a build is meant to feel like something you already do — quietly, from where you work.
# park a build that isn't public yet push build --to staging --private staged ok visibility: private indexing off robots: disallow all preview ready access: owner + invited # launch only when you say so launch --when ready status held awaiting your signal
Ready to stage something private?
Tell us what you're building. We'll get you set up with somewhere safe to put it.
Request access