Scope
We compare delivery of a marketing site: static hosting, file access, multilingual output and domain setup. Catalogues, memberships and app backends are out of scope.
Build options · Marketing sites
Four ways to ship a site. One table, no theatre.
CloudSite, WordPress, Webflow and a traditional agency build solve overlapping problems. This page compares the parts that usually decide a marketing-site stack, and marks the places where the honest answer is “it depends”.
Generation1–3 min
Single-file cap2 MB
Languages per site4 max
MCP tools75
Preview link1–72 h
The comparison matrix
Scope: marketing sites with static delivery and up to four languages. Symbols describe native capability, not overall product quality.
| Capability | CloudSite | WordPress | Webflow | Agency build |
|---|---|---|---|---|
| AI full-site generation | One prompt, 1–3 minutes | Plugin add-ons | Not a native path | Manual build |
| File-level editing | Any file, 2 MB per file | Theme files plus database | Visual canvas | Contract-dependent |
| Chat-based revisions | chat_site | Editor only | Designer only | Via account team |
| Static deployment | Cloudflare Pages or Firebase | Export plugins | Hosted static output | Varies by stack |
| Multilingual | Up to 4 languages per site | Plugins | Localization feature | Scoped per project |
| Custom domain binding | Automatic CNAME via Cloudflare | Manual DNS | DNS records | Handover docs |
| Preview without login | Link valid 1–72 hours | Setup-dependent | Platform previews | Staging, often gated |
| Agent / MCP access | 75 MCP tools | REST API | Limited API | Not offered |
| Billing model | Usage-based wallet | Hosting plus plugins | Subscription tiers | Fixed project fee |
✓native, documented capability
◐possible with add-ons, configuration or custom work
✗not a supported path
How to read it
Three caveats before this table goes into a procurement document.
“Partial” is real
WordPress can produce a static export, Webflow can host a fast site, and an agency can hand over clean files. The symbol marks the default path, not the ceiling.
Not compared
Price, plugin depth, design ceiling and support SLAs. Each depends on plan, region and contract, so they are better checked directly than scored here.
Where each option fits
An honest shortlist usually keeps two candidates, not one.
CloudSite tends to fit when
- You want a deployed marketing site in minutes, not a build queue.
- You prefer editing files and chatting changes over a locked canvas.
- Agents or internal tools should drive the site through MCP.
- Four languages per site is enough for your markets.
Another option may fit better when
- You need a deep plugin ecosystem and already run WordPress.
- Your design team wants a visual canvas as the source of truth.
- Procurement requires one vendor contract and a fixed scope.
- You need capabilities beyond static marketing pages.
Check the table against your own brief.
Describe the site in one sentence, choose a style and language set, then review the result on a preview link that needs no login and expires in 1–72 hours.