Your project's pages, built and served on a live HTTPS URL — one menu click, no server of your own.
Open the project menu and choose Publish Website. The build runs on the server, and the dialog reports each stage as it happens: exporting, building, uploading, deploying. You also get a bell notification when it starts and when it succeeds or fails, so you can close the dialog and keep working.
One publish runs at a time per project; a second click while a build is in flight is refused.
The first publish creates the project's preview host — an address like my-site-k3x9.example.app, shown in the dialog with a copy button. It is stable: republishing keeps the same URL forever, so a link you shared last week shows this week's build.
Two properties of that URL worth knowing:
It is unlisted, not private. Preview hosts are served with noindex, nofollow, so search engines stay away — but anyone with the link can open it, and the address contains your project's name. Treat it like an unlisted video.
It is never someone else's. The edge serves sites strictly by hostname; an unknown host gets an error, never another project's build.
A static export — plain HTML, JavaScript and CSS built with Next.js. That makes it fast and cacheable, and it also draws the boundary:
No server-side rendering and no API routes. Your designs' API calls run in the visitor's browser, the same way the canvas preview runs them.
CMS content is baked in at build time. Publishing new content means publishing again.
Change the design, choose Publish Website again. A fresh build replaces the old one at the same URL. There is nothing to invalidate by hand.
Not yet. Today you cannot point your own domain at a published project — the preview host is the way to share it. Custom domains are being built; this page will grow that section when they ship.
The same menu has Publish NPM: one click builds the project's components into a package on Misaki Studio's own registry, auto-versioned by date. The dialog hands you everything a consumer needs — the .npmrc lines, the npm install command and the package.json entry, each with a copy button.
Every component is importable by its own subpath, with types:
import * as Button from "@misaki-studio/<project-uuid>/components/atoms/button";React, React DOM and Next are peer dependencies, so the package uses the versions your app already has. Note the registry is Misaki Studio's, not npmjs.com, and the package is named by your project's uuid.
Prefer owning the pipeline? Boilerplates walks through publishing from your own repository instead.
Export your code — the code the site is built from.
Share a project — collaborators, not visitors.