The Cloudflare operations layer

Stop repeating changes across Cloudflare accounts.

Update selected domains in one place and see which changes need attention.

Start with your Cloudflare accountExplore the workflows
BulkFlareSample workspace Support Quick Actions A
2 connected Cloudflare accounts
All accounts
AnalyticsDomainsDNSEmailRedirectsWorkersSecurity
Search domains or DNS records… Filters Columns
4 domains selectedAcross 2 Cloudflare accounts
DNS changes
DomainDNS records
atlas.exampleAcme Studio
8 records
orbit.exampleAcme Studio
12 records
nova.exampleAcme Studio
8 records
pulse.exampleNorthstar Labs
12 records
ember.exampleNorthstar Labs
8 records
helio.exampleNorthstar Labs
12 records
6 domains · 2 accountsPage 1 of 1

Only selected domains are included in the change.

01 / 05
Choose domainsSet up changesReview and applyQueuedResults

Choose exactly which domains to update, across connected accounts.

  1. Choose domains. Choose exactly which domains to update, across connected accounts.
  2. Set up changes. Enter the DNS change once. Keep the rest of your records as they are.
  3. Review and apply. Review the account, domain and before-and-after values before applying.
  4. Queued. Your batch is saved. Follow its progress in DNS change status.
  5. Results. See confirmed changes and failures separately. DNS caches may still be updating.

One careful process

Less repetition. More certainty.

From the first selection to the last result, keep the important decisions in view.

Acme Studio2 selected
Northstar Labs2 selected

Choose the scope.

Work across connected accounts. Only the domains you select are included.

A record · @
192.0.2.10192.0.2.24
Review before applying

See what will change.

Check the intended change and its targets before you confirm.

atlas.exampleConfirmed
ember.exampleNeeds attention

Keep every result.

Successful, failed and unresolved changes stay distinct so you know what needs attention.

Compare with Cloudflare Dashboard

See BulkFlare at work

A familiar task. A much clearer flow.

DNS, onboarding, security, redirects and Worker routes, brought into one workspace.

Two accounts. One place to work.

Explore All Accounts
BulkFlareSample workspace Support Quick Actions A
Alex Morganalex@studio.example
Connected Cloudflare Accounts Connect new
Acme Studio
Account ID: …c04a
Current Disconnect
Sign out
01 / 05
Add accountChoose accessAuthorizeBoth connectedManage together

Open your account menu and choose Connect new to add another Cloudflare account.

  1. Add account. Open your account menu and choose Connect new to add another Cloudflare account.
  2. Choose access. Choose Continue with Cloudflare and review the workflow bundles you want to authorize. This example uses Foundation and DNS Ops.
  3. Authorize. Select your second account in Cloudflare, review the requested permissions, and approve the connection.
  4. Both connected. Back in BulkFlare, both accounts appear in your account menu. Choose Manage all accounts.
  5. Manage together. Search and select domains from both accounts in one workspace. Every domain keeps its owning account; choose an action when you are ready.

Built around your control

Cloudflare stays the source of truth.

You choose the accounts and permissions. BulkFlare keeps encrypted credentials, limited metadata, cache snapshots and operation records needed to run and explain your work.

Review the trust model

Built for portfolio work

For the teams behind many domains.

Agencies, platform teams and operators handling migrations can use the same reviewed process across their Cloudflare accounts.

View use casesChange records across many zones

Your next bulk change starts here.

Connect your Cloudflare accounts to manage bulk changes and track results in one place.

Start freeCompare plans