You vibe-coded something. Where does it live now?

Honest answer: it depends what you built. Full apps belong on app platforms, and we will tell you which. But most of what people vibe-code day to day (landing pages, prototypes, dashboards, reports, artifacts) is static, and static things just need a link. Private, if it is not for the whole internet.

Get started free

Where do you host a vibe-coded site?

Split it by what you built. A full app (login, database, server logic) belongs on your builder's hosting or an app platform like Vercel or Railway. Static output (a landing page, prototype, dashboard, report, or AI artifact) just needs a file served at a URL: publish the HTML to a static host, a private-by-default one like Stacktree if the audience is specific people rather than the public.

The boundary, stated plainly

Vibe-coding tools produce two different kinds of things, and they need different homes. Be suspicious of anyone who tells you one host fits both.

You built	It needs	Host it on
An app: login, database, server logic	Application hosting	Your builder's hosting (Lovable, Bolt, Replit deploy apps), or Vercel / Railway / Netlify
A landing page or one-pager	A file at a URL	A static host. Private link? Stacktree
A prototype or UI mockup for feedback	A shareable link, not the world	Stacktree (unguessable URL, optional password)
A dashboard or report with baked-in data	A private link colleagues can open	Stacktree (email-domain gate if it is internal)
An AI artifact (Claude, ChatGPT output)	A link that outlives the chat	Stacktree, straight from the agent over MCP

Stacktree hosts static HTML only, on purpose. We do not run your backend, and we will not pretend to. If your thing needs a server, the right answer is an app platform, and the rest of this page is not a sales pitch to change that.

Most vibe-coded output is the static kind

The day-to-day output of vibe coding is rarely a production app. It is the landing page you knocked out before lunch, the prototype you want three people to click through, the dashboard you generated from a CSV, the report your agent wrote, the diagram that explains the system. All of it is static. All of it needs exactly one thing: a URL someone can open.

The catch is that the default ways to get that URL are wrong for most of it. Builder preview links are public or tied to your workspace. Screenshots lose the interactivity. Zipping files for Slack means nobody opens them. And spinning up a deploy pipeline for one HTML file is using a freight train to post a letter.

The private link, in one step

Publish the HTML to Stacktree and send the link. Every URL is unguessable by default, so it works like a credential: the people you send it to can open it with no account, and nobody else can find it. Need more? Add a password, restrict viewers to your company email domain (verified by magic link), or encrypt end to end. Keep editing afterward: replace the content and the URL stays the same.

It works however you build. Drag a file into the dashboard. Ask Claude Code, Cursor, or Codex to publish it over MCP in one call. Or curl it from a script. The first publish needs no account at all.

Built a full app? Share the static view

Even when the real thing is an app on Lovable or Vercel, the thing you need to share usually is not the app. It is a snapshot: the metrics page for Monday's meeting, the design for sign-off, the prototype for feedback. Have your AI render that view as a self-contained HTML page and publish it. The app stays where it lives; the shareable moment gets its own private link.

Where to go next

Share Claude artifacts privately, straight from the chat.
Host AI-generated reports behind a private link.
Single-file internal tools, where they will actually get used.
Architecture diagrams the team can open.
How private HTML hosting works: the mechanisms behind the link.

FAQ

Frequent questions

Where should I host what I vibe-coded? +

It depends on what you built. A full app with a backend and database belongs on your builder's own hosting (Lovable, Bolt, Replit all deploy apps) or a platform like Vercel. A static page, prototype, dashboard, or report just needs a link: publish the HTML to a static host, a private one if it is not meant for the world.

What is the difference between an app and a static page here? +

An app has server logic: it logs users in, reads and writes a database, calls APIs from a backend. A static page is self-contained HTML, CSS, and JavaScript: landing pages, mockups, dashboards with baked-in data, reports, diagrams. Apps need application hosting; static pages need only a file served at a URL.

Can I share an AI-built page without making it public? +

Yes. Publish it to a private-by-default host. On Stacktree every page gets an unguessable URL that works like a credential: anyone you send it to can open it, nobody can find it. You can add a password, restrict viewers to your company email domain, or encrypt end to end.

My builder already gives me a preview link. Why not just share that? +

Builder preview links are often public, tied to your workspace, or break when you keep editing. A published Stacktree link is separate from your workspace, private by default, and stable: replace the content any time and the URL stays the same, so the link you shared yesterday shows today's version.

I built a full app in Lovable or Bolt. Is Stacktree for me? +

Not for hosting the app itself; keep that on your builder or a platform like Vercel. Stacktree is for the static things around it: the landing page, a clickable prototype for feedback, a report or dashboard snapshot a stakeholder needs. Have your AI render a static view and share that link.

Do I need to know how to deploy? +

No. If you can copy a file or ask your AI assistant to do it, you can publish. Drag the HTML into the dashboard, or have an agent like Claude, Cursor, or Codex publish it in one call over MCP. The first publish needs no account and the link comes back in seconds.

Keep reading

Related guides

References

Sources and further reading

Built something static? It needs a link, not a pipeline.

Drag it in or let your agent publish it. Private by default, free to start, no account for the first one.