tech/cloudflare/workers-for-platforms

To build a multi-tenant Cloudflare Workers environment, you use dispatch namespaces to route requests through a central Worker to customer-specific Workers. This isolates tenant code and data while maintaining separate namespaces and billing for each customer.

A dispatch namespace in Cloudflare Workers is an isolated execution boundary for tenant-specific Workers. You need it when building a platform where customers deploy their own code, ensuring separate rate limiting, CPU limits, and controlled infrastructure access.

You deploy tenant-specific Workers from a single Cloudflare account by initializing a dispatch namespace and using the Cloudflare API. A central Worker you control routes incoming requests to the appropriate tenant-specific Worker for isolated execution.

Yes, you can enforce separate billing and resource limits per tenant in Cloudflare Workers. By utilizing dispatch namespaces, the infrastructure applies distinct rate limiting and CPU limits for each tenant's isolated code execution environment.

Cloudflare Workers supports tenant isolation for customer-deployed code through its Workers for Platforms feature. It separates dispatch namespaces and routes requests to customer-specific Workers, ensuring full isolation between customers' code and data.