AWS Amplify vs Cloudflare Workers

Wrangler CLI makes Worker deployment fast. The runtime and its constrained API surface require a learning curve before the first production deployment.

AWS IAM configuration, console navigation, and Amplify-specific concepts add significant friction. First deployment for a team new to AWS typically takes hours, not minutes.

Cloudflare Pages offers native git integration with auto-deploy on push and PR preview deployments. Workers (without Pages) require Wrangler or CI integration.

Git-connected deployments and branch previews are supported. The workflow is functional but requires more manual configuration and IAM setup to work correctly.

Wrangler is one of the best CLIs in the deployment space. Deploy, manage secrets, tail live logs, run local dev environments, and interact with KV/R2/D1, all from the terminal.

Amplify CLI and the newer Amplify Gen 2 CDK-based tooling are capable but complex. Managing permissions, environments, and backends requires deep AWS CLI familiarity.

The Cloudflare dashboard is powerful but complex. Managing Workers, Pages, R2, KV, and D1 across a large account requires familiarity. Onboarding is not intuitive.

The AWS console is powerful but overwhelming. Finding Amplify Hosting settings across the AWS console, Amplify dashboard, and CloudFront configuration requires significant AWS experience.

Cloudflare delivers static assets via Cloudflare's 300+ PoP CDN. Sub-10ms cache hits globally. Custom headers and redirects via _headers and _redirects files.

CloudFront-backed static hosting with global CDN, custom headers, and redirect rules. Infrastructure is enterprise-grade though the setup experience is more involved than frontend-focused platforms.

Every branch and PR gets a unique preview URL on Cloudflare Workers. Preview deployments are fast, reliable, and shareable with clients.

Branch-based preview deployments with unique URLs are supported. PR previews available via GitHub integration. Functional but requires IAM setup to work correctly.

Supports configurable build commands, environment variables per deployment context, and integration with most CI/CD tooling. Build times are fast.

Configurable build spec (amplify.yml), environment-specific builds, caching, and build environment variables. Build times are solid across most project types.

Zero-config presets for Astro, Next.js, Nuxt, Remix, and SvelteKit. Next.js support via the next-on-pages adapter is functional but not fully feature-complete.

Works with Next.js, Astro, Vue, and React. Framework detection exists but setup is more manual. SSR and ISR are supported through CloudFront edge functions.

The best serverless execution model available. Eliminate cold starts entirely. 128MB memory, 30s CPU time on paid. 300+ global locations. Exceptional performance.

Serverless functions run on AWS Lambda under the hood. Cold starts on the Node.js runtime are 200-500ms. Amplify abstracts this but teams still encounter the underlying runtime constraints.

Workers are request-scoped, no persistent state between requests. Cloudflare Containers adds Docker support but the primary model remains stateless serverless.

Amplify Gen 2 supports ECS-backed services for longer-running workloads. Requires significant infrastructure configuration, not a zero-config path for persistent backends.

Cloudflare Containers launched in 2025 allowing Docker-based services. Still maturing, not yet a practical choice for teams needing persistent backend services.

ECS/Fargate integration via the CDK allows container deployments within AWS. More complex to configure than purpose-built container platforms but integrates with the full AWS ecosystem.

Cloudflare Queues provides message queue processing. Cron Triggers schedule recurring Workers execution. Background job support is native but still maturing relative to the core serverless offering.

EventBridge, SQS, and Lambda cron triggers are available through the AWS ecosystem. Native within Amplify but requires AWS-level configuration, not a simple, platform-managed experience.

300+ PoPs globally with one of the broadest geographic footprints available. Assets served sub-10ms worldwide for most users. CDN infrastructure is Cloudflare's core business.

CloudFront is one of the world's largest CDN networks with 600+ PoPs. Exceptional global reach and enterprise-grade performance for static asset delivery.

True edge execution, Workers run in the data center closest to each user, not just a few regions. Best-in-class for A/B testing, auth, personalisation, and middleware.

Lambda@Edge runs at CloudFront PoPs for request/response manipulation. Powerful but heavyweight, cold starts at the edge are more significant than with isolate-based runtimes.

Zero cold starts. spins up in microseconds, users never experience the multi-hundred-millisecond delays common with container-based serverless runtimes.

Standard Lambda cold starts of 200-500ms. Lambda@Edge has additional cold start overhead. No zero-cold-start equivalent, container-based runtimes have inherent startup latency.

Consistently top-tier for global API response times. Edge execution from 300+ locations delivers P99 latencies that region-bound serverless platforms cannot match.

CloudFront CDN ensures fast static asset delivery globally. Serverless API response times are solid when functions are warm, cold starts are the main latency variable.

D1 (SQLite at the edge), KV (key-value), and Durable Objects (stateful edge). D1 is now GA and suitable for many use cases. Traditional PostgreSQL requires an external provider.

Access to the full AWS database ecosystem; RDS (PostgreSQL, MySQL), DynamoDB, ElastiCache, Aurora. One of the most comprehensive managed database offerings available to developers.

R2 (S3-compatible object storage with no egress fees) is excellent. Global distribution, standard S3 API compatibility, and highly competitive pricing, especially at volume.

Amplify integrates with S3, CloudFront, and AWS Transfer Family. S3 is one of the most battle-tested object storage services available, highly capable and globally distributed.

D1 replicates globally, reads happen at the nearest PoP. KV and Durable Objects are also edge-native. No compute-to-database latency for Workers using native Cloudflare data stores.

AWS region selection ensures compute and database are co-located. VPC private networking eliminates public internet latency between Lambda functions and RDS instances.

Environment variables and secrets managed via wrangler.toml or the Cloudflare dashboard. Per-environment configuration is supported. Secrets are encrypted.

Environment variables managed across Amplify console, AWS Parameter Store, and Secrets Manager. Functional but scattered across multiple AWS services, not a unified experience.

_redirects file supports complex rules including splats and placeholders. For Workers, full HTTP control means any redirect logic is possible in code.

Redirect and rewrite rules configurable in the Amplify console or amplify.yml. Supports complex patterns and covers the full range of routing requirements.

_headers file support. Workers give full HTTP response control, set any header for any response. The most flexible platform-level header control available.

Custom response headers configurable at the CloudFront distribution level or per-path in Amplify. Full header control is available but requires more configuration steps.

Staging and production environments require separate Workers projects. Environment management is functional but requires more manual configuration to set up correctly.

Branch-based environments with separate env vars and domains. IAM-scoped team access per environment. More setup overhead, but scales well to large enterprise team structures.

Simple request-based pricing: free up to 100K requests/day, then $5/mo for 10M requests. R2 charges per operation with no egress fees. Highly predictable and transparent.

AWS pricing involves multiple dimensions; build minutes, data transfer, Lambda invocations, CloudFront requests, S3 storage. Forecasting the total monthly cost is genuinely difficult.

Request-based overages are gradual and proportional to traffic. No surprise bandwidth bills due to R2's no-egress-fee model. Spending controls available on paid plans.

AWS bills aggregate across many services without a single cap. A traffic spike can trigger CloudFront, Lambda, and S3 charges simultaneously. Budget alerts are essential but manual.

Exceptional value at scale. 10M requests for $5/mo is among the most competitive pricing available. R2's no-egress-fee model means storage costs stay predictable at volume.

Good value for teams already paying for AWS. Marginal cost for adding Amplify to an existing AWS account. Poor value for teams not already in AWS due to complexity overhead.

100K requests/day free on Workers, free D1 databases, and 10GB R2 storage free. Genuinely useful for real staging and low to medium traffic production sites.

AWS free tier includes limited Amplify build minutes, hosting, and data transfer. Functional for development but requires careful monitoring to avoid charges on early-stage projects.

Cloudflare's network is the infrastructure the internet runs on. Uptime is exceptional, one of the most reliable networks globally. Incidents are rare and resolved rapidly.

AWS infrastructure has one of the best uptime track records in the industry. CloudFront and S3 SLAs are enterprise-grade. Suitable for the most demanding production environments.

Workers require redeploying a previous version via Wrangler, a slightly more manual process.

Previous deployments are accessible in the Amplify console. Rollback requires redeploying a previous build; not instant. The process is functional but involves more steps than a one-click rollback.

Real-time log tailing via Wrangler and the dashboard. Log retention is limited by default. Workers Logpush to external providers is available but requires configuration.

CloudWatch provides comprehensive logging for Lambda functions, build processes, and access logs. Powerful but requires CloudWatch familiarity to use effectively.

Request rates, error rates, and CPU time metrics in the dashboard. Analytics Engine provides custom observability. Full APM requires external integration, Cloudflare's weakest area.

CloudWatch metrics, alarms, and dashboards provide enterprise-grade observability. X-Ray for distributed tracing. Full AWS monitoring stack available, overkill for small projects.

V8 isolate runtime, D1 (SQLite), KV, Durable Objects, and R2 are all Cloudflare-specific. Migrating a Workers-native app to a standard Node.js environment requires runtime adaptation.

Amplify Gen 2 uses CloudFormation for infrastructure, which is AWS-specific. Lambda, CloudFront, and IAM create dependencies across the AWS ecosystem.

Workers code using Web Standard APIs (fetch, crypto) ports reasonably well. Apps using D1, KV, or Durable Objects require more significant migration effort.

Application code is portable. Infrastructure configuration is AWS-specific. Migrating off AWS requires replacing configurations.

Workers uses Web Standard APIs (not Node.js), which is broadly transferable. However, Cloudflare-specific primitives (D1, KV, R2 bindings) are not open standards.

Standard Node.js runtime, Git, and S3-compatible storage. amplify.yml build spec is AWS-specific but straightforward to translate. Application code follows broadly standard conventions.

Cloudflare Workers is excellent for static and dynamic marketing sites.

CloudFront-backed hosting with preview deployments handles marketing site requirements. The setup overhead is unjustified unless the team is already operating in AWS.

Strong for stateless APIs and full-stack apps using Cloudflare's native data stores. Less suitable for apps requiring PostgreSQL, persistent processes, or background workers.

Strong for full-stack apps within the AWS ecosystem. Auth (Cognito), APIs (AppSync/API Gateway), storage (S3), and compute (Lambda) are all native integrations.

Excellent for technical teams; a bit harder to hand off to less experienced developers.

High IAM and AWS configuration complexity makes client handoff difficult. Best suited to enterprise clients with dedicated DevOps teams, not typical agency project use cases.