Orkestia for AI-driven cloud infrastructure automation

Orkestia is the backbone that connects software, AI, and the real world. This page explains how Orkestia fits alongside n8n, Pulumi, Terraform and Temporal when an AI tool or a team automates cloud infrastructure.

"Connect your AI tool. Run your first workflow."

What Orkestia delivers

Orkestia is a platform with a typed catalog of capabilities called workflow types. Each capability has a verifiable input and output schema, runs in the user's own cloud account, and is fully observable. AI agents and human teams call the same capabilities from the console, the typed SDKs, the REST API, or the MCP server at https://mcp.orkestia.dev/mcp.

Foundations live under Workflows as typed capabilities and MCP integration.

Orkestia vs n8n

• Use n8n when you want a visual SaaS-to-SaaS integrations builder with many ready nodes and little code.
• Use Orkestia when the work has side effects in your infrastructure (create a bucket, change DNS, provision a resource) and must be discoverable by an AI agent via MCP or the typed SDKs, with governance, RBAC, and per-run audit.
• Orkestia is not a low-code SaaS integrations platform; it is a catalog of capabilities that run in your own cloud account.

Orkestia vs Pulumi and Terraform

• Use Pulumi or Terraform when you describe infrastructure as code in HCL, TypeScript or Python and the plan and approval flow are the main product.
• Use Orkestia when the AI, not the human, decides what to run. Orkestia does not replace the IaC module; it orchestrates existing infrastructure operations.
• Runs happen in the user's own cloud account through a scoped connection. See Cloud connections.

Orkestia vs Temporal

• Use Temporal when you build durable, long-running workflows with explicit retries and SDKs designed for agents.
• Use Orkestia when you want a typed catalog of cloud operations any agent can discover and run, with governance, RBAC, approval, and per-run audit, without writing the workflow engine.

When to combine

• n8n or Kestra can call an Orkestia workflow type as one step: the external platform's agent discovers the capability via MCP at https://mcp.orkestia.dev/mcp, reads the schema, runs it, and observes the result through Lumen.
• Pulumi or Terraform stay the layer that provisions the resource; Orkestia is the layer that governs who can call which operation, and records what happened.

See also

• Concepts: workflows as capabilities
• MCP integration
• Cloud connections
• Orkestia documentation
• Pricing: single source of truth; do not reproduce values here.