Skip to connect
Rankpug

Cloudflare migration assessment

Cut your cloud bill. Keep the savings.

Connect a read-only AWS role. We pull Cost Explorer, estimate what suitable workloads would cost on Cloudflare, and tell you what should stay put.

Connect AWSHow it works

Read-only IAM role. No passwords. Delete the stack to disconnect.

No AWS yet? Estimate instead.

Rough directional numbers from a bill split. Connecting AWS is more accurate.

$

USD. Minimum $100.

Main cloud provider
Approximate workload mix

Estimate how the monthly bill splits across these categories.

35%

Functions, containers billed as compute, and similar runtime cost.

15%

S3-style buckets, assets, and backups stored as objects.

20%

Egress, CDN, and content delivery traffic.

20%

Managed databases and related storage I/O. Kept conservative.

5%

Queues, workers, and asynchronous processing.

5%

Everything else on the bill.

Total 100%

Monthly outbound bandwidth
Architecture complexity

Migration opportunity

Migration opportunity by workload category
WorkloadCurrent spendAddressableEstimated savings
Compute / serverless$1,750$1,050$578
Object storage$750$563$309
CDN / bandwidth$1,000$900$630
Database$1,000$200$60
Queues / background jobs$250$125$56
Other$250$25$5
Total$5,000$2,863$1,638

Want us to verify the numbers?

We can review your architecture and identify the workloads that are actually worth moving.

How it works

Find the AWS workloads that cost too much. Move the ones Cloudflare can run for less. Leave the rest.

  1. 01

    Find the expensive workloads

    Connect a read-only AWS role. We pull Cost Explorer and isolate compute, storage, bandwidth, databases, and background jobs instead of treating the invoice as one number.

  2. 02

    Model the Cloudflare replacement

    Map only the pieces that have a clear Cloudflare counterpart — Workers, R2, CDN, Queues — and leave the rest alone.

  3. 03

    Migrate only where the economics make sense

    We may recommend leaving some workloads where they are. The goal is a lower bill, not a complete replatform.

Common migration targets

These are the mappings we see most often. They are starting points, not a promise that every service should move.

  • S3R2
  • CloudFrontCloudflare CDN
  • LambdaWorkers
  • Static hostingWorkers
  • Some queues and background jobsCloudflare Queues and Workflows

Some workloads should remain on AWS. Large databases, private networking, and tightly coupled platform services often stay put because the migration cost exceeds the savings.

We make money when we save you money.

For qualified migrations, pricing can be based on a share of verified first-year savings. We do not quote a percentage until we have reviewed the architecture and confirmed what is actually worth moving.

Get an assessment