Build preview: see a version before it goes live
Build a new version of your site without publishing it and get a secret link to that version only. The live address keeps serving the current working version the whole time. Checked it? Publish with one click.
Available from the Start plan.
Build without publishing
In the panel, “Build without publishing”; in the CLI, the --no-activate flag; for an AI agent, activate:false. The live address keeps serving the current working version the whole time.
Get the link
The Preview toggle on a version gives you a secret link on preview.tuqo.ru. Send it to a client or a colleague, or open it on your phone.
Publish or walk away
All good? Click Publish and the live address switches to the checked version instantly. Don't like it? Just don't publish: visitors never noticed a thing.
When you need it
An AI agent asks before going live
The agent edits your live site and, instead of “I've shipped it”, sends a link: here is the result, shall I publish? The decision stays with you, not with the model.
A studio shows the client
The new version of a client's site is visible before release. No separate staging site and no moving files over after approval.
Check before a rollback
You can get a link for any kept version except the one that is live now — that one is already visible at the site's address. See what was in a past build before rolling back to it, instead of picking blindly by date.
Edits on a live site
Changing a form, prices or the hero section where visitors already are: look first, publish second.
How it works
Where to turn it on
Panel
On the site page, every version has a Preview toggle: switch it on and a link appears, with Open and Copy next to it. Switch it off and the link stops working. To publish, click Publish.
AI agent (MCP)
The activate: false parameter in the deploy
tools, the link from get_preview_url,
publishing with activate_deploy.
REST API
activate: false in the deploy body, then
POST /api/v1/deploys/{id}/preview.
To revoke, send DELETE to the same path.
CLI
tuqo deploy ./dist --site <id> --no-activate,
then tuqo preview <deploy_id> and
tuqo promote <deploy_id>.
Build preview — frequently asked questions
How is this different from Drop? +
Drop is publishing without an account: an anonymous draft lives for 24 hours and is meant for trying the service. Build preview is a working tool for a site owner: it shows a specific build of your existing site while the live address keeps serving the published version.
Who can see the site through the link? +
Whoever you give it to. The address is unguessable, the page is not indexed or cached, and you can turn the link off at any time with the toggle on the version. It does not ask for a password, even if the site itself is gated: otherwise showing a build to a client would be impossible (in subscribers-only mode they would have to subscribe to your channel). Holding the link is what grants access, so share it only with people you trust.
How long does the link live? +
As long as the build itself. Versions are kept according to your plan (the last 3 on Start), and older ones are pushed out by newer ones. The link has no timer of its own, but you can turn it off at any time.
Does a preview count toward my limits? +
Yes, like a regular build: it uses the daily deploy limit and storage. There is no separate fee for previews — they are included in every plan from Start up.
Can an AI agent do this on its own? +
Yes. The deploy tools take activate:false, and a separate tool returns the link. Agents are advised to offer a preview when the site is already live and the change is risky — but it is an option, not a required step: regular publishes go live right away.
What about search engines and analytics? +
Preview pages send a no-index directive and their own robots.txt, and the preview host is closed to crawlers entirely. These views do not count in the site's statistics.
Publish with confidence
A link to check first, the live address second. No separate staging site and no moment when visitors see a broken version.