Facts read November 6, 2026
Cloudflare Workers vs Render
Cloudflare Workers is Cuely's default hosting pick when your description doesn't favor either one: very low cost at scale with no egress charges. Pick Render if you care most about background jobs and long-running servers.
Side by side
| Fact | Cloudflare Workers | Render |
|---|---|---|
| What it is | Serverless functions that run on Cloudflare's edge network. | Managed hosting for long-running web services, workers, cron jobs and Docker containers. |
| Free plan | Workers Free: 100,000 requests per day and 10 ms of CPU time per invocation. | Hobby workspace: free web services (512 MB RAM, 750 instance hours/month, spin down after 15 minutes idle), 5 GB bandwidth, 500 build minutes per month. |
| Paid from | Workers Paid: $5/month minimum per account, including 10M requests and 30M CPU ms per month; then $0.30 per additional million requests. | $7/month for the smallest paid web service (512 MB RAM). |
| At 1,000 users | $0/month | $7/month |
| Open source | No | No |
| Self-hostable | No | No |
| Best for | Global low-latency APIs; High request volume on a small budget; Apps already on Cloudflare | Long-running servers and websockets; Background workers and cron jobs; Docker-based apps |
| Watch out | The Workers runtime is not full Node.js; some Node libraries and Next.js features need an adapter. Free plan caps CPU at 10 ms per invocation, and past 100,000 requests a day it returns error 1027 (or skips the Worker, if the route fails open). | Render's docs say not to use free instances for production; they spin down after 15 minutes idle. Free Postgres expires 30 days after creation. |
Where they differ
The published scores, from −3 to +3, that decide which one Cuely picks for each need.
| Need | Cloudflare Workers | Render |
|---|---|---|
| background jobs or long-running servers | −2 Invocations are CPU-time limited; use Queues or Containers for long work. | +3 Always-on services, background workers and cron jobs are first-class. |
| global low latency | +3 Code runs in Cloudflare's edge locations by default. | 0 No particular strength here. |
| keep costs as low as possible | +3 100k free requests a day, then $5/month covers 10M requests, with no egress charges. | 0 No particular strength here. |
| traffic comes in viral spikes | +2 Static assets are free and unlimited, and Paid ($5/month) includes 10M requests, then $0.30 per million. On Free, requests past 100,000 a day get error 1027. | −1 A fixed-size server doesn't absorb a sudden spike by itself; you size up or add instances ahead of time. |
| high volume | +2 Per-request pricing stays low at high volume and there are no data transfer charges. | 0 No particular strength here. |
| realtime features | 0 No particular strength here. | +2 Persistent servers hold websocket connections. |
| Next.js or React | −1 Next.js runs through an adapter, not natively. | 0 Runs Next.js as a Node server. |
Sources: Cloudflare Workers pricing (read November 9, 2026), Render pricing (read November 6, 2026). No vendor pays for placement.