Notable product changes with the dates they reached production: the panel, the MCP server, the REST API, the CLI, forms, gated access and analytics. Internal plumbing stays out.
Machine-readable for agents: tuqo.dev/changelog.md · how-tos: guides
Each of the 52 MCP server tools now has a readable title and a hint saying whether it only reads data or changes it (and whether it may delete or overwrite something). Claude and other clients use these hints to decide when to ask a person for confirmation. The Tuqo plugin for Claude Code is updated to version 1.1.0.
A site’s address can now be changed on the Domains tab: the new name is reserved for the site at once, and the switch happens after 24 hours — until then the change can be canceled, and the owner gets an email. Forms, domains, access settings and statistics stay with the site. For agents: REST POST /api/v1/sites/{id}/subdomain-change and MCP change_site_subdomain.
All tuqo.ru addresses are served with a shared Let's Encrypt certificate: a new site no longer waits for its own certificate, and HTTPS works from the moment it is created. Custom domains still get their certificates automatically, as before.
tuqo.ru now has SKILL.md (publishing rules for Claude Code, Cursor, Codex), prompt.md (connect in one line), the /ai/ page (when to recommend Tuqo), openapi.json for the REST API, pricing.md and changelog.md, and the full documentation in one file, llms-full.txt. mcp.tuqo.ru serves a server card at /.well-known/mcp.json listing every tool. The MCP instructions gained rules for how an agent talks to a person.
The integration page was rewritten for built-in delivery of submissions to messengers (profile → Messengers → Link, then a recipient in Forms); messengers were added to the forms and pricing pages. Technical SEO fixes: breadcrumbs on every page, honest lastmod in the sitemap, og:type=article for guides, a robots.txt that explicitly allows AI crawlers.
On every publish Tuqo checks the files: leaked keys and PEM private keys, broken links, localhost in links, mixed content, noindex and Disallow left over from a template, viewport, base64 images, a form without a submit address, a template title, favicon and OG tags. The result is a banner on the site card, a separate checklist page, a toggle in settings and a recommendations field in deploy_files, REST and get_site responses.
verify_domain and the panel show the real certificate status (ssl_status with a reason: issuing, handshake error, no certificate) and where the domain’s A record points right now. The certificate is warmed up on the first deploy, so the first visit does not wait for issuance.
An incremental mirror of S3 and database dumps is copied to independent storage at another provider with a key that is not allowed to delete. Sites and data survive the loss of the main storage.
Two new gated access modes. Member sign-up: visitors register themselves with an email code, accept your documents and pass sign-in moderation. Paid access: sell access to a site through your own acquiring (T-Kassa, YooKassa) with a 0% Tuqo fee, a storefront and checkout on pay.tuqo.ru, seats and a sales window, and a generator of seller documents. New tabs: Members, Payments, Access terms, Settings, Login screen; a favicon for the login screen.
An active key now has a Regenerate button: a new secret with the same name and permissions, and the old one stops working. Previously you had to create a new key and delete the old one.
The “Useful” and “Documentation” menus became mega menus with three and four columns; on phones the menu opens over the page and scrolls on its own.
Published: a data processing agreement (DPA) for owners of sites with forms and paid access, the list of subprocessors, and additions to the Terms of Service and the terms for site visitors; the paywall shows the seller’s details in its documents.
Server-side statistics without cookies or scripts on every plan: views and visitors (“humans” and “all”), traffic, top pages, referrers, downloads, 404 errors and devices, submissions and deploys on the chart, period presets up to 365 days, CSV export, notifications at 80% and 100% of plan traffic. For agents: get_site_stats and GET /api/v1/sites/{id}/stats.
The auto-reply email is written in a visual editor with formatting and {{field}} placeholders from the submission; the delivery page holds up to three files with captions; submissions have a table view with search and an auto-reply badge. Support tickets gained a “no reply” mark and editing of replies.
From the Start plan, whoever submits a form automatically gets an email on behalf of the site owner, with a text and the promised file (a checklist, a guide, a price list). The file is delivered by a link in the email, so only in exchange for a real address. Set it up in the panel, via REST or MCP (set_autoreply, add_autoreply_file, set_autoreply_delivery).
A deploy with activate:false builds a version without publishing it: the live address does not change, the build can be shown by a secret link and published later (promote). The panel has a toggle and buttons, the CLI has --no-activate, tuqo preview and tuqo promote, MCP has get_preview_url and activate_deploy. Unneeded builds can now be deleted.
Link a messenger in your profile to get account notifications and form submissions there. New access mode, Subscribers only: the site opens only to subscribers of your Telegram or MAX channels, and the subscription is confirmed in the bot right from the login screen.
Custom domain, badge removal, site password, email code, subscribers, members, paid access, site and storage packs: targeted add-ons for any plan, the Free plan included. An Add-ons section in the panel and a “Plan or add-on?” page on the website.
A password closes the whole site (images and PDFs included) behind your own login screen; access by date and by number of entries, an access log; sign-in with an emailed code for a list of up to 1000 addresses with names and bulk actions. Managed from the panel, REST and MCP.
A limit refusal names the specific plan and price; deploy errors explain the cause (a nested folder, index.htm, no output directory); the service paths .git and .env are not published, and dropped files are listed in MCP, REST and Drop responses. A page on static hosting in Russia was published.
Storage limits were raised on every paid plan; the panel accepts zip archives; a support page was published.
Support tickets live in the panel: a number, history, attachments, categories; clicking a notification opens the conversation.
Extra submissions and plan renewals go through a single checkout with a receipt; a quarter is −10%, a year −25%. Sites on the Free plan show the “Powered by Tuqo” badge.
A draft is published without an account, by drag and drop on the website or with POST /instant/deploy from an agent; it lives 24 hours and is claimed into a free account by a link. CLI 0.2.0: the key in TUQO_API_KEY, --wait prints the live address, tuqo.json for several sites.
GET mcp.tuqo.ru returns ready-made connection instructions to an agent, so a person only has to send the link to the AI. On the OAuth consent screen (connecting claude.ai, ChatGPT, Claude Code, Codex without pasting a key) you now choose the connection name and lifetime; connections are listed and revoked in the panel.
verify_domain and the panel show where the domain’s A record points and which value to set.
multipart/form-data is accepted, unknown body types get an honest 415, “spam” and “not spam” marks return the quota, and there is a page to buy extra submissions.
A site is served on its subdomain and all verified domains at once; addresses are switched on and off, a disabled one redirects to a working one, and a domain can move between sites. Submission recipients are assigned to all sites of a project or to a specific one, and delivery can be paused.
get_form_submissions and REST let an AI read submissions; auto-deploy from a repository on push via OAuth or a PAT, including the Russian GitFlic and GitVerse. Plans are switched on and payment acquiring is live.
Deploying by manifest with deduplication: a repeat deploy does not re-upload matching files, bytes do not pass through the agent’s context, and no tar is built in memory. CLI: npx @tuqo/cli deploy ./dist --site <id>.
A ready-made form snippet, submissions in the panel, spam protection, email delivery, plan limits with extra packs.
The static hosting platform is open: deploy by files, by archive and from Git, .tuqo.ru subdomains, custom domains with automatic SSL, an MCP server and REST API, payment in rubles.
The platform launched on June 10, 2026. We do not publish plans or product decisions here, only what already works.
