Deploy from the SaladCloud Portal.
Overview
Inference is powered by ComfyUI, exposed via ComfyUI API to facilitate horizontally scalable operation. Users can make an HTTP request to the provided endpoints and get back one or more outputs in base64 encoded form, via Webhook, or via S3. THIS RECIPE DOES NOT SERVE THE WEB UI. Several models are available, including:- Dreamshaper 8 - Fine-tuned from Stable Diffusion 1.5, great quality images, very low hardware requirements, supports many different art styles, and has a commercial-friendly license.
- FLUX.1-Dev - Foundational image generation model by Black Forest Labs, specifically this FP8 version provided by the Comfy Org.
- FLUX.1-Schnell - A faster, more efficient version of FLUX.1-Dev, specifically this FP8 version provided by the Comfy Org.
- Stable Diffusion XL - a foundational image generation model by Stability AI. It includes the base and refiner model.
- Stable Diffusion 3.5 Medium - a foundational image generation model by Stability AI.
Example request
Submit API-formatted ComfyUI prompts to the/prompt
endpoint, and receive base64-encoded images in response.
prompt.json
How To Use This Recipe
Authentication
When deploying this recipe, you can optionally enable authentication in the container gateway. If you enable authentication, all requests to your API will need to include your SaladCloud API key in the headerSalad-Api-Key
. See
the documentation for more information about authentication.
Replica Count
The recipe is configured for 3 replicas by default, and we recommend using at least 3 for testing, and at least 5 for production workloads. SaladCloud’s distributed GPU cloud is powered by idle gaming PCs around the world, in private residences, gaming cafes, and esports arenas. A consequence of this unique infrastructure is that all nodes must be considered interruptible without warning. If a 👨🍳 Chef (a compute host) decides they want to use their GPU to play a video game, or their dog trips on the power cord, or their Wi-Fi goes out, the instance of your workload running on that node will be interrupted, and a new instance will be allocated to a different node. This means you may want to slightly over-provision the capacity you expect to need in order to have adequate coverage during node reallocations. Don’t worry, we only charge for instances that are actually running.Logging
SaladCloud offers a simple built-in method to view logs from the portal, to facilitate testing and development. For production workloads, we highly recommend connecting an external logging source, such as Axiom. This can be done during container group creation.Deploy It And Wait
When you deploy the recipe, SaladCloud will find the desired number of qualified nodes, and begin the process of downloading the container image to the host machine. Depending on the model you choose, the image can be anywhere from 6GB for Dreamshaper 8, up to 16GB for the Flux models, and it may take up to tens of minutes to download to some machines, depending on the network conditions of that particular node. Remember, these are residential PCs with residential internet connections, and performance will vary across different nodes. Eventually, you will see instances enter the running state, and show a green checkmark in the “Ready” column, indicating the workload is passing its readiness probe. Once at least 1 instance is running, the container group will be considered running, but for production you will want to wait until an adequate number of nodes have become ready before moving traffic over.