Hybrid Manager (HM) extends Langflow with a deployment lifecycle that turns flows you've built in the editor into long-running, callable services. A flow moves through three stages:
- Publish a bundle: package one or more flows from a Langflow project into an immutable bundle in the HM Asset Library.
- Deploy a published flow: instantiate a published bundle as a managed workload in an HM project, with its own parameter values, resource limits, and endpoints.
- Access a deployed flow: invoke the flow over HTTP or MCP. Access is authenticated by the same HM machine-user access keys used elsewhere in HM.
Flows in the Langflow editor are private to the user who built them and run in a shared editor environment. Compared to that, a deployed flow has:
- A stable HTTP endpoint and an MCP server endpoint, both routed through the HM gateway.
- Its own parameter values, supplied at deploy time independently of whatever the builder used in the editor. Any parameter values that are secrets (passwords, API keys, or tokens the flow uses to reach databases, model APIs, or other downstream resources) are stored as Kubernetes secrets in the deployment's namespace.
- An independent lifecycle (deploy, update, undeploy) that doesn't require opening the editor.
- Versioning: each deployment is created from an immutable bundle version. Updating the bundle creates a new version. The deployment continues to run the version it was deployed from until you update it.
- Access control: a deployed flow can be made available globally or per-project, with access limited to a specific set of Hybrid Manager projects.
Concepts
| Term | Meaning |
|---|---|
| Published flow | A versioned bundle of one or more Langflow flows in the HM Asset Library. Visible at Asset Library > Published Flows (/asset-library/published-flows). Immutable per version. |
| Bundle | Synonym for "published flow" when emphasizing that it can contain multiple flows. |
| Parameter | A value in the flow that uses a Langflow Global Variable. Parameters are deduplicated across all flows in a bundle by variable name. |
| Credential | A parameter whose input is a Langflow secret field (SecretStrInput), typically a password, API key, or token the flow uses to reach a downstream resource such as a database or model API. Not a credential for accessing the deployed flow itself (that is HM machine-user authentication, see Accessing deployed flows). Credentials never carry defaults at publish time. Their values are supplied at deploy time and stored as Kubernetes secrets. |
| Access level | Either project (visible only to users with access to one of a chosen list of HM projects) or global (visible to all projects). Configured at publish time, editable later. |
| Deployed flow | A running instantiation of a published flow in an HM project. Visible at Estate > Flows (/estate/flows). Each deployed flow is isolated in its own Kubernetes namespace. |
| Runtime | The Langflow runtime container that hosts a deployed flow. Exposes an HTTP API and an MCP server, both routed through the HM gateway. |
Required roles
Permissions for the publish/deploy lifecycle are defined in Roles:
| Action | Required role |
|---|---|
| View published flows | Project Viewer (project-scoped) or any organization role (global) |
| Publish a flow / create new version | Project Admin or Project Member, for each project granted access |
| Edit a published flow (defaults, access list) | Project Admin or Project Member |
| Delete a published flow version | Organization Admin |
| Deploy a published flow | Project Admin or Project Member |
| View deployed flows | Project Viewer |
| Edit / undeploy a deployed flow | Project Admin or Project Member |
What's next
- Publishing bundles: Package flows from Langflow into an Asset Library bundle.
- Deploying flows: Turn a published bundle into a running deployment with its own parameter values and resources.
- Accessing deployed flows: Invoke a deployed flow over HTTP or MCP.
Publishing bundles
Package one or more Langflow flows into an immutable bundle in the Hybrid Manager Asset Library.
Deploying flows
Deploy a published bundle as a managed workload in a Hybrid Manager project, with its own parameter values, resource limits, and endpoints.
Accessing deployed flows
Invoke a deployed flow over HTTP or MCP using a Hybrid Manager machine-user access key.