Getting started
Integration keys
Nothing to configure to start — the platform's keys run your projects within your plan's monthly budget; your own keys lift the limit.
Published Updated 2 min read
Do you need keys?
No. Webhub works out of the box:
- Demo projects run on the platform's keys — no configuration at all. Each demo project has a small budget of its own, so you can explore research, domains and campaigns end to end.
- Production projects on a paid plan run on the platform's keys within your plan's monthly budget for provider calls: Starter $30, Growth $60, Scale $150. The budget covers LLM, DataForSEO keyword data and article images. It resets on the 1st of every month (UTC).
Your current spend and the reset date are on Billing → Platform keys. When the budget is used up, research and content generation on platform keys pause with a clear "budget reached" message until the next month.
Your own keys lift the limit
Add your own keys in Settings → Integrations and that integration is never metered again:
| Integration | Used for |
|---|---|
| LLM (Anthropic or OpenAI) | Research synthesis, articles, domains |
| DataForSEO | Keyword volumes and competitor SERP data |
| Pexels / Gemini | Article images |
The order is always the same: your key → the platform's key → the server environment. Your key wins for its integration; the others keep running on the platform's keys.
Domains need your Cloudflare account
Hosting is ours: satellites are published to Cloudflare Pages on the platform's account, including their DNS. Buying domains is different — the money leaves your own account, so registration uses your Cloudflare API token and account ID (add them under Settings → Integrations → Cloudflare). Free *.pages.dev hosts and domains you already own work without it.
Demo vs production
- Demo projects never buy domains and stay in the sandbox — see Demo projects.
- Production projects use real providers: the platform's keys within your plan's budget, or your own.
Security tips
- Treat keys like passwords; only owners and admins of the organization should add them.
- Rotate a key in the provider's console if it leaks, then save the new one here.
- Never commit keys to git — use Settings → Integrations only. Saved keys are stored server-side and shown masked.