Provisioning & lifecycle
How a project is provisioned, and the operations that manage it through its life — pause, resume, retry, admin re-provision, and delete.
What provisioning does
Section titled “What provisioning does”Creating a project kicks off provisioning against Workers for Platforms:
- A
proj-<slug>user worker is created in the dispatch namespace from the published worker template. - Its D1 database and R2 storage are created and bound.
- A one-time admin credential is generated and handed to the project’s own admin.
- The chosen template seeds an initial collection set (if any).
- The instance goes live at
<slug>.backlex.com.
A deploy record is written for the provision, so the first deploy shows in the project’s deploy history. Most projects are live in well under a minute.
Lifecycle operations
Section titled “Lifecycle operations”| Action | Effect | Min role |
|---|---|---|
| Pause | Stops traffic + billing for the instance | admin |
| Resume | Restores a paused instance | admin |
| Retry provisioning | Re-runs provisioning for a failed project | admin |
| Re-provision admin | Regenerates the project admin credential | admin |
| Delete | Soft-deletes (recoverable within the retention window) | admin |
| Update | Rename, change environment | admin |
Every operation is recorded in the audit log with the actor, target, and source IP.
Templates
Section titled “Templates”A project can be created from a vertical template (blog, e-commerce, SaaS, CRM, …) or blank. The cloud passes the chosen template id through to the new instance, where the project admin applies it as a ready-to-use collection set. Blank starts with only the system schema.
Pausing vs deleting
Section titled “Pausing vs deleting”Pause when you want to stop the meter but keep everything in place — resume restores it instantly. Delete when you’re done; it’s a soft delete, so it can be recovered until the retention window lapses, after which the underlying resources are torn down.