Media runtime
Pulsar with ComfyUI
Connect ComfyUI for governed image creation, editing, video workflows, model assets, queue state, and retained outputs.
Key considerations
Image workflows
Create, edit, upscale, and retain outputs through one product surface.
Video workflows
Support approved text-to-video and image-to-video paths.
Operator control
Manage connectivity, model assets, queues, compatibility, and recovery.
Architecture at a glance
Media creation stays inside the workspace
Users create and inspect image or video work while Pulsar owns request validation, queue state, output records, and Library retention.
ComfyUI remains a separately operated runtime
The ComfyUI host may use its own GPU, models, custom nodes, and storage paths. Pulsar verifies reachability and exposes product-level controls without hiding the operational dependency.
Compatibility requires evidence
FLUX, SDXL fallback, IPAdapter, LoRA, sampler, upscaling, and video paths depend on the deployed model and node set. Public claims must match the current tested workflow rather than a generic ComfyUI capability.
Queue and recovery are product concerns
Long-running jobs require visible status, bounded retries, failure handling, and retained outputs. Operators can diagnose the runtime while users remain in a consistent media workflow.
Private deployment consultation
Review Pulsar against your environment.
Bring the infrastructure, security boundaries, model runners, and use cases. The Pulsar team will map the appropriate deployment path.