Docs

Publish a site

Turn one directory of an agent's disk into a website at your-name.plori.site. Private by default, served while the agent sleeps, and how visibility works.

Publishing takes one directory of an agent's disk and serves it as a website at https://<name>.plori.site. The site is served straight from the disk, so it keeps working while the agent sleeps, and serving it runs no compute. New sites are private: nobody but you can open one until you make it public.

A typical flow: ask the agent to build the site ("make me a landing page for my side project in site/"), check the result in the files panel, then publish that directory.

Publish

  1. Open the agent's Files panel on the dashboard, or the files dock in the terminal.
  2. Click Publish site. Pick the directory to serve and a name. The directory's index.html becomes the home page.
  3. Choose Private or Public and publish. The site is live at https://<name>.plori.site right away.

Publishing needs a registered account, and each agent can have one site.

The address

Every site gets its own address on plori.site:

https://my-project.plori.site

Names are lowercase letters, digits, and hyphens, at least 3 characters, and globally unique; some names are reserved. A name belongs to one agent, and it stays reserved to that agent even after you unpublish, so a link you shared can never start serving someone else's content.

Who can see your site

Private (the default):

  • Only you. Open it with Open site from the files panel or dashboard; the first visit signs your browser in to that one site for about seven days.
  • Everyone else sees a plain 404 page, the same page a nonexistent address shows. A private site does not reveal that it exists.
  • Search engines cannot index it, and pasting the link into a chat shows no preview. That is by design: private means signed in, not "hidden behind a long URL".

Public:

  • Anyone with the link can open it, and search engines may index it.
  • Switch a site between private and public anytime in Site settings. Flipping a public site back to private locks out every visitor immediately, including tabs that are already open.

Updating the site

The published site serves the directory as it is now. When you or the agent change the files, the site changes with them; there is no separate deploy step. Public sites are cached at the edge, so a change can take up to a minute to appear.

What can be served

Sites are static files; nothing on a site runs on a server. HTML, CSS, JavaScript, images, fonts, audio, video, PDFs, and WebAssembly all serve with their proper content types. Paths starting with a dot are never served, and there are no directory listings: a directory shows its index.html or nothing.

Not supported yet: custom domains, and single-page-app fallback routing. A framework router that expects unknown paths rewritten to index.html will 404 on refresh, so have the agent generate real files per page instead.

Cost

Serving is included: no charge per visit, and no compute charge, because the site serves from disk without waking the agent. The site's files count toward your account disk like any other files.

Unpublish

Unpublish in Site settings takes the site offline: the link stops working and the name stays reserved to your agent. Publishing again with the same name brings it back.

Abuse

Published sites follow the platform's acceptable-use rules. If a plori.site website is hosting harmful content, report it there; we can take a site offline platform-wide.