See /docs/devops/bindings

Stub — the canonical Cloudflare® Workers bindings registry lives at /docs/devops/bindings.

This page

Manuals

This document is now a stub. For the complete bindings registry, see /docs/devops/bindings.

In Cloudflare®'s serverless architecture, bindings represent the declarative bridges linking your isolate compute logic to other internal microservices and storage platforms. This page intentionally keeps only the high-level architectural framing; the canonical registry — every Service Binding, KV, R2, D1, Workers AI, Vectorize, Queue, Durable Object, and Browser Rendering entry — lives in docs/devops/bindings and is the single source of truth.

Copy account_id, KV namespace IDs, and D1 database IDs from your Wrangler account — never paste live IDs from another install. Use "<CLOUDFLARE_ACCOUNT_ID>" and "<KV_NAMESPACE_ID>" in examples.

Tip: Adding new bindings to your workers? Always update your wrangler.jsonc manifest at the workspace root, and then execute hoox deploy update-internal-urls to sync bindings and URLs globally!

🔗 Next Steps

Canonical Bindings Reference — Complete, up-to-date bindings table (service bindings, KV, R2, D1, AI, Vectorize, queues, DOs).
Storage & SQLite DDL — schema.sql, R2 bucket configurations, and database rules.
Production Deployments — How Wrangler compiles and maps these bindings to the live edge.