Volnyn – Website Builder, Domains, Property, Freelancers & Free Games
Open App

Publish your Volnyn site

Deploy your AI site to a live URL, control who can visit it, connect a custom domain, and keep updating after launch.

Publishing turns your AI-built project into a live web app on a URL you can share. Volnyn hosts the published site for you — HTTPS included on production hosts. Visitors see the published build; your editor, chat history, and unpublished work stay private to your account.

Quick start: publish your first site

  1. Build a site in chat or the AI builder until the build completes.
  2. Volnyn can auto-publish a completed site under a free subdomain so you get a live link without opening a separate publish modal.
  3. Open the live URL, or find it from your site dashboard / chat when the build finishes.
  4. To push later edits live, publish or rebuild again so the hosted snapshot updates.

You can also continue editing after the first publish. The live URL stays stable when the site already has a subdomain; auto-publish is idempotent and will not invent a new random subdomain every time.

Prefer a branded address? Connect a custom domain after the site is live on its Volnyn subdomain.

What publishing does

Publishing does Publishing does not
Serve a hosted snapshot at a public (or password-gated) URL Grant strangers access to your editor or source
Give you a shareable link for clients and visitors Automatically push every chat edit without a new publish/build
Work with custom domains and access settings Replace GitHub backup — use Git sync for that

Free Volnyn subdomain

On first publish, Volnyn allocates a subdomain on the platform base domain (for example xxxxxx.volnyn.site — the exact base depends on server settings).

  • The URL uses HTTPS in production (or HTTP on local).
  • Custom domains take priority in “live URL” helpers once verified: custom domain URL → otherwise the published subdomain URL.
  • Renaming the site display name does not by itself change the allocated subdomain.

Who can see the published site

Open Access in the site sidebar (/user/site/access) under Site settings.

Mode Who can visit
Public (default) Anyone with the address. Search engines may index it.
Password Visitors must enter the password you set (at least 4 characters). Share the password with reviewers or internal users.

Password mode is useful for client reviews and internal tools without making the site fully public. It is enforced when the published site is served.

Publishing does not change who can edit the project in the dashboard. Access settings only gate visitors at the live URL.

For guest feedback without giving editor access, use Project comments share links.

Connect a custom domain

Give the site an address like www.yourbrand.com:

  1. Open Custom Domain (/user/site/ai-domain) under Domains and URLs.
  2. Enter a domain you already own.
  3. Point DNS (name servers or A record) as shown on the page.
  4. Click Verify.
  5. After verification, SSL is provisioned (status moves toward active). Wait for the certificate before expecting HTTPS on the custom host.

Notes:

  • Custom domains apply to AI-built sites from this page.
  • A domain can only be attached to one site at a time.
  • Remove the domain from the page if you need to detach it; the Volnyn subdomain URL remains available when configured.

Security before you go public

Publishing does not automatically block on security findings, but you should check first:

  1. Open Security (/user/site/security).
  2. Click Run scan — dependency advisories (OSV) plus committed secret patterns.
  3. Fix critical issues (especially exposed API keys) before a wide public launch.

See Security overview.

SEO after publishing

Some checks only make sense against a live URL:

  1. Publish the site (you need a live URL).
  2. Open SEO (/user/site/seo).
  3. Run the audit for on-page SEO and AI-search readiness.
  4. If you later connect a custom domain, run the audit again against the new host.

Ask the assistant in chat to adjust titles, descriptions, and social previews when you want metadata changes.

Updating a published site

Your site stays editable after publishing.

  1. Change the site in chat or the builder.
  2. Let the build complete.
  3. Publish / deploy updates so visitors see the new snapshot.

If the live site looks stale, hard-refresh or confirm the latest build finished and was published. Preview in the editor can be ahead of the last published snapshot.

Collect feedback without opening the editor

Use Comments to create a share link. Reviewers open /review/{token}, see the published site (when available), and leave feedback — no Volnyn account required. Manage replies from the Comments inbox.

See Project comments.

Back up source on GitHub

Publishing hosts the live site. It does not replace a Git backup. Use GitHub → Push to GitHub to export source. See Git sync overview.

FAQ

Does my published site expire?
No automatic expiry for inactivity is documented for the hosted subdomain. Keep your account and platform hosting in good standing. Preview review links are separate from the permanent published URL.

Does publishing expose my project code?
No. Visitors get the published front-end at the live URL. They do not get your dashboard, chat history, or unpublished workspace unless you share those separately (for example via GitHub).

Why don’t I see my latest changes on the live site?
The live site is a published snapshot. Finish a new build/publish after edits. Check that you’re opening the same subdomain or verified custom domain.

Can I password-protect a published site?
Yes — Access → Password mode. Share the password with people who should visit.

Can I publish without a custom domain?
Yes. The free Volnyn subdomain is enough to go live.

Should I run SEO after publishing?
Yes for public sites. The SEO auditor needs a live URL. Re-run after connecting a custom domain.

Does publishing cost AI credits?
Hosting and the publish/auto-publish path are separate from chat usage. Asking the assistant to change the site or metadata in chat uses credits like any other chat message.

What if auto-publish fails?
The build can still be complete. Publish manually from the AI site flow, or retry once subdomain publishing is configured on the platform.