Pages
Publish static sites and agent outputs to a shareable URL
Pages host static sites (HTML, CSS, JS, images) on a public URL. Use them for AI agent outputs like feature previews, reports, or summaries, or any small static site you want to share without deploying a service.
Each organization gets one shared pages bucket. Every page is a folder in that bucket, served at its own address:
https://<name>.rock8cloud.pageThe root index.html is served at that address.
Pages have their own name pool, separate from apps' .rock8cloud.app addresses - the same name can belong to different owners on each.
Publishing
Pages are published by an AI coding agent through the MCP integration. Ask your agent to publish and it calls the publish_page tool:
- First publish provisions your org's bucket. This takes about a minute and the agent waits automatically.
- Slug is the storage path segment (lowercase letters, digits, dashes). Omit it to auto-generate, or reuse one to update an existing page.
- Address is the public name served at
<name>.rock8cloud.page. Omit it on first publish to derive one from the slug, or omit it later to keep the current address. Addresses are first come, first served across all pages - renaming frees the old one for anyone else to claim. - Republishing the same slug replaces the whole site. Files not in the new upload are deleted.
- Unavailable address does not discard an upload. A page whose requested address is already taken is stored as a hidden draft. It shows Needs address in the dashboard and is not reachable from either public URL. Choose an available address in its settings to publish it.
- Invalid address format is rejected before files are uploaded.
Draft files remain available through authenticated file browsing, count toward bucket storage, and stay until you publish or delete the page. The API token needs the write:artifacts scope.
Limits
| Limit | Value |
|---|---|
| Total per publish | 5 MB |
| Per file | 1 MB |
| Files per publish | 200 |
Access control
Pages are protected by default with HTTP basic auth. The agent sets a username and password on first publish, or you set public: true to serve without a credential.
Agents change access later with the set_page_access tool, without republishing. Pass public: true to open a page, or a username and password to protect it. The password is stored hashed and cannot be shown again, so the agent shares it with you when it sets it. You can also change access yourself in the page's Settings.
Managing pages
Open Pages from the dashboard - the Pages card on your dashboard, or the org switcher menu - for the full list across the organization, with each page's address, size, file count, and status (Live, Needs address, Offline, or Removed).
Select a page for its detail view:
- Overview - the page's address, size, and current status, with a notice when it needs an address or has been taken offline.
- Settings - toggle public/protected access, rotate the basic-auth password, rename the address, or delete the page. Deleting removes all its files from storage and cannot be undone.
- Preview - view the published site inline without leaving the dashboard.
Bucket storage
The shared bucket is drawn from your plan's S3 storage quota (100 MB minimum). Expand it from the Pages section's bucket settings. Increasing the cap draws from your unallocated storage quota.
Agents and the dashboard can also list, delete, or change access of pages via the list_pages, delete_page, and set_page_access MCP tools.