Skip to content
open-computeopen-computeopen-compute

Compatibility

Current Cloudflare Workers compatibility and the intentional single-node differences in open-compute.

open-compute implements the declared Cloudflare Workers programming model on one node. Worker code and supported bindings follow Cloudflare’s public APIs; placement, replication, quotas, and management remain local to the selected ocd authority.

Inspect the exact running release:

Terminal window
ocd capabilities --json

With --config <absolute-path>, configured limits come from that file. Without it, the command reports the embedded defaults.

  • Module Workers, Versions, Deployments, Static Assets, Service Bindings, Version Metadata, WebSockets, and the documented runtime APIs
  • KV, D1, R2, Durable Objects, Alarms, Queues, Cron, Workflows, Workers Cache, and Cache API
  • Images, Vectorize, AI Search, Markdown Conversion, Workers Logs/realtime tail, and Artifacts
  • Cloudflare-compatible /client/v4 management APIs, the certified Wrangler workflow, and the operator Dashboard

Most products are reported as supported_with_deviation because they use a single local authority instead of Cloudflare’s hosted global topology. Vectorize uses deterministic exact search. AI Search and Markdown Conversion use operator-configured providers; full Workers AI inference is not implied.

The release embeds a checksum-verified elliothux/workerd fork selected by the formal runtime lock. Production startup remains offline. Projects use standard wrangler.jsonc and project-local Wrangler. Compatibility dates and flags are admitted only when the current runtime contract supports them.

Dynamic Worker Loader support is native but remains bounded by the documented missing CPU, memory, and subrequest enforcement. It is not a claim of the complete Workers for Platforms product.

See Products, Behavior differences, Limits, Not available, and the generated Worker API index.