Required stack
- Custom-node names or repository links.
- Model names, roles and download sources.
- Known ComfyUI, node or model revisions where available.
Technical qualification
ComfyUI workflow compatibility review.
Start with the nodes, models and production result your product needs. Comfy Rail maps that stack to the current runtimes or prepares a tailored, maintained runtime image for deployment in your RunPod account.
Starting point
Start with the stack your product needs.
Production context
- The intended inputs, outputs and required image dimensions.
- Expected request volume and startup behaviour.
- Data-handling or deployment-location constraints.
Keep provider credentials, customer media, production prompts and private model files out of the first email.
What gets checked
Trace the complete dependency path.
Nodes and packages
Required node classes are mapped to repositories, pinned revisions and package dependencies for a reproducible build.
Models and files
Model roles, download sources and runtime placement are mapped to the current inventory or the tailored image.
Licence and provenance
Available licence terms, source records and required notices are inventoried for the agreed stack.
Runtime and API fit
VRAM needs, input validation, output handling and storage assumptions shape the runtime and GPU profile.
Review outcome
Move from stack list to maintained runtime.
Current runtime match
Requirements already covered by the pinned inventory are mapped to the appropriate maintained profile.
Tailored runtime image
Additional agreed custom models, custom nodes and dependencies are packaged into a versioned Docker runtime image for the workflow stack.
Deployment path
The selected image, GPU profile and endpoint configuration are prepared for deployment in your RunPod account.
Maintained delivery
The agreed stack is carried forward through versioned releases, documented changes and runtime verification.
Workflow review