Remote bindings allow you to connect your local Worker code to deployed Cloudflare resources like R2 and D1. Come along on the technical journey of how we built this feature to create a seamless local development experience.

Cloudflare's platform is a leading provider of internet security and performance solutions, offering insights into web security, content delivery, and DNS management. Through documentation, blog posts, and webinars, Cloudflare provides insights into protecting websites and applications from cyber threats and improving performance. Developers and IT professionals can learn about CDN (Content Delivery Network), DDoS mitigation, and firewall configurations to secure and accelerate web traffic.

Cloudflare

Cloudflare's remote bindings feature allows developers to connect local Worker code to deployed production resources like R2 buckets and D1 databases without deploying for each iteration. The implementation leverages the existing service binding architecture, where the local runtime translates API calls to HTTP/JSRPC requests sent directly to production services. Developers can now selectively enable remote bindings per resource by adding 'remote: true' to their Wrangler configuration, combining the benefits of local development speed with access to real production data.

Connecting to production: the architecture of remote bindings

How bindings work under the hood in production

Remote bindings with Vite, Vitest and the JavaScript ecosystem