Cloudflare Workers
Rust query engine incompatibility with edge runtime platforms
8The Prisma Rust query engine makes Prisma undeployable to Cloudflare Workers and other edge runtime environments, limiting platform compatibility.
Workers cannot securely connect to VPC-isolated resources
8Organizations cannot use Cloudflare's Developer Platform for applications with AWS resources or other infrastructure within VPCs, as Workers lack secure connectivity to VPC-isolated environments. This is a blocker for enterprise adoption.
Cloudflare abuse infrastructure (pages.dev/workers.dev) enables phishing and credential harvesting at scale
8Cloudflare's free developer domains (pages.dev and workers.dev) have become a platform for brand-impersonation, phishing kits, and credential-harvesting campaigns. Pages.dev incidents rose 198% (460→1,370) and workers.dev by 104% (2,447→4,999) in 2024, with multiple security vendors documenting widespread abuse. Researchers report <30% takedown rates despite submitting hundreds of reports.
No native HTTP imports support in Cloudflare Workers
7Cloudflare Workers lacks native support for HTTP imports, which is a significant blocker for developers wanting to use the platform for certain use cases.
Connectivity issues between serverless functions and traditional databases
7Traditional database setups (like RDS instances) are often not connected to the internet by default, making it extremely difficult to connect serverless compute platforms like Cloudflare Workers to them. This creates a significant operational burden for modern development workflows.
High latency for geographically distributed database queries from Workers
6When Workers execute multiple database queries, each request must traverse globally (e.g., Australia to Europe repeatedly), combined with per-request connection establishment, resulting in significant latency penalties.
Sandbox reuse complexity and data isolation concerns
6Reusing containers/sandboxes in serverless platforms requires worrying about data leaking between different uses, adding complexity and cost to the implementation.
Cloudflare benchmark discrepancies and performance variance
5Cloudflare's published benchmarks showing superior performance were contradicted by independent testing, with third-party benchmarks indicating Cloudflare could be 3-3.5x slower for CPU-intensive JavaScript workloads, raising questions about real-world performance claims.
Pages platform lacks Workers feature parity
4Cloudflare Pages, the go-to for hosting static and full-stack websites, lacks access to features like Durable Objects (without creating separate Workers) and Workers Logs, limiting functionality compared to the Workers platform.