Forge is preparing the requested surface and verifying the live route.
Forge is preparing the requested surface and verifying the live route.
Forge Pipeline turns tool calls, engine usage, and agent stages into one governed workflow surface.
Pipeline is the product surface for chained execution inside Forge Foundry. It lets customers define step-by-step or graph-shaped workflows without losing the managed billing, policy, and validation layers that Forge applies to every run.
Like the rest of the platform, Pipeline is bundled for paid Forge subscribers while still supporting pay-per-use access for buyers who only need the underlying capability on demand.
These are the execution patterns that make Pipeline a distinct customer-facing surface.
Forge Pipeline can execute linear chains, branched workflows, or graph-based task plans while tracking dependencies and outputs across every stage.
Each stage can call a model, a tool, an engine, or a multi-agent subflow so teams can combine product surfaces without rebuilding orchestration infrastructure.
Pipeline execution keeps billing, validation, and policy enforcement attached to the workflow instead of leaving those concerns to custom code.
Pipeline follows the same bundled-plus-metered model that now drives tool and engine access across Forge.
Subscribed Forge users get Pipeline as part of the managed platform, so end-to-end workflow orchestration is bundled into the paid plan experience.
When a non-subscriber or autonomous agent only wants specific pipeline-backed capability, Forge can still expose the underlying execution through pay-per-use engine access.
Enterprise customers and outside automation systems can adopt Pipeline through account-scoped billing, contracts, and machine-payment rails instead of being forced into one buyer profile.
Use Forge plans for the full managed platform or meter the underlying engine access directly.