Cloudflare compatibility
What runs on celld v0.6.2, what differs from Cloudflare, and what is out of scope. The governing rule is upstream's: celld rejects an unsupported configuration or API at deployment or first use. An unsupported feature that does not raise an error is a defect.
This page summarizes celld's own compatibility reference for the release the operator currently tracks, plus the notes that matter when celld runs under the operator. When the two disagree, upstream is authoritative.
Platform services
| Status | Services |
|---|---|
| Yes | Workers · Durable Objects · Durable Object Facets · Static assets · Cron Triggers · Dynamic Workers (Worker Loader) · KV · Queues · D1 · Workflows · R2 |
| Partial | Python Workers: fetch handlers on the Pyodide 0.28 runtime line |
| Experimental | Containers. The operator does not provision the nested container runtime that celld's Containers and Sandbox bindings need. |
| No | Workers AI · Vectorize · Hyperdrive · Browser Rendering · Email Workers |
Notes for operator-run fleets:
- Cron triggers run as one reserved cell per script, so ownership fencing fires each occurrence once per fleet, not once per pod. There is nothing for the operator to schedule.
- Runtime features follow the image. A deployment's manifest names the
runtime features it uses. Upgrade
spec.celld.imagebefore publishing a deployment that needs a newer release, and finish an image rollout before enabling the new features. See celld version upgrades. - Rolling back from v0.6.1 or newer requires removing Python deployments first.
Runtime APIs
| API | Status | Differences from Cloudflare |
|---|---|---|
| Fetch, Request, Response, Headers | Yes | No cache request option. Inbound request.cf has no edge fields (geolocation, colo, TLS). Content-Length is removed from Worker responses except for HEAD. A remote Durable Object call cannot retry once the request body has started streaming. |
| Bindings | Yes | Only the binding types of the supported services above. |
| Context | Yes | passThroughOnException() has no effect (there is no CDN fallback). ctx.facets exists only inside a Durable Object. |
| Handlers | Yes | No tail or email handlers. |
| RPC | Yes | A stub cannot cross an isolate boundary. An AbortSignal in a Durable Object RPC does not cross a node boundary. A remote RPC retries only when the failed attempt never started the method; use a stable operation ID for application retries. |
| Streams | Yes | An unclaimed, inactive HTTP stream expires after 60 seconds and then reports an error instead of EOF. |
| WebSockets | Yes | A WebSocket cannot move to a new cell owner: clients must reconnect. A 1 MiB budget per isolate input queue. acceptWebSocket() throws above 90% of the V8 heap limit. |
| Web Crypto | Yes | ECDSA is P-256 with SHA-256 only. Secret keys cannot use jwk with exportKey() or wrapKey(). Ed25519 and X25519 are supported. |
| Performance and timers | Yes | performance.timeOrigin is 0 and performance.now() matches Date.now(); both advance only at I/O boundaries. |
| Encoding, Web standards, WebAssembly, Console, HTMLRewriter, EventSource, MessageChannel | Yes | No documented differences. |
| TCP sockets | Yes | A socket cannot outlive its event. TLS verifies against the bundled Mozilla root store. celld does not block the ports Cloudflare blocks: fleet egress policy is yours to set. |
| Node.js compatibility | Partial | Implements assert, async_hooks, buffer, diagnostics_channel, events, fs (request-local /tmp, read-only /bundle), os, path, stream, timers/promises, util; crypto and zlib (sync gzip/deflate) partially. Importing another built-in succeeds, but its first call throws. |
| Cache | Partial | An always-miss cache: there is no shared edge cache. put() stores nothing, match() returns undefined. |
| BroadcastChannel | No | The class exists so bundles load; its constructor throws. |
Documented no-ops. A few calls succeed and do nothing, by design:
ctx.passThroughOnException(), the always-miss Cache API, and compatibility
flags celld does not model. Unmodeled flags are accepted without effect and left out of
Cloudflare.compatibilityFlags rather than reported as enabled.
Wrangler configuration
celld deploy accepts wrangler.jsonc or wrangler.json
(not wrangler.toml). The name must be 1 to 63 lowercase letters,
digits, or internal hyphens. Accepted top-level keys:
$schema · name · main · no_bundle · compatibility_date · compatibility_flags
durable_objects · migrations · assets · services · triggers · vars
d1_databases · kv_namespaces · queues · workflows · r2_buckets
worker_loaders · containers · define · rules
Any other top-level key, including routes, stops the deployment with an
error that names it. Run celld deploy . --dry-run in CI so unsupported
configuration fails on the pull request, never at runtime. Routing is the operator's job:
use spec.hostnames.
Honored compatibility flags: delete_all_deletes_alarm, js_rpc,
fetcher_no_get_put_delete, sqlite_vec,
websocket_standard_binary_type, and the static-assets navigation flags.
Variables
celld v0.5 and newer read Worker variables from the deployment's Wrangler
vars and refuse to start with CELLD_VARS_FILE set. The operator
therefore rejects spec.vars for those images. Keep variables in the project
and publish them with celld deploy; they live with the deployment in the
fleet bucket, under the same credential that already controls the fleet.
Entity, not process
Durable-execution engines (Temporal, Restate, Azure Durable Functions) model a process: a workflow that runs to completion. A cell models an entity: a user, a room, a document, an agent. It is a small stateful server that lives as long as its name does. If your domain decomposes into named entities, cells shard it by construction.