Guides
Short, practical how-tos on deploys, domains, SSL, gated access and publishing from AI agents.
CI/CD for a static site without GitHub Actions
Continuous deployment for a static site without GitHub Actions, YAML pipelines or runners: link the repository to Tuqo and every push publishes the site.
Read →Deploy a site from Claude, ChatGPT or Cursor
Deploy a site straight from an AI chat: connect Tuqo over MCP to Claude, ChatGPT, Cursor or another client, then ask it to create, build and publish.
Read →Site access by email list: a code instead of a password
Tie site access to a person: visitors enter their email, get a six-digit code and sign in. How it differs from a password and what the sign-in log shows.
Read →Auto-deploy a static site from Git: push to publish
Set up continuous deployment for a static site: connect GitHub, GitLab, Gitea, GitVerse or GitFlic, and every push rebuilds and publishes the site on its own.
Read →Claude artifact on your own domain: how to publish
Claude built a site as an artifact. How to put it on your own domain with HTTPS, forms and versions, and why that beats the built-in Publish button in Claude.
Read →How to add a custom domain to a static site
Connect your own domain to a static site: which DNS records to add, how domain ownership is verified and how free HTTPS gets turned on automatically.
Read →Custom domain via Cloudflare DNS: turn off the proxy
Which Cloudflare DNS records to create for a site on Tuqo, and why the orange cloud must be switched to DNS only: otherwise HTTPS and verification fail.
Read →How to deploy a Vite project in two minutes
Step by step: publish a Vite project (React, Vue, Svelte) online in a couple of minutes, with an automatic build, free SSL and a subdomain right away.
Read →Domain not working after setup: what to check
Why a custom domain won't open: the A record points elsewhere, the TXT record hasn't propagated, DNS caching, www as a separate name, or HTTPS not issued yet.
Read →Deploy from GitHub Actions and GitLab CI in one step
Publish a static site to Tuqo from your own pipeline: one npx @tuqo/cli deploy step, the key in a TUQO_API_KEY secret, ready YAML and pull request previews.
Read →Auto-reply to form submissions on a static site
Someone sends your form and instantly gets your email: a confirmation, instructions or a file. Set up an auto-reply on a static site in minutes, no backend.
Read →How to get a free SSL certificate for your site
What SSL and HTTPS are, why a site needs them, and how to get a free certificate with automatic renewal for a static site, with nothing to set up.
Read →How to host an HTML site online
Put a plain HTML, CSS and JS site online in a couple of minutes: free HTTPS, no build step and no server. Custom domains are available on paid plans.
Read →How to hand over a site to a client, domain included
The site moves into the client's account whole: domain, certificate, versions and settings. What moves, what switches off, and why both sides need a paid plan.
Read →Lead magnet on a static site: a file for an email
Hand out a checklist, guide or price list only for a real email address: form, auto-reply, file delivery page. No backend and no mailing service needed.
Read →Media-heavy site: update without re-uploading photos
Sites with hundreds of photos: deploy with the CLI and sha256 dedup, so a text edit never re-uploads images and AI agents never pass bytes through context.
Read →Migrate a static site from Vercel or Netlify
Move a static site or frontend build from Vercel or Netlify to Tuqo: the same repository, auto-deploy on push, free SSL, and what does not carry over.
Read →Password-protect a static site without .htaccess
Put a password on a static site without Apache, nginx or htpasswd: the lock covers every file. How it differs from .htaccess and how to limit access time.
Read →How to publish a site from ChatGPT: three ways
ChatGPT wrote a site; now put it online. Three ways: Drop with no account, a folder upload in the Tuqo panel, or a connector right from the chat over OAuth.
Read →Publish a site without signing up: Tuqo Drop
Publish a static site on Tuqo with no account: drop a folder and it is live within a minute. The draft lives 24 hours; claim it into a free account in a click.
Read →Redirect the tuqo.ru subdomain to your own domain
A site is served on every enabled address at once. How to make your domain the main one, redirect the system subdomain and choose what a disabled address shows.
Read →How to roll back a site to a previous version
A deploy broke the site? Bring back the previous version in one click: the Deploys tab, activate_deploy over MCP or promote in the CLI. Kept versions by plan.
Read →Share a mockup with a client by a private link
Show a client a site demo at its real address, hidden from search and competitors: a password on the whole site, access until sign-off, and one click to unlock.
Read →SPA 404 on page refresh (React Router, Vue Router)
Why a React or Vue single-page app returns 404 when you reload an inner page, and how a fallback to index.html fixes it. On Tuqo it works with no config.
Read →What AI breaks in sites: 14 checks explained
An API key in the markup, broken paths, localhost, base64 images, a form with no submit address. Tuqo's 14 checks: why AI models do this and how to fix it.
Read →What is a deploy? A plain-English explanation
A deploy is publishing a site or app so it is available online. What a deploy is, how it works for a static site, and how it differs from a build or a rollback.
Read →What is MCP, and how to deploy a site from an AI
MCP (Model Context Protocol) in plain words: how to connect a hosting platform to an AI model and handle sites, deploys, domains and rollbacks by chat.
Read →Why a deploy failed: 6 common causes and fixes
The six most common reasons a static site deploy is rejected: nested folders, index.htm, a gzipped file, a build with no output, size limits, service files.
Read →