Plan: turning deployments on is a paid monthly plan
Like Workers for Platforms: a monthly fee with included usage, then per-unit billing. Since it costs money, it is recommended, never switched on without the workspace agreeing.
1 file+9−20/1 viewed
| 552 | 552 | from prepaid credit. `FREE_WHILE_BUILDING` and the free model allowance | |
| 553 | 553 | do not cover deployments: a workspace without credit cannot deploy, and | |
| 554 | 554 | turning deployments on says so first. | |
| 555 | − | - **On by default, off in one click.** Deployments are recommended, not | |
| 556 | − | required: a repository can turn them off, keep only production, or | |
| 555 | + | - **Turning them on is a paid plan, the way Cloudflare's is.** "Including | |
| 556 | + | things like them even enabling the feature should have that pay like | |
| 557 | + | Cloudflare does." Enabling deployments for a workspace starts a monthly | |
| 558 | + | fee that includes an allowance of requests, CPU time and deployed apps; | |
| 559 | + | usage past it is billed per unit, as Workers for Platforms bills g1t. | |
| 560 | + | The fee and allowance are the user's to set. | |
| 561 | + | - **Recommended, off in one click.** Because enabling costs money, it is | |
| 562 | + | never switched on without the workspace agreeing: new repositories | |
| 563 | + | recommend it prominently. A repository can turn it off, keep only production, or | |
| 557 | 564 | deploy somewhere else from its own workflows. Apps built for Cloudflare | |
| 558 | 565 | (Workers, static assets, D1, KV, R2) deploy without configuration. | |
| 559 | 566 |