Publishing Your Site

Publish

Click Publish in the top bar (sign-in required):

Publish — go live, roll back, and share preview branches.

Pick a name. Your site lives at https://<name>.plyed.cloud — the picker checks availability as you type. The name is claimed to your account the first time you publish.
Publish. Plyed builds the project and uploads it. The button shows progress; when it’s done you get a View live link.

Publishing is atomic — visitors never see a half-updated site. Republishing replaces the whole site in one switch, but only uploads the files that actually changed since your last publish — a small edit republishes in a fraction of the time a full site upload would take.

Update, roll back, take down

Reopen the Publish popover on a published project:

Publish live again after making changes to republish — the new version is live in seconds. Edited content in a connected CMS also needs a republish to show up, since the published site is a static build.
Rollback instantly restores the previous version (one step back).
Unpublish takes the site offline; the name stays yours.

Preview branches

Your project’s git branch decides where Publish goes. The Publish popover shows the branch you’re on and the exact address it will publish to before you click.

On your default branch (usually main), Publish live updates your live site at https://<name>.plyed.cloud.
On any other branch, the button becomes Publish preview: the branch gets its own address, https://<name>--<branch>.plyed.cloud, while the live site stays as it was. A branch called feature/new-pricing publishes to https://<name>--feature-new-pricing.plyed.cloud. Characters a web address can’t hold become hyphens, and very long names are shortened.
Republishing on the same branch updates that same preview.
Switch branches (in the Git panel, in a terminal, or let the AI agent do it) and the popover follows. Nothing to rename or retype. A branch you create with Create & switch in the Git panel publishes a preview, never your live site.
To put a branch on the live site anyway, use Publish as the live site… and confirm.
A branch whose name has no letters or numbers can’t become an address. Plyed says so instead of guessing; rename the branch to publish a preview.

Previews carry a preview badge and ask search engines not to index them. They are public to anyone with the link; this is not access protection. The Previews list shows every preview of the site, including ones from other branches and from cloud agents. Open or unpublish each from there. Your live site is untouched.

Previews are available on paid plans; how many each site can have depends on your plan.

Custom domains

A project’s dashboard page at api.plyed.app can show existing domain names and their status when your role allows it. The current dashboard does not provide controls to add, verify, change the primary domain or remove a domain. Use your site’s plyed.cloud address for the complete self-service publishing flow described above.

Deploy to your own Vercel account

Your plyed.cloud address isn’t the only place a site can live. From api.plyed.app, open your project’s dashboard page — if you don’t have one yet for a published site, the dashboard’s Create a workspace form makes one, linked to that site — and find the Vercel card:

Generate a personal access token from your Vercel account settings.
Paste it into the card (a team ID is optional, for tokens scoped to a Vercel team) and click Connect.
Click Deploy to Vercel. Plyed deploys your project’s code as a new deployment and shows you the resulting URL.

Deploying to Vercel uses the code from the Plyed tab of the Git panel in the top bar — see Back up to GitHub. That tab needs no setup, but it does need at least one sync: if you’ve never opened the Git panel for this project, sync it there once before your first Vercel deploy, or the deploy will fail with a message asking you to.

Turn on auto-deploy while connecting to keep it going without clicking Deploy each time: pushes to your project’s main branch go to Vercel production, and other branches — including ones a cloud agent run creates — get a Vercel preview deployment.

This deploys the same project you’re building in Plyed onto infrastructure you control; it doesn’t replace or interfere with your plyed.cloud site, and the two can run side by side. Only the project owner can connect, deploy or disconnect Vercel.

Site limits

Plan	Published sites	Preview branches per site
Free	1	—
Starter	3	1
Pro	10	5
Ultra	50	20

Trying to publish past your limit shows an upgrade prompt; see Plans & credits. Claimed names count toward your site limit even while unpublished.