Workflow layer
Start here. This is the preferred way to build with ProviderPlane when you want explicit multi-step orchestration with less boilerplate.
ProviderPlane Documentation
Start with workflows, not raw provider calls. These docs take you from installation and provider configuration to a first workflow.
Start here
Most users only need a few pages to get moving: install the library, understand the workflow model, copy a representative example, then use the API reference for exact signatures.
Getting StartedInstall ProviderPlane, configure one provider, and build your first workflow.ConceptsUnderstand the workflow layer, the lower execution layers, and how they fit together.ExamplesUse runnable workflow, persistence, job, and direct-client examples as templates.ConfigurationDefine provider connections, execution policy, and the default provider chain.API ReferenceUse the reference when you need exact types, method signatures, and option details.
Pick the right layer
ProviderPlane has multiple public layers, but they are not equal starting points. Most applications should stay at the workflow layer unless there is a clear reason to move lower.
Job system
Use jobs when you need lower-level control over individual executions. Compared with the workflow layer, they require more manual orchestration.
Direct client
Use direct client calls only for isolated capability access. This is the thinnest layer and the most manual once calls start depending on each other.
Examples to explore
Use these runnable examples as practical patterns once the basic workflow model makes sense.
Workflow example
The recommended way to build with ProviderPlane: explicit multi-step workflows with fan-out, fan-in, approval, and custom logic.
Persistence and resume
A workflow example that fails intentionally, persists state, and resumes from a later run.
Job example
A single capability call run through the job system for finer execution control.
Direct client example
The thinnest public layer for one-off capability calls when you do not want jobs or a workflow graph.