Cloudflare Dashboard + BulkFlare
Cloudflare is the source of truth. BulkFlare is the operations layer.
Use Cloudflare for direct product control. Use BulkFlare when the same careful change needs to reach many domains.
One account at a time
Acme StudioNorthstar LabsAnother account
Open the account, find the domain, repeat the change.
One reviewed batch
atlas.exampleorbit.examplepulse.example
Select → Review → Apply → Results
Keep selected domains and their outcomes together.
Illustrative workflow comparison; no speed benchmark is implied.
Side by side
Choose the right workspace for the job.
| Decision point | Cloudflare Dashboard | BulkFlare |
|---|---|---|
| Best operating mode | Direct product control when one zone needs a precise setting, investigation, or product-specific change. | Repeatable portfolio operations when many zones need the same review, preview, queue, and outcome trail. |
| Single-zone vs multi-zone work | Powerful zone-by-zone controls, but operators still move between domains for repeated work. | Select many zones, run guided workflows, and keep every affected domain visible in one result surface. |
| Risk before mutation | The dashboard is ideal for direct configuration, but repeated changes can become manual and hard to compare. | Preview-first flows, typed confirmations, and queue status slow down dangerous clicks before live traffic changes. |
| Permissions | Cloudflare owns the token and permission model, including the exact scopes a token can receive. | BulkFlare translates missing scopes into workflow-specific permission bundle guidance and retry paths. |
| DNS and security visibility | Deep product pages expose the source data, settings, analytics, and policy controls. | Operator checklists summarize DNS Health, analytics limits, WAF posture, and readiness signals across selected zones. |
| Data custody | Cloudflare remains the system of record for operational resources, settings, logs, certificates, DNS, and analytics. | BulkFlare stores encrypted credentials, limited metadata, cache snapshots and workflow records while Cloudflare remains the source of truth. |
| Result reporting | Single actions are visible in their product context, with audit data available through Cloudflare surfaces. | Bulk work reports succeeded, skipped, failed, missing permission, and retry-ready outcomes per zone. |
Use Cloudflare directly when...
- You are changing one zone and need the full Cloudflare product surface.
- You need a product setting or diagnostic BulkFlare does not expose yet.
- A specialist wants to inspect a single Cloudflare feature in detail.
- You are creating or managing the Cloudflare API token itself.
Use BulkFlare when...
- You manage many client, product, or acquired domains.
- The same DNS, redirect, cache, Worker, or security change repeats across zones.
- You need previews, confirmations, queue status, and per-zone outcomes before stakeholders ask what happened.
- Missing permissions should become a clear upgrade path instead of a vague failed action.
- You want Cloudflare to remain the source of truth while BulkFlare runs requested work through Cloudflare APIs.
Your next bulk change starts here.
Connect your Cloudflare accounts to manage bulk changes and track results in one place.