Launch
Usage-based · settled from your wallet
- One property, from prompt to deploy
- Chat edits and file-level control
- Custom domain and preview links
- Forms, chat and analytics included
Transparent usage billing
You pay for what runs. The ledger shows every unit.
CloudSite has no mystery invoice. Each site generation and each confirmed campaign send draws from your wallet balance, and every amount is stored in fen — the smallest unit, not a rounded story.
Three ways to operate
Same platform. Different volume.
Tiers describe how much you run through CloudSite, not which features are locked away. The toolset is identical on all three.
Operate
Usage-based · settled from your wallet
- Properties for each campaign or region
- Up to 4 languages on every site
- Campaigns with preflight and quotes
- Leads, subscribers and exports together
Scale
Usage-based · settled from your wallet
- Many properties under one workspace
- Agent operations across 75 MCP tools
- Read-only and read-write tokens
- Exports for internal reporting
Feature matrix
What every plan includes.
Read across, not down. The build, publish, reach and measurement surface stays the same; your balance absorbs the usage.
| Capability | Launch | Operate | Scale | Notes |
|---|---|---|---|---|
| Build | ||||
| AI site generationOne sentence becomes a complete site | ✓ | ✓ | ✓ | 1–3 minutes |
| Chat-based editingChange pages conversationally | ✓ | ✓ | ✓ | chat_site |
| File-level controlList, read, write, delete | ✓ | ✓ | ✓ | 2 MB per file |
| Publish | ||||
| Deployment targetsCloudflare Pages or Firebase Hosting | ✓ | ✓ | ✓ | Both supported |
| Custom domainsCNAME written on Cloudflare | ✓ | ✓ | ✓ | Automatic |
| LanguagesMultilingual properties | ✓ | ✓ | ✓ | Up to 4 per site |
| Preview linksShare without an account | ✓ | ✓ | ✓ | 1–72 hours |
| Reach | ||||
| Campaigns and listsSubscribers, templates, providers | ✓ | ✓ | ✓ | Preflight before send |
| Sending controlsQuote first, then explicit confirmation | ✓ | ✓ | ✓ | confirm=true |
| Forms and chatCustom fields, visitor threads | ✓ | ✓ | ✓ | Leads included |
| Measure | ||||
| AnalyticsTraffic, events, subscriptions | ✓ | ✓ | ✓ | One workspace |
| Exports and agent accessRecords and scoped tokens | ✓ | ✓ | ✓ | 75 MCP tools |
Amounts are stored as
value_fen and balance_fen, never as rounded display text.Wallet debits are itemised by action.Billing behaviour
No charge without a line.
01
Quote before send
Campaigns run a preflight and return a cost quote before anything leaves the platform. You see the estimate first.
02
Confirm explicitly
A real send requires confirm=true. Quoting alone never spends from the wallet balance.
03
Read the balance
Generation and sending debit the same wallet. Amounts are kept in fen, so the ledger reconciles with what was charged.
Start on the platform, not on a sales call.
Generate a site, inspect the wallet ledger, then decide how much you want to run.