1# Cloudflare Workers for Platforms
2 
3Multi-tenant platform with isolated customer code execution at scale.
4 
5## Use Cases
6 
7- Multi-tenant SaaS running customer code
8- AI-generated code execution in secure sandboxes
9- Programmable platforms with isolated compute
10- Edge functions/serverless platforms
11- Website builders with static + dynamic content
12- Unlimited app deployment at scale
13 
14**NOT for general Workers** - only for Workers for Platforms architecture.
15 
16## Quick Start
17 
18**One-click deploy:** [Platform Starter Kit](https://github.com/cloudflare/workers-for-platforms-example) deploys complete WfP setup with dispatch namespace, dispatch worker, and user worker example.
19 
20[![Deploy to Cloudflare](https://deploy.workers.cloudflare.com/button)](https://deploy.workers.cloudflare.com/?url=https://github.com/cloudflare/workers-for-platforms-example)
21 
22**Manual setup:** See [configuration.md](./configuration.md) for namespace creation and dispatch worker configuration.
23 
24## Key Features
25 
26- Unlimited Workers per namespace (no script limits)
27- Automatic tenant isolation
28- Custom CPU/subrequest limits per customer
29- Hostname routing (subdomains/vanity domains)
30- Egress/ingress control
31- Static assets support
32- Tags for bulk operations
33 
34## Architecture
35 
36**4 Components:**
371. **Dispatch Namespace** - Container for unlimited customer Workers, automatic isolation (untrusted mode by default - no request.cf access, no shared cache)
382. **Dynamic Dispatch Worker** - Entry point, routes requests, enforces platform logic (auth, limits, validation)
393. **User Workers** - Customer code in isolated sandboxes, API-deployed, optional bindings (KV/D1/R2/DO)
404. **Outbound Worker** (optional) - Intercepts external fetch, controls egress, logs subrequests (blocks TCP socket connect() API)
41 
42**Request Flow:**
43```
44Request → Dispatch Worker → Determines user Worker → env.DISPATCHER.get("customer") 
45→ User Worker executes (Outbound Worker for external fetch) → Response → Dispatch Worker → Client
46```
47 
48## Decision Trees
49 
50### When to Use Workers for Platforms
51```
52Need to run code?
53├─ Your code only → Regular Workers
54├─ Customer/AI code → Workers for Platforms
55└─ Untrusted code in sandbox → Workers for Platforms OR Sandbox API
56```
57 
58### Routing Strategy Selection
59```
60Hostname routing needed?
61├─ Subdomains only (*.saas.com) → `*.saas.com/*` route + subdomain extraction
62├─ Custom domains → `*/*` wildcard + Cloudflare for SaaS + KV/metadata routing
63└─ Path-based (/customer/app) → Any route + path parsing
64```
65 
66### Isolation Mode Selection
67```
68Worker mode?
69├─ Running customer code → Untrusted (default)
70├─ Need request.cf geolocation → Trusted mode
71├─ Internal platform, controlled code → Trusted mode with cache key prefixes
72└─ Maximum isolation → Untrusted + unique resources per customer
73```
74 
75## In This Reference
76 
77| File | Purpose | When to Read |
78|------|---------|--------------|
79| [configuration.md](./configuration.md) | Namespace setup, dispatch worker config | First-time setup, changing limits |
80| [api.md](./api.md) | User worker API, dispatch API, outbound worker | Deploying workers, SDK integration |
81| [patterns.md](./patterns.md) | Multi-tenancy, routing, egress control | Planning architecture, scaling |
82| [gotchas.md](./gotchas.md) | Limits, isolation issues, best practices | Debugging, production prep |
83 
84## See Also
85- [workers](../workers/) - Core Workers runtime documentation
86- [durable-objects](../durable-objects/) - Stateful multi-tenant patterns
87- [sandbox](../sandbox/) - Alternative for untrusted code execution
88- [Reference Architecture: Programmable Platforms](https://developers.cloudflare.com/reference-architecture/diagrams/serverless/programmable-platforms/)
89- [Reference Architecture: AI Vibe Coding Platform](https://developers.cloudflare.com/reference-architecture/diagrams/ai/ai-vibe-coding-platform/)
90