Use case
For regional marketing and IT teams running several properties at once. CloudSite keeps each market in its own project, scopes access by token, and returns a deployment record every time something goes live.
No credit card needed to try the generator.
Capabilities
Run many market sites from one console: isolated projects, token scopes your security team can approve, review links and a record of every publish.
Each region gets its own slug, file tree, domain and deploy status, so a local team cannot overwrite another market by accident.
Read-only tokens inspect and report, write tokens edit and publish, and campaign sending asks for confirmation after a preflight check.
Preview links open for legal and regional reviewers without an account and expire on their own between one and seventy-two hours after you create them.
| Area | What you get |
|---|---|
| Languages | Up to four locales per site, each with hreflang, its own canonical URL and sitemap entry. |
| Deploy | Cloudflare Pages or Firebase Hosting; bind_domain writes the DNS record for you. |
| Editing | Chat edits or direct file writes through 75 MCP tools, all on the same project. |
| Audit | Built-in SEO and GEO audit for metadata, structured data and AI crawler access. |
| Preview | Shareable preview links that expire after 1 to 72 hours. |
One project state for generation, chat edits and deploys, so nothing drifts out of sync.
Give CloudSite the product, the audience and the languages. A complete first draft arrives in about 1 to 3 minutes.
Ask for a calmer hero, a spec table or another locale. Files update in place and stay deploy-ready.
Publish to the edge, bind the domain, then read traffic, leads and chat in the same console.
Projects are separated by slug, and every token belongs to one account. Give each market its own write token, and hand reviewers a read-only token or a preview link instead of console access.
Uploads replace the file set as one unit and return the deployment that went live, including the target platform. Domain binding reports provider, zone and status for each custom domain in the project list.
Yes. The console actions are exposed as 75 MCP tools under the same token scopes, so an internal assistant can inspect a project or prepare a deploy without bypassing your access rules.
This site is maintained by the CloudSite team as a reference for large organisations evaluating website operations. We work on project isolation, token scopes and deployment records inside the console. Reach us through cloudsite.editorapi.com to arrange a walkthrough.
CloudSite is a website platform at cloudsite.editorapi.com. You describe a business, or upload an existing static site, and CloudSite writes, edits, deploys and hosts it. Every console action is also an MCP tool, so agents can run the same lifecycle end to end.
Twenty sites, twenty angles, all served from the same platform.