ComfyUI on RunPod

Production readiness checklist.

A workflow that runs locally is a starting point, not yet a production endpoint. Use this checklist to make its dependencies, inputs, outputs and release behaviour explicit before it serves an application.

01 · Contract

Define what the endpoint accepts and returns.

Workflow contract

  • Export an API-compatible workflow without credentials or local file paths.
  • Name required inputs, defaults, validation limits and outputs.
  • Define output formats, size limits and failure responses.

Application contract

  • Call the endpoint from a trusted backend, not a public client with a provider key.
  • Set timeouts, retries and idempotency behaviour intentionally.
  • Document how jobs and generated media move through the application.

02 · Reproducibility

Pin every moving runtime dependency.

Runtime inventory

Record the ComfyUI revision, custom-node commits, package versions, model files and hashes used by the candidate. Avoid mutable tags and floating package ranges.

Provenance review

Check model, node and code licences against the intended use. Keep source links and required notices with the candidate. This is technical inventory, not legal advice.

03 · Runtime evidence

Test the real serverless path.

Functional checks

  • Run known reference inputs and compare required output properties.
  • Test missing, malformed and oversized inputs.
  • Verify cold and warm starts on each supported GPU profile.

Operational checks

  • Observe VRAM use, execution time, queue behaviour and timeout handling.
  • Test parallel workers at an agreed request pattern.
  • Confirm logs do not expose prompts, credentials or customer media.

04 · Release

Make the candidate reversible.

Release record

Attach an immutable image digest, supported GPU profiles, reference-test results, known issues and documented changes to the candidate.

Rollback path

Keep the previous verified image available and document the endpoint change needed to restore it. A successful SEO publication is not commercial runtime clearance.

Bring your model and custom-node requirements. Keep secrets out of the first email.

Request a Demo