Deploy a Gatsby site in seconds
Gatsby builds the site into public/, which Tuqo recognizes alongside dist and build, so upload the sources and we build it for you. Free SSL; version rollbacks on paid plans.
public/ · Node 20 · free SSL Upload the project
A .tar.gz or .zip archive with the Gatsby sources (a lock file is recommended).
Build on Node 20
npm ci && npm run build (gatsby build), with the output taken from public/.
Published over HTTPS
The site is on name.tuqo.ru right away, free SSL, a custom domain from the Start plan.
# build locally and upload, or upload the sources and let Tuqo build them
npm ci && npm run build # output in public/
# pack the output (index.html must be at the root of the archive)
tar -czf site.tar.gz -C public .
# deploy over REST (or from the panel, or from an AI agent over MCP)
SITE=<site_id> # from the panel or list_sites
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 not the only way: in the panel you can simply drag the site folder
in, and instead of .tar.gz a
.zip works too — Tuqo detects the archive
format by itself.
Deploying Gatsby — frequently asked questions
Will Tuqo build Gatsby by itself? +
Yes. The standard build script of a Gatsby project is gatsby build, and Tuqo looks for the public/ output alongside dist and build.
Can I upload a public folder I already built? +
Yes. If the upload has an index.html and no package.json, it is published as it is, with no build.
Is there HTTPS and a custom domain? +
HTTPS with free SSL on every plan, including Free. Custom domains from the Start plan; on Free, as a paid add-on.