Build policy
Pin the ComfyUI release, custom nodes, models, and dependencies that belong in an approved build.
MANAGED BUILDS
Govern the models, custom nodes, and dependencies your team runs. Create a managed distribution of ComfyUI and deploy the same build on local infrastructure or through the Developer Platform.
One approved ComfyUI environment, everywhere your team runs it.
Define the ComfyUI release, custom nodes, models, and dependencies your team is approved to run. Ship the same versioned build wherever the work happens.
- Private custom nodes and models
- Use supported provider keys and existing contracts
- Assign approved builds through company identity
MANAGED BUILDS
Define your build
COMFYUI RELEASE
PYTHON · PYTORCH · CUDA
CUSTOM NODES
MODELS
v0.34.2 · py3.12 · torch 2.12.1
4 nodes · 3 models · pinned
Stop rebuilding the operating layer around ComfyUI.
01
Environment packaging
Replace one-off install scripts, dependency matrices, and machine-specific fixes with one versioned build.
02
Admin and upkeep
ComfyUI’s ecosystem spans 5,000+ extensions and 60,000+ community nodes. Pin and approve the nodes included in each build.
03
Onboarding and rollout
Assign known-good builds through company identity, onboard new teammates, and move the fleet together when a release is ready.
From one working setup to an approved fleet.
1. Define the build
Start from a known-good environment or import a snapshot of a setup you already run.
2. Build it once
Pin the ComfyUI release, Python and CUDA versions, custom nodes, models, and dependencies.
3. Roll out to the fleet
Assign the build through Comfy Desktop or your GPU servers. Deploy endpoints through the Developer Platform.
4. Update deliberately
Cut a new version when you decide. Move the team together without changing work already in flight.
Govern the build, models, people, and usage.
Model policy and BYOK
Choose the partner, open, and private models teams can use. Bring supported provider keys and existing contracts.
People and access
Use company identity and SSO to assign approved environments to the teams that need them.
Usage visibility and audit requirements
Track usage by model and partner on the Developer Platform. Scope authentication, build-assignment, release, retention, and export requirements during enterprise security review.
The graph stays flexible. The environment around it becomes an approved, reviewable operating model for the organization.
Ready for your security review.
Workflows stay local
For local deployments, your Comfy Workflows and outputs stay where they run. Comfy does not train on customer data.
Private models and nodes
Include internal node packs and fine-tuned models inside a team-controlled build.
Identity and BYOK
Gate build assignment through company identity and use supported provider keys with existing contracts.
Audit requirements
Define the model, partner, authentication, release, retention, and export events your organization needs.
DPA and enterprise agreement available. US processing on Google Cloud. 99.5% workflow-execution uptime SLA. SOC 2 Type II audit in progress.
Built with studios in the room.
For teams that need ComfyUI to move between people, productions, and partners without changing underneath them.
Game studios
Keep art, UA, and marketing teams on one pinned toolchain while each group works in the Comfy Workflows built for its job.
VFX and animation
Lock the environment per show, keep private nodes and models inside the build, and run IP-sensitive work on infrastructure you control.
Studios you onboard
Give a new studio or client an approved build aligned to its stack, then release updates deliberately instead of repeating setup by hand.
DEVELOPER PLATFORM
Run approved Comfy Workflows as endpoints with dedicated GPU capacity, priority queueing, and enterprise SLA terms through the Developer Platform.
SEE THE PLATFORMFORWARD DEPLOYED CREATIVES
Builders, not advisors. Forward Deployed Creatives build production Comfy Workflows inside approved environments, alongside the teams that will own and extend them.
VIEW THE OFFERINGManaged Builds, answered.
A Managed Build is an approved, reproducible ComfyUI environment. It pins the ComfyUI version, custom nodes, models, and dependencies your team needs so the same setup can be assigned and updated across machines.
Managed Builds run on your workstations, studio GPU servers, or customer cloud infrastructure. Your Comfy Workflows stay on the machines where they run.
Yes. Teams can include private fine-tuned models, govern which models and partner providers are available in a build, and use supported provider keys with their existing contracts.
Administrators choose which custom nodes belong in each build, then pin them with the rest of the environment for controlled rollout.
Company identity and SSO can gate access to approved builds. Teams receive the environments assigned to them instead of configuring every machine independently.
Track usage by model and partner on the Developer Platform. Authentication, build-assignment, release, retention, and export requirements are scoped explicitly during enterprise security review.
Request a demo and bring one known-good environment. Comfy engineers will map the current setup, deployment targets, governance requirements, onboarding plan, and path to the first approved build.
Your approved ComfyUI setup, ready for the whole team.
Start with one known-good environment. Comfy engineers will map deployment targets, governance requirements, onboarding, and the path to your first approved build.