# AgentCell vs Cloudflare Workers and Pages

> Workers is the most small-software-friendly primitive in existence — and it's developer infrastructure, not an app platform. Assembling Workers + Access + custom UX is the DIY version of AgentCell.

Published: 2026-09-19  
Canonical: https://agentcell.dev/resources/vs-cloudflare-workers  
Markdown: https://agentcell.dev/resources/vs-cloudflare-workers.md

> **TL;DR verdict:** Use Cloudflare Workers/Pages when you want the cheapest serious primitive (100k req/day free, $5 floor, no seats) and your team can assemble the rest. Use AgentCell when "the rest" — per-app sharing, agent tool-calls, Python runtimes, one bill — is exactly what you don't want to build. Full disclosure: we prototype on Cloudflare primitives and rate Cloudflare our most credible competitor.

## Where Cloudflare wins (honestly)

- **Idle economics.** Active-CPU billing on isolates is the closest thing to "always on, nearly free when idle" — ≈$0 incremental per app past the $5/mo floor. Our own serving tier is shaped by this math.
- **Velocity.** Sandbox SDK (GA April 2026), Dynamic Workflows (May 2026, marketed nearly verbatim as our thesis: per-tenant execution at near-zero idle cost), Workers for Platforms. Nobody ships platform primitives faster.
- **No seats.** 100k requests/day free, then a flat floor — the friendliest meter in the industry for tiny workloads.

## What you still assemble (the DIY list)

Workers is infrastructure; a shared team tool needs a product around it:

1. **Per-app sharing.** Cloudflare Access does org-internal Zero Trust (50 users free, then $7/user/mo) — but needs IdP integration and policy fluency, and fails at ad-hoc sharing with someone outside the org. Per-app guest lists with revocation are your code.
2. **Agent operation.** No `deploy-from-folder`, no MCP tool-calls, no structured agent-legible errors. Your agent scripts the API and parses HTML errors.
3. **Python.** The cheapest tiers are JS/TS/WASM-only. Streamlit and FastAPI tools need Containers or external compute — with real idle cost attached.
4. **One object per tool.** Cells, share lists, per-cell logs, caps, and bills arrive as separate services to wire, not one mental object.

That assembly is a fine weekend project for a platform engineer. It is the entire operator tax we're eliminating for everyone else.

## The strategic honesty box

Two statements, both true: **we build on Cloudflare's primitives** (Workers for Platforms, Sandbox SDK, Durable Objects, Containers — fastest path, removes sandbox hardening, only idle economics that make twenty tools viable) **and Cloudflare is our primary strategic threat.** Dynamic Workflows is pitched at per-tenant execution at near-zero idle cost; if Cloudflare ships polished "publish and share your AI-built app" UX on top, most of our differentiation window closes. Mitigations: work with every agent and framework (neutrality Cloudflare can't match without favoring its own), get to cheap org identity first, and architect so the compute vendor is swappable (OpenSandbox/microsandbox as documented fallback).

## Side-by-side

| | Cloudflare Workers/Pages + Access | AgentCell |
|---|---|---|
| Primitive cost | Best in class (≈$0 idle) | Same economics, packaged per cell |
| Per-app sharing | DIY (Access policies + your code) | Share list built in |
| Agent deploy (MCP/CLI) | DIY scripts | Primary interface |
| Python cells | Containers / external (real idle $) | Detection + measured idle (pre-launch numbers) |
| Auth for outsiders | Breaks (org-internal shape) | Named guests, groups, public links |
| Best for | Engineers assembling their own platform | Teams that want the platform assembled |

## Fit checklist

**Use AgentCell when:** the team has no platform engineer to spare; sharing includes outsiders; Python tools must idle cheaply without container ops.

**Stay on Cloudflare when:** the team already runs Zero Trust well; workloads are JS/edge-shaped; assembling primitives is a feature, not a cost.

## FAQ

**Are you just a wrapper on Cloudflare?**
The compute foundation leverages their primitives; the product — share lists, agent control plane, membrane, per-cell everything — is ours and vendor-swappable by design.

**What if Cloudflare launches exactly this?**
Then the category is validated by the best infrastructure company alive, and we compete on neutrality (every agent, every framework), org-identity pricing, and focus. That is the top risk in our founding document, stated openly.

---

*Want Cloudflare's economics without assembling the platform? [Deploy now](/docs/deploy/).*