Where do I host a Storybook privately?

Chromatic keeps published Storybooks private by default. A static host with a gate, such as Cloudflare Pages with Cloudflare Access, also works.

Can Display host my Storybook?

Not today. A Storybook build is a folder of many files, and Display publishes one HTML or Markdown file for each artifact. Directory and ZIP publishing is on the roadmap.

Where do I host a vibe-coded site privately?

If the export is a static folder, use Netlify, Cloudflare Pages or GitHub Pages and add a gate. If the site has a backend, use an app platform. If it is one HTML file, publish it to Display.

Can I password-protect a static site?

Yes, on hosts that check the password on the server. Netlify has it on Pro. Vercel has it on Pro for $20 a month per protected project. A JavaScript password page does not protect the files. Read How to password-protect an HTML file.

How do I share a client demo site without making it public?

Put the folder on a host with a gate, and give the client the login or the password. For a single demo file, publish it to Display and invite the client's email address. The client opens it with a one-time password and can view it. Outside guests cannot comment yet.

Can I host an AI dashboard privately?

Yes, if it exports to one self-contained HTML file. Ask your agent to publish it to Display for your company. Read Share data dashboards internally.

What if I have a folder and I want Display?

Build it to one file, as above. If that is not possible, host the folder somewhere else for now. Read Where should I host an HTML page or site my AI agent made?.

Where Do You Host a Vibe-Coded Site or a Storybook Build Privately?

Display is our product. This page sends you to a different host for most folders, and says so. We checked the vendor facts on each vendor's own pages on 16 October 2026.

Static output is files, an app is a process

Look at what the build made.

Static output. A folder with index.html, scripts, styles and images. Storybook builds this with npm run build-storybook. Many vibe-coding tools can export it. A client demo is usually this too. Any web server can serve it.
An app with a backend. The page calls a server, a database or an API with secrets. A static host cannot run that part. You need an app platform such as Vercel, Railway or Render.

If the folder needs only a browser, a static host with a gate works. The rest of this page is about that case.

Options for a private static site

Option	How it controls access	Cost	Fits
Chromatic	Published Storybooks are private by default. A visitor signs in with a profile that has project access. You can make one public	Check Chromatic's pricing	A Storybook
Cloudflare Pages + Cloudflare Access	Access applications deny everyone by default. You add an Allow policy	Free for up to 50 users, then $7 per user a month, paid annually. The domain must be on Cloudflare	Any static folder
Netlify	A shared password on Pro. A private project uses Netlify login for the people you invite	Pro plan price	Any static folder
Vercel Deployment Protection	Vercel Authentication on every plan, Password Protection on Pro, or sign-in through your identity provider on Enterprise	$20 a month per protected project for a password on Pro	An app or a static folder on Vercel
GitHub Pages, private	Only people with read access to the repository	Needs GitHub Enterprise Cloud	A folder built from a repository
Display	Company sign-in, invited email addresses, or public	€0 to €49 a month, unlimited viewers	One HTML or Markdown file

A shared password tells you only that someone knows the password. It does not tell you who opened the page. A password prompt written in JavaScript does not protect the files.

Where Display fits, and where it does not

Display holds one HTML or Markdown file for each artifact. A file can be 10 MB on Free and 50 MB on paid plans. That fits:

an AI dashboard exported as one self-contained file
a demo page, a prototype or a report in one file
a component sheet that you write as one page

It does not fit a Storybook build, which is a folder with many files. It does not fit a multi-page client site or any app with a backend. Publishing a directory or a ZIP file is on the roadmap. It is not available today. If you need it now, host the folder on one of the options above, or use a tool that accepts a ZIP file. Stacktree documents ZIP upload through its REST API.

Make a build into one file

Some builds can make a single HTML file. The Vite plugin vite-plugin-singlefile puts the JavaScript and CSS inside one file. Build with it. Open the file from disk and check that the page still works.

Then tell your agent: "Publish dist/index.html to Display as 'Booking widget demo' for my company."

If the page loads fonts, images or data from other files, those files are not part of the artifact. Put them inside the file as data URLs, or remove them.

Steps: a Storybook behind a gate

Build it with npm run build-storybook. Storybook writes a static web app. Its guide uses storybook-static as the output folder in an example.
Pick one gate from the table. If your team already uses Chromatic, publish there. The Storybook guide calls Chromatic "a free publishing service made for Storybook".
For Cloudflare, deploy the folder with npx wrangler pages deploy storybook-static. Then add an Access application with an Allow policy.
Open the URL in a private window. If the page loads without a sign-in, the gate does not work.

Do the same test for a vibe-coded export and for a client demo. For each one, open the URL while you are signed out.

When another tool is better

Use Chromatic for a Storybook. Use Cloudflare Pages with Access, or Netlify, when you must protect a whole static site today. Use an app platform when the build has a backend.

Use Display for the documents around the build. Examples are the review of the demo, the specification, the report with the test results, and a dashboard in one file. Agents publish them to a link. Colleagues comment, and the agent updates the same URL.