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.
Tip: Adding new bindings to your workers? Always update yourwrangler.jsoncmanifest at the workspace root, and then executehoox deploy update-internal-urlsto 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 — Drizzle schemas, R2 bucket configurations, and database rules.
- Production Deployments — How Wrangler compiles and maps these bindings to the live edge.