tuqo

What is a deploy? A plain-English explanation

A deploy is publishing a site or an app on a server so that anyone can open it by a link. While the project sits on your computer, only you can see it. After a deploy, it is available to everyone at an address like https://name.tuqo.ru.

A build and a deploy are not the same thing

Two steps often get mixed up:

  • A build turns source code into ready-to-serve files. For example, npm run build compiles a React project into a dist/ folder with optimized HTML, CSS and JS.
  • A deploy uploads those ready files to hosting and publishes them at an address with HTTPS.

A plain HTML/CSS/JS site needs no build: it goes straight to deploy. Framework projects are built first and deployed second. On Tuqo you can leave both steps to the platform: upload the source code and it builds and publishes it for you.

How a static site gets deployed

  1. The ready files (or the source code) are packed into an archive and sent to the hosting.
  2. If needed, the hosting builds the project and lays out the files.
  3. The files are served over HTTPS, usually through a CDN so the site opens quickly everywhere.
  4. You get an address where the site is available; on paid plans you can attach your own domain.

What a deploy rollback is

Every deploy is a separate version of the site. If a new version breaks, good hosting lets you roll back: bring the previous working build back in a second, without rebuilding. On Tuqo a rollback is one click, on paid plans, which keep several past versions (see pricing for how many).

A deploy in seconds on Tuqo

On Tuqo a static deploy takes seconds:

# deploy via the REST API (or from the panel, or from an AI agent over MCP)
curl -X POST https://api.tuqo.ru/api/v1/sites/$SITE/deploys \
  -H "Authorization: Bearer tqk_xxx_yyy" \
  -H "Content-Type: application/gzip" \
  --data-binary @site.tar.gz

The command line is optional: in the panel you can simply drag the site folder in, and a zip works as well as a tar.gz: Tuqo detects the archive format itself.

Right after that the site opens over HTTPS with a free SSL certificate.

What next