diff --git a/development/deploy/cloud-custom-builds.mdx b/development/deploy/cloud-custom-builds.mdx
new file mode 100644
index 0000000000..c1cf459b58
--- /dev/null
+++ b/development/deploy/cloud-custom-builds.mdx
@@ -0,0 +1,255 @@
+---
+title: "Adding Custom Builds to Comfy Cloud"
+sidebarTitle: "Custom Builds"
+description: "Run a Workflow with your own Custom Nodes on Comfy Cloud: create a Build, run its deployment from the editor, upload a LoRA, and delete the deployment."
+icon: "puzzle-piece"
+---
+
+A Build packages your Custom Nodes, private Custom Nodes, LoRAs and other models, and Python dependencies so your Workflows can run on Comfy Cloud. You start the Build from the Comfy Cloud editor, create and deploy it on the Developer Platform, and then run your Workflow on it in the editor.
+
+A deployment of your Build also gives you GPU workers that serve only your Workflows, even when Comfy Cloud already supports every Node in them.
+
+
+ To use your own LoRA or another model with Nodes that Comfy Cloud already supports, you don't need a Build. Upload the model to your **Model Library** instead. See [Add your own LoRA or model](#add-your-own-lora-or-model).
+
+
+### Prerequisites
+
+Before you create a Build, make sure you have these:
+
+- **A saved Workflow on Comfy Cloud**
+- **An active subscription or a Comfy Credits balance above zero**
+
+
+ A Build costs nothing to create or keep. A deployment costs GPU time while a GPU is on for it. It also costs storage for as long as the deployment exists, even while it's stopped or no GPU is on. The deploy dialog shows the estimated cost before you confirm. To stop paying, delete the deployment. See [Stop or delete your deployment](#stop-or-delete-your-deployment).
+
+
+## Create a Build from your Workflow
+
+If your Workflow uses Custom Nodes Comfy Cloud doesn't support, Comfy Cloud shows a dialog when you open it. The dialog lists the missing Custom Node packs (groups of Custom Nodes) and models, such as LoRAs. To run the Workflow, create a Build with them. When you pick your saved Workflow, the Developer Platform finds its Custom Nodes and models and selects them for you.
+
+
+
+ In the dialog, click **Create on Platform**. The Developer Platform opens in a new tab, on its **Deploy** page.
+
+ 
+
+ 
+
+
+ To create a Build without the dialog, click the cloud menu to the left of **Run**. By default, it's set to **Comfy Cloud**.
+
+ - If your workspace has no deployments yet, select **Create a custom deployment**, and then click **Create on Platform**.
+ - If it already has deployments, select **Manage deployments**.
+
+
+
+ On the **Deploy** page, click **New build**. If you have no Builds yet, click **Start from scratch** instead.
+
+
+ 1. Click **Pick from Comfy Cloud**.
+ 2. Select your Workflow, and then click **Add 1 workflow**.
+
+ You can also drag the Workflow's `.json` file, or a `.png` image made with it, onto the drop area.
+
+ 
+
+ The step succeeds when your Workflow's name appears under the drop area with a check mark, and the **Suggested defaults** list shows the Build's **Custom nodes**.
+
+
+ Click **Build with defaults…**. The **Choose build targets** dialog opens.
+
+ If **Build with defaults…** is unavailable, a line under the button says why. When it reads _Add the missing models and custom nodes on their steps first._, add what's missing:
+
+ 1. Click **Customise build**.
+ 2. Click **Next** until a step lists the missing Custom Nodes or models.
+ 3. On each one, click **Use suggestion** or **Upload**.
+
+
+
+To change what goes into the Build, click **Customise build** instead and go through the steps. Two steps decide what the Build holds:
+
+- **Which custom nodes does the build need?**: choose the Custom Nodes.
+- **Which models ship inside the build?**: choose which models the Build includes. A model the Build doesn't include downloads the first time a job uses it.
+
+### Publish the Build
+
+Publishing turns your Build into a numbered version, such as `v1`, that you can deploy now and later. Publishing is free.
+
+1. In the **Choose build targets** dialog, keep **Serverless build** selected. It's the target that runs on Comfy Cloud.
+2. Click **Publish**.
+
+Your Build's page opens with the new version. The **Serverless build** row shows the build's progress. Building usually takes 10 to 15 minutes, and you can leave the page and come back. When the build finishes, the **Serverless build** row shows a **Deploy** button.
+
+To come back to the version later:
+
+1. In the **Developer Platform sidebar**, click **Deploy**.
+2. In the **Builds** section, click your Build.
+3. Under **Versions**, click the latest version.
+
+
+
+ Some Custom Nodes fail to build. When that happens, the **Serverless build** row on your Build's page shows **Build failed**.
+
+ 1. Open **Logs** on the row to read what failed.
+ 2. Click **Edit build**, and change the Build, such as by removing the Custom Node that failed.
+ 3. Publish the Build again.
+
+ The row's **Debug with your agent** button opens a prompt that describes the failure. Copy it to a coding agent to repair the Build.
+
+
+
+### Deploy and run your Workflow
+
+A deployment is your Build running on Comfy Cloud GPUs. Deploy the Build, and then switch the Comfy Cloud editor to the deployment to run your Workflow.
+
+1. On the **Serverless build** row, click **Deploy**. The **Deploy v1 of** _your Build's name_ dialog opens.
+2. Select a GPU. Each GPU shows its VRAM (GPU memory) and its price per hour.
+3. If the dialog shows **Ready for the Cloud editor**, leave it selected. It's on by default.
+4. Leave the other settings at their defaults. With **Always-warm workers** at `0`, the deployment turns its GPUs off when no jobs come in. By default, **Keep worker up after a job** keeps a GPU on for 3 minutes after the last job, and that idle time is billed at the GPU rate.
+5. Check the **Estimated cost** panel. It shows the GPU time per hour and the model storage per month.
+6. Click **Create deployment**. The deployment's page opens. Wait until the status under the deployment's name reads **Ready**.
+7. In the Comfy Cloud editor, click the cloud menu to the left of **Run**. Under **Run on**, select your deployment. The editor reloads, and your tabs stay open.
+
+ 
+
+8. Open your Workflow, and then click **Run**. Your first job can wait while the deployment starts a GPU.
+
+This browser keeps running your Workflows on the deployment until you select another one. To switch back, select **Comfy Cloud** in the same menu. If a Workflow has unsaved changes, the **Save your workflows before switching?** dialog opens. Click **Save and switch**, or **Switch without saving**.
+
+## Add your own LoRA or model
+
+The **Model Library** holds the models your workspace uploads. A model you upload runs on Comfy Cloud and on your deployments.
+
+Before you upload a model, make sure you meet these requirements:
+
+- **An active Pro, Creator, Team, or Enterprise plan**: your workspace needs one to upload a model.
+- **A `.safetensors` file of 2 GB or less**: put larger base models, such as SDXL or Flux, in the Build.
+
+
+ Some deployments created before library models were available can't load them. To use library models, create a new deployment. On an older deployment, a job can fail with `Library model "" is unavailable on this deployment. Retry the job. If it still fails, contact support with the job ID.`
+
+
+### Upload the model
+
+You can upload in the Comfy Cloud editor or on the Developer Platform. Pick the tab for the place you're working in.
+
+
+
+ 1. In the cloud menu to the left of **Run**, make sure **Comfy Cloud** is selected under **Run on**. On a deployment, the **Model Library** has no **Import** button.
+ 2. In the **Left sidebar**, click **Model Library**, and then click **Import**.
+ 3. Click **Choose a file**, or drag a `.safetensors` file into the dialog.
+ 4. Under **What type of model is this?**, keep **LoRA** for a LoRA, or select the type that matches the file.
+ 5. Click **Upload**. When the dialog says _Model successfully imported._, click **Finish**.
+
+ 
+
+ To import a model from a Civitai or Hugging Face link instead:
+
+ 1. In the **Import** dialog, paste the model's link in **Paste link here**.
+ 2. Click **Continue**.
+ 3. Under **What type of model is this?**, select the model type.
+ 4. Click **Import**.
+
+ A link import in another format, such as `.ckpt`, imports into the **Model Library** but doesn't run on a deployment.
+
+
+ 1. On the **Which models ship inside the build?** step of a Build, click **Upload Models**.
+ 2. Select **Workspace library**.
+ 3. Drag a `.safetensors` file onto the drop area, or click the area to browse.
+ 4. Under **Model type**, keep **LoRA** for a LoRA, or select the type that matches the file.
+ 5. Click **Upload**.
+
+ 
+
+
+
+### Use the model in your Workflow
+
+Once the model is uploaded, you can use it on Comfy Cloud or on your deployment.
+
+1. In the cloud menu to the left of **Run**, select where to run: **Comfy Cloud**, or your deployment.
+2. Add a `Load LoRA (Model and CLIP)` Node, or open a Workflow that has one.
+3. In the Node's `lora_name` list, select your file.
+4. Click **Run**.
+
+
+
+
+ On a deployment, the first run downloads the model, and the job's row in the queue shows `Downloading `. Later jobs on the same running GPU skip the download. A GPU the deployment starts later downloads the model again. To skip the download, add the model to the Build.
+
+
+Follow these rules so a job finds your model:
+
+- **Pick the matching type.** A loader Node lists only models of its type. A `Load LoRA (Model and CLIP)` Node lists models uploaded as LoRA.
+- **Use a new file name.** If your Build already has a model with the same name, a job on your deployment uses the Build's file, not your upload.
+- **Match the base model.** A LoRA must match the base model your Workflow loads.
+- **Use a loader Node that Comfy Cloud has.** If the loader Node comes from a Custom Node that Comfy Cloud doesn't have, add the model to the Build.
+
+### Change or delete a library model
+
+When a deployment is selected under **Run on**, the **Model Library** lists only the Build's models. To change or delete a model you uploaded, [switch back to Comfy Cloud](#deploy-and-run-your-workflow) first, and then in the **Left sidebar**, click **Model Library**.
+
+To change the model type:
+
+1. Hover over the model's card, and then click **Model Info**.
+2. Select a new **Model Type**.
+
+
+ Deleting a model removes it from the **Model Library** permanently. A job that still uses the file fails with a `Value not in list` error on the loader Node.
+
+
+To delete the model:
+
+1. Hover over the model's card, click **More**, and then click **Delete**.
+2. In **Delete this model?**, click **Delete**.
+
+## Stop or delete your deployment
+
+A deployment costs storage until you delete it, even while it's stopped. Stop a deployment to keep it for later without running jobs. Delete it to stop paying for it.
+
+To open the deployment's page:
+
+1. In the **Developer Platform sidebar**, click **Deploy**.
+2. In the **Deployments** section, click the deployment's name.
+
+
+
+To stop the deployment:
+
+1. Click **Stop**.
+2. In the **Stop deployment** dialog, click **Stop**.
+
+The status reads **Stopping**, and then **Stopped**.
+
+To run the deployment again:
+
+- Click **Start**.
+
+
+ Deleting removes the deployment and its history permanently. Your Build and its versions stay, so you can deploy again later.
+
+
+To delete the deployment:
+
+1. On a stopped deployment, click **Delete**. On a running deployment, open the **More actions** menu, and then select **Delete**.
+2. In the **Delete deployment** dialog, click **Delete**.
+
+The next time you open the editor in this browser, the editor runs your Workflows on Comfy Cloud.
+
+## Next steps
+
+
+
+ Upload a model from a terminal and pick it per request with `lora_name`.
+
+
+ Call your deployment from your own code as an autoscaling endpoint.
+
+
+ See how Comfy Cloud credits and concurrent job limits work.
+
+
+ Export a Workflow in the format that API requests send.
+
+
diff --git a/development/deploy/overview.mdx b/development/deploy/overview.mdx
index f0fb6bfd5b..fbda0e45a9 100644
--- a/development/deploy/overview.mdx
+++ b/development/deploy/overview.mdx
@@ -7,10 +7,13 @@ icon: "map"
You can run your ComfyUI Workflows on Comfy Cloud, on your own Comfy API deployment, or on a server you manage. Comfy Cloud and Comfy API run on Comfy GPUs, so they don't need a GPU on your computer. Pick the option that fits your Workflow, and start from its card.
-
+
Run Workflows whose Custom Nodes and models are already on Comfy Cloud, with no build or deployment.
+
+ Run Workflows that need your own Custom Nodes and models in the Comfy Cloud editor, with a Build you create in your browser.
+
Package Custom Nodes, models, and Python dependencies into a build, and run it as an autoscaling endpoint.
@@ -19,7 +22,7 @@ You can run your ComfyUI Workflows on Comfy Cloud, on your own Comfy API deploym
-To call any of the three from your own code, send the Workflow in [API format](/development/api-development/workflow-api-format).
+To call any of these from your own code, send the Workflow in [API format](/development/api-development/workflow-api-format).
## Deploy from the ComfyUI app
@@ -49,86 +52,7 @@ On the Developer Platform, you create a build from the Workflow, publish a versi
## Run a deployment from the Cloud editor
-Your deployment can run Workflows in ComfyUI on Comfy Cloud, with the Custom Nodes and models in its build.
-
-### Create a deployment from Comfy Cloud
-
-On Comfy Cloud, the **Workflow actions** menu has no **Deploy to Comfy API** entry. Start from the menu next to **Run** instead:
-
-1. Click the menu next to **Run**.
-2. Select **Create a custom deployment**, and then click **Create on Platform**. Your builds on the Developer Platform open in a new tab.
-
-
-
-When your workspace already has deployments, the menu shows **Manage deployments** instead. It opens the same builds page on the Developer Platform.
-
-When you open a Workflow that uses Custom Nodes Comfy Cloud doesn't have, the **Run this workflow on a custom deployment** dialog lists what's missing. Click **Create on Platform** to start a build for it.
-
-
-
-### Open your deployment in the Cloud editor
-
-1. In the deploy dialog, leave **Ready for the Cloud editor** selected if the dialog shows it. The option is on by default. If you clear **Ready for the Cloud editor**, opening the deployment in the editor later takes a minute.
-2. On the deployment's page, wait for the status under its name to read **Ready**. **Open in ComfyUI** stays disabled until then.
-3. Click **Open in ComfyUI**. ComfyUI on Comfy Cloud opens in a new tab and reloads onto your deployment.
-
-
-
-To check where your Workflows run:
-
-1. Click the menu next to **Run**.
-2. Find the check mark next to the deployment your Workflows run on.
-3. Click **Run** to run the Workflow on it.
-
-
-
-- The menu lists every deployment in your workspace. Select a **Ready** deployment to switch to it.
-- Switching reloads the editor. By default, your tabs stay open.
-- This browser keeps running your Workflows on the selected deployment until you select another one.
-
-### Switch back to Comfy Cloud
-
-1. Click the menu next to **Run**.
-2. Select **Comfy Cloud**.
-
-The editor reloads. If a Workflow has unsaved changes, a **Save your workflows before switching?** dialog opens. Click **Save and switch**, or **Switch without saving**.
-
-## Stop or delete a deployment
-
-Stop a deployment to stop its jobs, or delete it to remove it and end its storage billing. Both actions are on the deployment's page on the Developer Platform.
-
-
- A stopped deployment runs no jobs, but its storage still bills. Delete the deployment to end storage billing.
-
-
-To open the deployment's page:
-
-1. In the Developer Platform sidebar, click **Deploy**.
-2. In the **Deployments** section, click the deployment's name.
-
-
-
-To stop the deployment:
-
-1. Click **Stop**.
-2. In the **Stop deployment** dialog, click **Stop**.
-
-The status reads **Stopping**, and then **Stopped**.
-
-To run the deployment again:
-
-- Click **Start**.
-
-
- Deleting removes the deployment and its history permanently. The build stays.
-
-
-To delete the deployment:
-
-1. On a stopped deployment, click **Delete**. On a running deployment, open the **More actions** menu, and then select **Delete**.
-2. In the **Delete deployment** dialog, click **Delete**.
-
-The next time a browser that ran the Cloud editor on the deployment loads ComfyUI, ComfyUI runs on Comfy Cloud instead of the deleted deployment.
+To create a deployment from the Comfy Cloud editor, run your Workflows on it, and stop or delete it, see [Adding Custom Builds to Comfy Cloud](/development/deploy/cloud-custom-builds).
## Run Workflows from your application
diff --git a/development/serverless/library-models.mdx b/development/serverless/library-models.mdx
deleted file mode 100644
index b781db5bb7..0000000000
--- a/development/serverless/library-models.mdx
+++ /dev/null
@@ -1,163 +0,0 @@
----
-title: "Workspace Library Models on a Comfy API Deployment"
-sidebarTitle: "Library Models"
-description: "Upload a LoRA or other .safetensors model to your workspace library and run it on a Comfy API deployment with no new Build, Release, or redeploy."
-icon: "folder-open"
----
-
-Comfy API runs models from your workspace library, even when the deployment's Release doesn't include them. Upload a LoRA or another `.safetensors` model to the library, and run it on your deployment without a new Build, Release, or redeploy.
-
-Use the workspace library to try a LoRA you trained on your deployment, or to pick a different LoRA for each API request by changing one file name in the Workflow.
-
-## Before you start
-
-Before you upload a model to the workspace library, make sure you meet these requirements:
-
-- **Plan**: Your workspace needs an active Pro, Creator, Team, or Enterprise plan.
-- **Model file**: The file must be a `.safetensors` file of 2 GB or less. Larger base models, such as SDXL or Flux, still go in the Build.
-- **An active deployment**: The deployment must be in the same workspace as the library.
-
-
- Some deployments created before workspace library models were available can't load them. To use workspace library models, create a new deployment. On an older deployment, a job can fail with `Library model "" is unavailable on this deployment. Retry the job. If it still fails, contact support with the job ID.`
-
-
-## Upload a model to the workspace library
-
-You can upload a model with any of three tools:
-
-- **Cloud editor**: upload a file, or import from a Civitai or Hugging Face link.
-- **comfy-cli**: upload from a terminal or a script.
-- **Developer Platform**: upload from a Build's models step.
-
-Pick the tab for the tool you use.
-
-
-
- 1. In the deployment menu to the left of **Run**, make sure **Comfy Cloud** is selected under **Run on**.
- 2. In the **Left sidebar**, click **Model Library**, then click **Import**.
- 3. Click **Choose a file**, or drag a `.safetensors` file into the dialog.
- 4. Under **What type of model is this?**, keep **LoRA** for a LoRA, or select the type that matches the file.
- 5. Click **Upload**. When the upload finishes, click **Finish**.
-
- 
-
- To import a model from a Civitai or Hugging Face link instead:
-
- 1. In the **Import** dialog, paste the model's link in **Paste link here**.
- 2. Click **Continue**.
- 3. Under **What type of model is this?**, select the model type.
- 4. Click **Import**.
-
- Only `.safetensors` files run on a deployment. A link import in another format, such as `.ckpt`, imports into the library but doesn't run on a deployment.
-
-
- Upload the file and set its model type with `--type`:
-
- ```bash
- comfy assets library upload my_style.safetensors --type loras
- ```
-
- Check that the file is in the library:
-
- ```bash
- comfy assets library ls --tags models,loras
- ```
-
-
- 1. On the Developer Platform, open the models step of a Build and click **Upload Models**.
- 2. Select **Workspace library**.
- 3. Drag a `.safetensors` file onto the drop area, or click the area to browse.
- 4. Under **Model type**, keep **LoRA** for a LoRA, or select the type that matches the file.
- 5. Click **Upload**.
-
- 
-
-
-
-Every member of the workspace can use the model once it is in the library. The library takes any model type, not only LoRAs. Pick the type that matches the folder your loader Node reads, such as `loras` for a LoRA or `vae` for a VAE.
-
-## Run the model on your deployment
-
-Once the model is in the library, you can run it on your deployment from the Cloud editor or through the API. Pick the tab for how you send jobs.
-
-
-
- 1. Click the deployment menu to the left of **Run**. Under **Run on**, select your deployment. The editor reloads, and your tabs stay open.
- 2. Add a `Load LoRA (Model and CLIP)` Node, or open a Workflow that has one.
- 3. In the Node's `lora_name` list, select your file. The list shows your library models next to the Release's models.
- 4. Click **Run**.
-
- On the first run, the job's row in the queue shows `Downloading my_style.safetensors` while the worker downloads the file. When the job downloads several models, the row shows `Downloading ( of )`.
-
- 
-
-
- In the [API-format Workflow](/development/api-development/workflow-api-format), set the `lora_name` input of the `LoraLoader` Node to the library file name, including `.safetensors`:
-
- ```json
- "10": {
- "class_type": "LoraLoader",
- "inputs": {
- "lora_name": "my_style.safetensors",
- "strength_model": 1.0,
- "strength_clip": 1.0,
- "model": ["4", 0],
- "clip": ["4", 1]
- }
- }
- ```
-
- Send the Workflow with `comfy deploy run`, the [Comfy SDKs](/development/api-development/sdks), or the [Comfy API v2](/api-reference/v2/overview):
-
- ```bash
- comfy deploy run --deployment --workflow workflow_api.json
- ```
-
- To use a different LoRA, change `lora_name` to another file name from your library in the next request. You don't need a new Build, Release, or redeploy.
-
-
-
-
- The first job on a worker that uses a library model takes longer, because the worker downloads the model first. Later jobs on the same worker use the cached copy. A new worker downloads the model again, and so does a worker that removed the model from its cache to make room for other models. To skip the download, add the model to the Build.
-
-
-## Follow the limits and naming rules
-
-Besides the file size and format limits in [Before you start](#before-you-start), these limits apply:
-
-| Limit | Value |
-| --- | --- |
-| Workspace storage | 1 TB of models per workspace, including link imports |
-| Library model names per Workflow | 100 |
-
-A loader that names a 101st library model fails as if the file were not in the library.
-
-Follow these rules so a job finds the right file:
-
-- **Use the folder the loader reads.** A loader only finds library files of its own model type. A `Load LoRA` Node finds files uploaded as `loras`, not as `checkpoints`.
-- **Use the bare file name.** Set the loader input to the file name only, such as `my_style.safetensors`, with no folder in front of it.
-- **Don't reuse a Release model's name.** If the Release already has a file with that name, the worker uses the Release's file, not your library file.
-- **Keep names unique across folders.** If the library has the same file name in two folders that one loader reads, a job sent through the API loads neither file.
-- **Expect the newest file to win.** If the library has two files with the same name in one folder, jobs use the one added last.
-- **Match the base model.** A LoRA must match the base model the Workflow loads.
-- **Use a loader the deployment has.** The loader Node must be available on the deployment. Library models load only through loader Nodes that Comfy Cloud has. If your loader comes from a Custom Node that Comfy Cloud doesn't have, add its models to the Build.
-
-## Change or delete a library model
-
-When a deployment is selected under **Run on**, the **Model Library** lists only the Release's models. To change or delete a library model, switch back to Comfy Cloud first:
-
-1. Click the deployment menu to the left of **Run**. Under **Run on**, select **Comfy Cloud**.
-2. In the **Left sidebar**, click **Model Library**.
-
-To change the model type:
-
-- Hover over the model's card, click **Model Info**, and select a new **Model Type**.
-
-
- Deleting a model removes it from the workspace library for every member. A job or API request that still names the file fails with a `Value not in list` error on the loader input.
-
-
-To delete the model:
-
-1. Hover over the model's card, click **More**, then click **Delete**.
-2. In **Delete this model?**, click **Delete**.
diff --git a/development/serverless/overview.mdx b/development/serverless/overview.mdx
index 49c5e5351d..cb04a903aa 100644
--- a/development/serverless/overview.mdx
+++ b/development/serverless/overview.mdx
@@ -18,7 +18,7 @@ Comfy API lets your application run ComfyUI workflows through a managed endpoint
Workflows supported by [Comfy Cloud](/development/deploy/cloud) can run there without creating a Build or deployment.
-To add a model to a deployment without a new Build, upload it to your workspace library. See [Workspace library models](/development/serverless/library-models).
+To add a model to a deployment without a new Build, upload it to your workspace library. See [Add your own LoRA or model](/development/deploy/cloud-custom-builds#add-your-own-lora-or-model).
Start with an agent or choose another way to provide your environment or workflow.
@@ -77,6 +77,43 @@ The `--min` and `--max` options set the worker bounds. Run `comfy deploy status
You can also call the endpoint with the [Comfy SDKs](/development/api-development/sdks). Set `COMFY_BASE_URL` to the deployment URL and provide an API key. See [Choosing a base URL](/development/api-development/sdks#choosing-a-base-url).
+## Use workspace library models in API requests
+
+A deployment runs `.safetensors` models from your workspace library, even when its release doesn't include them. To upload a model in the Comfy Cloud editor or on the Developer Platform, see [Add your own LoRA or model](/development/deploy/cloud-custom-builds#add-your-own-lora-or-model).
+
+To upload from a terminal, set the model type with `--type`, and then check that the file is in the library:
+
+```bash
+comfy assets library upload my_style.safetensors --type loras
+comfy assets library ls --tags models,loras
+```
+
+In the [API-format Workflow](/development/api-development/workflow-api-format), set the loader input to the library file name, including `.safetensors`:
+
+```json
+"10": {
+ "class_type": "LoraLoader",
+ "inputs": {
+ "lora_name": "my_style.safetensors",
+ "strength_model": 1.0,
+ "strength_clip": 1.0,
+ "model": ["4", 0],
+ "clip": ["4", 1]
+ }
+}
+```
+
+Send the Workflow with `comfy deploy run`, the [Comfy SDKs](/development/api-development/sdks), or the [Comfy API v2](/api-reference/v2/overview):
+
+```bash
+comfy deploy run --deployment --workflow workflow_api.json
+```
+
+To use a different LoRA, change `lora_name` to another library file name in the next request. You don't need a new Build, release, or redeploy.
+
+- A Workflow can name up to 100 library models. A loader that names a 101st library model fails as if the file were not in the library.
+- Keep file names unique across the folders one loader reads. If the library has the same file name in two of them, a job sent through the API loads neither file.
+
## Operate a deployment
```bash
@@ -121,7 +158,7 @@ comfy deploy events --deployment dep_123456
Storage billing starts with a deployment:
- - When you deploy a release, its models are staged onto network storage shared by the deployment's workers. The storage is read-only after deployment and billed per GB-month for as long as any deployment of the Build exists in that region, including while a deployment is paused with `comfy deploy stop`. Models a job uses from your [workspace library](/development/serverless/library-models) are not staged there. The worker downloads them for the job.
+ - When you deploy a release, its models are staged onto network storage shared by the deployment's workers. The storage is read-only after deployment and billed per GB-month for as long as any deployment of the Build exists in that region, including while a deployment is paused with `comfy deploy stop`. Models a job uses from your [workspace library](/development/deploy/cloud-custom-builds#add-your-own-lora-or-model) are not staged there. The worker downloads them for the job.
- Each worker also gets a fixed 50 GB container disk. It is ephemeral and is only billed while the worker is running, as part of the worker's compute cost.
- Deleting a deployment releases its compute. Staged network storage is cleaned up shortly after the last deployment using it in that region is deleted, and billing for it ends.
diff --git a/docs.json b/docs.json
index 3d75ad64bb..4181b62c7b 100644
--- a/docs.json
+++ b/docs.json
@@ -3963,7 +3963,8 @@
"group": "Comfy Cloud",
"pages": [
"development/deploy/cloud",
- "development/deploy/cloud-usage"
+ "development/deploy/cloud-usage",
+ "development/deploy/cloud-custom-builds"
]
},
{
@@ -20845,6 +20846,10 @@
}
},
"redirects": [
+ {
+ "source": "/development/serverless/library-models",
+ "destination": "/development/deploy/cloud-custom-builds#add-your-own-lora-or-model"
+ },
{
"source": "/custom-nodes/tips",
"destination": "/custom-nodes/overview"
diff --git a/images/development/deploy/missing-nodes.png b/images/development/deploy/missing-nodes.png
new file mode 100644
index 0000000000..74a68cef68
Binary files /dev/null and b/images/development/deploy/missing-nodes.png differ