WordPress with a plugin list nobody wants to audit. A Webflow project that only one person can publish. Or a folder of HTML that was last touched by a contractor.
CloudSite takes the output — HTML, CSS, assets — and serves it from Cloudflare Pages or Firebase Hosting. No plugin layer, no database to keep alive, no rebuild queue.
CloudSite does not import a WordPress database or a Webflow project. You bring the built site — the files a browser actually receives — and CloudSite hosts and edits that.
From WordPress, publish a static copy through your existing export path. From Webflow, export the site. From a hand-built folder, use it as-is.
The archive must place index.html at the site root. Fix nested folders before uploading, not after.
Upload once and open the pages.dev address. No DNS change is needed to look at the result.
Upload a zip or the individual files. The upload replaces the whole site on the current property.
Point the domain from the console. CloudSite writes the CNAME at Cloudflare automatically.
Keep the old site up while you check. The preview address works independently of your domain, so you can compare page by page before switching traffic. Review on a phone as well as a laptop — exported layouts often break where the CMS used to handle wrapping.
| The old stack | On CloudSite | |
|---|---|---|
| Publishing | A login, a builder and a publish button somebody owns | An explicit deploy to Pages or Firebase, callable by an agent with a write token |
| Editing | Theme settings, shortcodes, or a visual editor's approximation of the markup | Chat for intent, or a direct write to one named file |
| Structure | Content lives in a database you have to back up separately | The site is the files; index.html at the root is the entry point |
| Languages | A plugin per locale, or a translation service bolted on | Up to four languages per property, managed as part of the site |
| Domain | DNS records copied by hand from a support article | Binding writes the CNAME at Cloudflare automatically |
| Review | Staging environments that drift from production | Preview links valid for one to 72 hours, openable without an account |
| Ceiling | Whatever the plugin ecosystem will still support | 2 MB per file, UTF-8; large media belongs elsewhere |
If the site is mostly content, this is usually straightforward. If it is an application with accounts and transactions, keep the application where it is and migrate the marketing pages first. That is still a migration, and a much smaller one.