CloudSite gives large teams a structured way to run many properties: separate projects per market, explicit access scopes for the people and agents that touch them, and a deployment record for every publish.
Each market gets its own project, its own domain and its own deploy status. Nothing is shared implicitly.
Slug-scoped projects with independent file trees, so regional teams never overwrite each other.
Up to four locales per property, generated and maintained as first-class variants.
Every custom domain carries provider, zone and status in one list instead of a spreadsheet.
A token states what it may do. Agents get exactly the surface they need.
| Capability | Read-only | Read and write | Notes |
|---|---|---|---|
| List projects and files | yes | yes | Scoped to the issuing account |
| Read page source | yes | yes | UTF-8 text, 2 MB per file |
| Edit files | no | yes | Marks the project as pending deploy |
| Publish | no | yes | Cloudflare Pages or Firebase Hosting |
| Email campaigns | no | confirmation required | Preflight runs before sending |
Every step returns a state you can log: upload, publish, domain binding.
Share links expire in 1–72 hours and open without a login, which suits legal and regional review.
An upload replaces the file set as one unit and returns the exact deployment that went live.
Internal copilots use the same operations through MCP, inside the same access rules.