Hosted app pages: publish a page Sidekick built

When Sidekick builds you a simple, self-contained page — a demo, prototype, or small utility — you can ask it to publish that page directly and get a real, shareable link. Publishing always asks for your explicit confirmation first, every page is checked before it goes live, and you can unpublish it any time. Bigger apps with a backend route to a connected deployment destination instead.

Publish a page Sidekick built#

When Sidekick builds you a simple web page — a demo, a prototype, a small utility, a one-off interactive tool — you can ask it to publish that page so you have a real link to share. Sidekick hosts it directly; you don't need to set up a hosting account first.

How it works#

  1. Ask Sidekick to build the page (for example, "build me a page that visualizes X" or "make a quick demo of Y").
  2. Ask it to publish or host the page. Sidekick shows you what it's about to make public and asks you to confirm — nothing goes live without your explicit go-ahead.
  3. Once you confirm, Sidekick publishes the page and gives you the real link. Anyone with the link can open it.
  4. Say "unpublish it" (or "take it down") whenever you want, and the page stops being reachable.

Sidekick never tells you a page is live before it actually is — you only get a link once publishing has actually happened, never a guess or a placeholder.

What this is for#

Hosted app pages are for small, self-contained, client-side pages: demos, prototypes, one-off utilities, interactive visualizations, simple games, and similar. They're a fast way to share something Sidekick made without leaving the conversation.

They are not a general web hosting service. A page that needs a backend, a database, server-side code, or a login system doesn't fit this path — for that kind of full application, Sidekick routes the code to a deployment destination you've connected and approved (your own hosting account) instead of hosting it directly. See Builder destinations for how that works.

What's true about every published page#

  • Revocable, anytime. You can take a page down whenever you want, and LumenFlow can take a page down too if it needs to.
  • Sandboxed. A published page runs isolated from your workspace — it can't read your data, your account, or anything else in LumenFlow.
  • Checked before it goes live. Every page is checked against a content policy before publishing; a page that fails the check is refused rather than published.
  • No sign-in fields. Published pages can't collect passwords or sign-in details from visitors.
  • Not indexed for search. Published pages are meant to be shared by link, not discovered through search engines.
  • Limited per workspace. Your workspace has a limit on how many pages can be live at once and how often you can publish. If you're at that limit, Sidekick tells you honestly rather than pretending a publish worked, and gives you a way forward — unpublish an older page, wait, or upgrade.

Reporting a problem with a published page#

Every published page carries a way to report it if something looks wrong. Reports go to LumenFlow, not to the person who published it.

info Saving something in LumenFlow and publishing it are different actions. See Outputs, artifacts, and destinations for how managed artifact links, hosted app pages, and connected deployments differ.