up to $20

Docs

Publish a site

Publish static files or run a scale-to-zero service at your-name.plori.site. Ready-card and Files paths, private-by-default visibility, updates, and runtime credits.

Give one directory of an agent's disk its own address at https://<name>.plori.site. That address can either serve static files or run a service. New sites and services are private by default, and publishing always needs an explicit action from you in the Files panel.

Use a static site for pages whose work can happen in the browser. Use a service when the project needs a server: for example, an API, a secret that cannot be sent to the browser, or server-side access to another website.

Use the ready card

When an agent finishes and verifies something publishable, the session shows a Ready to publish or Ready to activate card. This is the shortest path:

  1. Click Review & publish site or Review & activate service on the card.
  2. Check the address and the prefilled directory. The correct Static site or Service mode is already selected.
  3. Choose Private or Public, then click Publish privately, Publish publicly, or Activate service.

The card does not put anything online by itself. You still choose visibility and confirm. If there is no ready card, or you want to publish directly from Files, use the manual paths below.

Publish a static site from Files

  1. Open the agent's Files panel on the dashboard, or Files in the agent terminal.
  2. Expand the site directory and open its front page, usually index.html.
  3. Click Publish as a website in the file preview toolbar.
  4. Keep Static site selected and check the address and Directory to serve.
  5. Choose Private or Public, then click Publish privately or Publish publicly.

The site's index.html becomes its home page. The publish button follows the file that can be put online, so opening only the directory is not enough; open an HTML file first.

Activate a service from Files

A service directory needs the server code and a plori-service.json file at its root. For example:

{
  "start": "node server.js",
  "port": 3000
}

The server must listen on the declared port. The manifest may also contain non-secret environment variables and paths to exclude from the deployed copy; never put secrets in this file.

To put the service online:

  1. Open Files and expand the app directory.
  2. Open plori-service.json.
  3. Click Publish as a website in the file preview toolbar.
  4. Service is selected automatically. Check the address and App directory.
  5. Choose Private or Public, then click Activate service.

Opening the manifest is the important part: selecting the directory by itself does not show the publish button.

Publishing needs a registered account. Each agent can have one plori.site address, backed by either a static site or a service.

Static sites and services behave differently

Static site:

  • Files are served directly from the agent's disk. HTML, CSS, browser JavaScript, images, fonts, audio, video, PDFs, and WebAssembly work; Node, Python, and other servers do not run in this mode.
  • An edit is live as soon as it is saved. There is no redeploy step.
  • It keeps working while the agent sleeps and uses no runtime credits.
  • There are no directory listings. A directory serves its index.html or nothing, and paths starting with a dot are never served. Unknown routes are not rewritten to a single-page app's index.html.

Service:

  • The app runs in a scale-to-zero container. The first request after it has gone to sleep includes a brief cold start; the service then stays up for a short idle window before sleeping again.
  • Activation deploys a snapshot of the app directory. After changing code, dependencies, or plori-service.json, open Site settings and click Redeploy. The next request boots the new snapshot.
  • The service uses runtime credits for each started minute its container is running, including the idle window before scale-to-zero. It draws no runtime credits while asleep. A static site has no runtime charge.
  • Files written by the running server are not kept across restarts. Use an external store for durable application data.

What address does it get?

Every published site or service lives at its own subdomain:

https://my-project.plori.site

You get a suggested name and can change it before the first publish. Names use lowercase letters, digits, and hyphens, are at least 3 characters, and must be globally unique. A name stays reserved to its agent after unpublishing or deactivating, so an old link can never begin serving someone else's project.

Who can open it?

Private is the default for both kinds:

  • Only you can open it. Open site from the Files panel or dashboard signs the browser in to that address. Pasting the address into a browser where you are signed in to plori works too.
  • Other people cannot confirm that the address exists. Private content is not indexed by search engines and does not produce link previews in chat apps.

Public means anyone with the link can open it, and search engines may index it.

Change visibility in Site settings at any time. Switching a public address back to private locks out existing visitors immediately.

Take it offline

Open Site settings, then choose Unpublish for a static site or Deactivate for a service. The link stops working, but its name remains reserved to the agent.

Reporting abuse

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