Your own domain

A garden can answer at a domain you own instead of, or as well as, its sizuq address. Attaching one does not use up a garden slot — it is an extra address for a garden you already have.

1. Open the garden's settings, choose Publishing, and enter the domain in Address.
2. sizuq shows you the DNS record to add. Add it at whoever manages your domain.
3. Come back and press Check status. sizuq checks project ownership, DNS readiness for certificate issuance, and routing separately; DNS changes take their own time.
4. The address is marked Connected only when all of those checks are ready.

Publishing separates the garden's address from the place that serves it. Sizuq Cloud remains the default, while Orbit / linktree gardens can publish the same portable artifact to an Own host over FTPS or SFTP. Both transports share the same revision, public HTTPS verification, audit and rollback pipeline.

Manual export downloads a provider-neutral publication manifest containing the public routes, published content, pages, navigation, projects, Orbit data and presentation settings for this garden. Orbit / linktree gardens can also download a static ZIP that can be unpacked directly on ordinary hosting. The portable renderer preserves content, clean URLs, identity, accent and theme atmosphere; dynamic/WebGL scenes use a static palette-based representation for now.

Static ZIP has an Include hosted media switch. Off keeps image URLs remote and makes the export small. On copies sizuq-managed R2 images into assets/media and rewrites the HTML to local paths. Third-party URLs such as an external OAuth avatar stay remote; sizuq does not server-fetch arbitrary URLs. Large ZIPs are staged temporarily in R2 instead of being returned through the function response, then old temporary exports are cleaned automatically.

Orbit / linktree gardens can use Own host → FTPS. Public URL is the HTTPS address readers open; FTP server is the transfer endpoint; Remote root is the directory on that server. They are deliberately separate, so moving a garden does not make its public identity depend on a provider.

1. Choose the Lolipop preset or Generic FTPS. For Lolipop the connection uses explicit TLS (FTPES), port 21 and passive transfers.
2. Enter the Public URL, FTP server, account, password and Remote root, then save.
3. Run Test connection. The password is encrypted before storage and is never returned to the settings screen.
4. Run Publish now. sizuq builds the same portable artifact used by Static ZIP, uploads the new files, removes files from the previous committed revision that no longer exist, uploads the well-known manifest last, then reads that manifest back over FTPS and verifies the revision.
5. Turn on Auto publish when the manual path is healthy. Every 10 minutes sizuq compares the generated deployment revision and transfers only when content or relevant publishing settings changed.

SFTP transfers files over SSH. sizuq recommends Ed25519 public-key authentication and also supports password authentication when needed. It uses the same portable artifact as FTPS, so publication and rollback semantics stay identical.

1. Choose SFTP / SSH and enter the server, port, account, Remote root and Public URL.
2. Obtain the SSH server's SHA-256 host-key fingerprint through a trusted channel such as the hosting control panel and enter it. sizuq never auto-accepts an unknown host key merely because it is the first connection.
3. Choose Ed25519 key and save. sizuq generates a Garden-specific key pair and shows only the public key; add that line to authorized_keys on the SSH server. The private key is encrypted with AES-256-GCM and is never returned to the settings screen.
4. Run Test connection, then Publish now. sizuq reads the manifest back over SFTP to verify the revision, then verifies the same revision and the root over the reader-facing Public URL.
5. Enable Auto publish once the manual path is healthy. Rollback redeploys the retained artifact over the same SFTP transport.

There are three ways, and which one is available to you depends on your domain and your DNS provider. sizuq shows the exact values; this is how to choose between them.

The first two are preferable because they follow sizuq's connection host: if the underlying address ever changes, nothing on your side needs touching. A plain A record is a fixed number, and would need updating by hand.

If you take the subdomain route, remember to send the bare domain somewhere too, usually by redirecting it to the subdomain at your DNS or hosting layer. Otherwise someone typing the domain without the www gets nothing.

Several separate things have to be true: the domain must be authorized for the sizuq project, its DNS must point at Vercel so a certificate can be issued, and sizuq must know which garden the domain means. Check status tests each condition; a merely valid-looking or nonexistent hostname cannot become Connected.

If the status reports that verification succeeded but routing has not been published, the symptom is unhelpful — the domain answers with sizuq's own front page rather than your garden. Pressing Check status again republishes the mapping and usually resolves it.

Both addresses keep working. Which one is the canonical address — the one search engines index and the one links prefer — is yours to decide with a single setting.

• Leave it off, and the sizuq address stays canonical while your domain also answers.
• Turn it on, and your domain becomes canonical: the sizuq address redirects to it, and the sitemap and links follow.