A deploy creates exactly what the project's manifest (leadmax.json) declares, on the Cloudflare account you chose in Settings, and reuses those resources on every later deploy. Names are derived from the project slug so you can find everything in your Cloudflare dashboard.
The resources
| Resource | Name | Created | Purpose |
|---|---|---|---|
| Worker | <slug> | Always | The app: server code plus static assets. Reachable at https://<slug>.<your subdomain>.workers.dev. |
| D1 database | leadmax-<slug> | When the project needs a database | Your app's data. The project's migrations/ folder is applied here, in order, before each new version goes live. |
| KV namespace | leadmax-<slug> | When the project uses caching | The framework's data cache (the CACHE binding). |
<slug> is the URL-safe name chosen when the project was created (visible in the dashboard). In the Cloudflare dashboard, the Worker is under Workers & Pages; the database and namespace are under Storage & Databases. If a resource with the expected name already exists (for instance after you deleted the project on LeadMax and created it again), the deploy reuses it rather than creating a duplicate.
New projects save available business photos through LeadMax without creating a photo bucket on your Cloudflare account. Filebase is optional for your own photo storage and owner uploads. Photos stored by LeadMax continue to use its media service after publication.
What a deploy does, step by step
- Snapshot. The current revision of your project is frozen; the deployment references it forever.
- Build. Your browser builds the selected revision and sends the compiled files for publishing. Keep the editor open until this step finishes. The build log shows progress.
- Token check. Your Cloudflare token is refreshed and checked for the required scopes. If a scope is missing or the token cannot be refreshed, the deployment stops in needs re-authorization and Settings tells you what to do.
- Provision. The D1 database and KV namespace are created on your account as needed, or reused by name. Their identifiers are saved for later deploys.
- Migrate. The migrations in your project's
migrations/folder that have not run yet are applied to your D1 database. This happens before the new code goes live, so a failed migration leaves the previous version running. - Upload. The Worker and its static assets are uploaded to your account with the bindings wired up, and the
workers.devURL is switched on if this is the project's first deploy. - Record. The live URL, the Cloudflare version id and the duration are saved with the deployment.
Deploys run through a queue with workspace concurrency limits. A deploy that exceeds the time budget is marked failed with its log rather than left hanging.
Removing what LeadMax created
LeadMax never deletes anything on your account: not when a deploy fails, not when you delete the project, not when you close your LeadMax account. To remove an app for good:
- Workers & Pages → the Worker named after the slug → Settings → delete.
- Storage & Databases → D1 →
leadmax-<slug>→ delete. Repeat for the KV namespace. - For an older project that already has an R2 bucket, empty and delete that bucket in Cloudflare only if you no longer need it. New projects do not create an R2 photo bucket.
- If you connected Filebase, manage its media separately. Keep any photos still used by a published website. When several projects share a bucket, remove only the files you no longer need.
What stays on the LeadMax side
Your project files, snapshots, chat history and photos saved by LeadMax stay with the project until you delete it. Published websites using those photos still request them from LeadMax. Copy the images to your own storage and update their URLs before deleting the project or moving away.
Custom domains
Deployed apps get a workers.dev URL. Custom domains on your own zones are planned (the optional workers-routes.write and zone.read scopes exist for that); until then you can add a route to the Worker yourself from the Cloudflare dashboard, which LeadMax leaves untouched on later deploys.