Workflow Orchestration across clouds

Managed state machines - Step Functions, Logic Apps, Workflows - that call services in order, retry the right steps, and keep a record of every run.

3 verified modules, 3 of them live-tested apply→verify→destroy; the rest are static-validated, live-test pending.

Compare by provider

ProviderModuleVerification
AWSStep Functions State Machine✓ live-tested
AzureLogic App (Consumption) Workflow✓ live-tested
Google CloudCloud Workflows (least-privilege identity)✓ live-tested

How to choose

Compare how the definition is written (JSON states, a designer, YAML), what the workflow runs as and whether each step can be scoped, how long a run may last, and what an execution history costs to keep: the record of every run is the reason to use these, and also the bill.

When not to use

A workflow is code with a worse diff. Keep the definition in version control with the module, and treat a retry policy as a decision per step, because retrying a payment is not the same as retrying a lookup.

Other solutions