--- title: "ComfyUI Managed Builds | Govern ComfyUI across your fleet" description: "Create approved, reproducible ComfyUI environments and deploy them across workstations, studios, and customer infrastructure." canonical: https://comfy.org/enterprise/managed-builds/ lang: en index: https://comfy.org/llms.txt --- # MANAGED BUILDS BETA Govern the models, custom nodes, and dependencies your team runs. Create a managed distribution of ComfyUI and deploy the same build anywhere, local or serverless cloud. [REQUEST DEMO](https://comfy.org/contact/) MANAGED BUILDS ## 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 COMFYUI RELEASE more options PYTHON · PYTORCH · CUDA more options CUSTOM NODES more options MODELS more options v0.3.41 · py3.12 · torch 2.6 4 nodes · 3 models · pinned [REQUEST DEMO](https://comfy.org/contact/) ## One ComfyUI build for the whole team **Environment packaging** Replace one-off install scripts, dependency matrices, and machine-specific fixes with one versioned build. **Node governance** ComfyUI’s ecosystem spans 5,000+ extensions and 60,000+ community nodes. Pin and approve the nodes included in each build. **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 ### Define the build Start from a known-good environment or import a snapshot of a setup you already run. ### Build it once Pin the ComfyUI release, Python and CUDA versions, custom nodes, models, and dependencies. ### Update deliberately Cut a new version when you decide. Move the team together without changing work already in flight. ### Roll out to the fleet Assign the build through Comfy Desktop or your GPU servers. Deploy endpoints through the Developer Platform. ## Govern the build, models, people, and usage. **Build policy** Pin the ComfyUI release, custom nodes, models, and dependencies that belong in an approved build. **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. ## Builds vs. Managed Builds Builds is self-serve for packaging and testing your own environment. Managed Builds adds team sharing and enterprise governance. | FEATURE | BUILDS | MANAGED BUILDS | | --- | --- | --- | | Custom nodes packaging | Included | Included | | Team sharing | Not included | Enterprise only | | Governance | Not included | Enterprise only | | Python dependency auto-resolution | Included | Included | [EXPLORE BUILDS](https://comfy.org/platform/builder) ## Managed 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. ## Built with studios in the room [EXPLORE WORKFLOWS](https://comfy.org/workflows/) ## DEVELOPER PLATFORM BETA Scale your custom nodes in your Comfy workflows in custom environments through Comfy API. [Get Started](https://platform.comfy.org/) [Read the docs](https://docs.comfy.org/development/overview) ## Forward 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 OFFERING](https://comfy.org/forward-deployed-creatives/)