SpicyAPIspicyAPI

NSFW POLICY GUIDES · COMFY ORG (OPEN SOURCE)

ComfyUI NSFW workflows vs an API: what self-hosting really costs

ComfyUI is the node-based front end most uncensored image and video workflows are built in. There is no NSFW policy to read: it is open source and runs wherever you install it. The question developers actually have is whether to build a product on it.

Written for developers building a product. Policy text read on 21 September 2026. Re-checked quarterly.

What the ComfyUI policy says

Source: ComfyUI repository (GPL-3.0, no content policy).

“ComfyUI is open source. Content rules come from the models, LoRAs and hosting you choose, not from ComfyUI itself.”

What that means if you are building on it

  • For personal use it is the best uncensored toolkit there is: Wan 2.2, FLUX and their adult LoRAs all run in it.
  • For a product it becomes an infrastructure project: a GPU per concurrent user, queueing, storage and a CDN, workflow versioning, LoRA updates that break outputs, and moderation you must build yourself to stay on the right side of the law and your payment processor.
  • Hosted ComfyUI services solve the GPU part and then re-apply moderation, which puts you back where you started.

The workarounds, and why they break

  • Rented GPUs with your own ComfyUI: full control, $1,500 to $3,500 a month per always-on worker before anyone maintains it.
  • ComfyUI-as-a-service platforms: less ops, filters back on.
  • Exporting the workflow as an API with the built-in server works for one user, not a queue of them.

The API alternative for fictional adult content

SpicyAPI is a REST API built for adult products: uncensored text to image, image editing, image to video, text to video and chat behind one key, pay per generation from a prepaid balance, OpenAI SDK compatible. Every prompt is moderated before billing and every request is steered to depict adults only; real people without consent and minors are blocked, and image inputs must be images your account generated.

SpicyAPI runs the same class of models (Wan 2.x for video, tuned image models for stills) behind a REST API with moderation, provenance rules, webhooks and per-generation billing, so the workflow you would have built is a single call.

curl https://api.spicyapi.com/v1/videos/generations \
  -H "Authorization: Bearer $SPICYAPI_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model": "spicy-motion-2", "prompt": "slow build, steady rhythm", "image_url": "<a URL from /v1/images/generations>", "resolution": "720P", "duration": 5}'

Full reference in the API docs, prices on the pricing page, runnable curl, Python and Node examples in the porn-api repo. See also the porn AI API overview.

Get an API key (18+)See example output

FAQ

Does ComfyUI allow NSFW?

ComfyUI itself has no content policy; it is open-source software you run yourself. What it generates depends on the models and LoRAs you load and where you host it.

Is there an API that replaces an uncensored ComfyUI workflow?

SpicyAPI serves adult-tuned image and Wan-family video models over REST with sandbox keys, webhooks and per-generation pricing, so you skip the GPU and pipeline work.

Does SpicyAPI allow real people or deepfakes?

No. SpicyAPI generates fictional adults only. Real people without consent, minors in any form and image inputs you did not generate yourself are blocked before billing, the same lines the mainstream platforms draw. What changes is that fictional adult content is allowed instead of refused.

Can I test it without spending money?

Yes. Create a key with Sandbox ticked and every endpoint answers with sample output at no cost, so you can build the whole integration first. Real generations are billed per call from a prepaid balance with a $50 minimum top-up by card or crypto.

Other platforms