Infrastructure, provider and configuration automation

Use OpenTofu, Python and Ansible where each fits best.

IntelliconOps adds declarative OpenTofu plan and state management alongside its provider-aware Python orchestration and validated Ansible guest configuration—without forcing every cloud operation through one engine.

Book a demonstration

Choose the right execution path

OpenTofu
Plan and apply approved declarative infrastructure modules.
Python
Discover, validate and operate through provider APIs.
Ansible
Apply approved operating-system and service configuration.
IntelliconOps
Govern the decision and connect results to shared inventory.

One governed workflow

Keep infrastructure and configuration connected.

For Blueprint jobs, Blueprint Studio defines the ordered Python and Ansible workflow. OpenTofu deployments use their own validate, plan, approve and apply lifecycle, then synchronise managed resources into the same inventory.

  • Provider-aware execution through a private Python worker
  • Ordered and dependency-aware Ansible workflow steps
  • Controlled OpenTofu modules, saved plans and encrypted state
  • Step-level attempts, outputs, errors and timestamps

Clear responsibilities

Three engines. Distinct jobs. One governed control plane.

Declarative infrastructure

OpenTofu manages approved infrastructure state.

A controlled module and typed inputs produce a saved plan. An authorised operator reviews that exact proposal before IntelliconOps applies it and captures the resulting state.

  • Versioned, allow-listed infrastructure modules
  • Saved plan approval and deployment locking
  • Encrypted artifacts and managed-resource synchronisation

Provider automation

Python handles provider orchestration.

The authenticated worker selects the configured AWS, Azure or Google Cloud adapter and performs the approved operation through provider APIs and SDKs.

  • Preflight, discovery, pricing and provider validation
  • Resource creation and day-two lifecycle actions
  • Sanitised results, correlation identifiers and resource records

Guest automation

Ansible configures the service inside the machine.

Once a machine is ready and guest connectivity is available, approved Ansible steps apply the operating-system and application configuration defined by the Blueprint.

  • Idempotent operating-system and service configuration
  • Bounded execution with syntax and policy validation
  • Health checks and tracked post-provisioning outcomes

The automation boundary

Keep infrastructure lifecycle and guest configuration separate.

OpenTofu is strongest when it describes cloud resources and reconciles state. Ansible is strongest when it configures the operating system and services after a machine is reachable.

IntelliconOps does not use unrestricted OpenTofu remote-exec or local-exec provisioners as a substitute for governed Ansible workflows.
OpenTofuNetworks · compute · disks · interfaces · state
PythonDiscovery · preflight · provider actions · reconciliation
AnsiblePackages · services · files · application configuration
IntelliconOpsPermissions · approvals · execution history · inventory

Inside Blueprint Studio

Build the complete workflow from an AI-assisted proposal.

The prompt proposes a revision; each tab makes the resulting service definition visible for human review before it is validated and published.

Select any screenshot to inspect it at full size.

1

Overview and AI revision

Review the blueprint identity, approval requirement and day-two actions while prompting the configured AI integration for a proposed change.

2

Request form

Define typed request fields, required values, defaults and UI hints instead of accepting arbitrary input.

3

Provisioning workflow

Inspect the ordered guest-readiness, Python provider and embedded Ansible workflow definition.

4

Maintenance actions

Add versioned operational workflows and refer to sensitive values through vault references rather than inline secrets.

5

Changes and publication

Compare the draft with its published base, record a changelog and explicitly publish an immutable semantic version.

6

Validation

Confirm the workflow contract, guest-readiness steps and Ansible syntax checks passed before publication.

7

Complete source

Inspect the complete provider-neutral blueprint document that brings metadata, schema and workflows together.

Current product boundary

Separate execution paths today. Shared operational context now.

Blueprint-based Python and Ansible jobs and dedicated OpenTofu deployments are controlled separately today. OpenTofu-created resources are synchronised into IntelliconOps inventory; composing OpenTofu and Ansible into one Blueprint workflow is a future integration.

Built for recoverability

Resume configuration without rebuilding successful infrastructure.

Provider ready

Provider provisioning completes and its resource result is retained before guest automation begins.

Configuration tracked

Each required Ansible or validation step records its status, attempts, bounded output and timing.

Failure isolated

A required post-provisioning failure marks configuration as failed without discarding the provider result.

Resume safely

An authorised retry preserves successful steps and continues from the first failed workflow step.

Execution safeguards

Reviewable automation with bounded execution.

  • Generated workflow and Ansible content remains a draft until reviewed
  • Unsafe modules, sensitive inline values and invalid syntax are rejected
  • Vault references resolve only when an executable step is sent to the worker
  • Temporary playbook files are removed after isolated execution
  • Timeouts, retries and output size are constrained by the workflow contract

See IntelliconOps in action

Give every cloud request a clear, controlled path.

Tell us how your teams manage infrastructure today. We will show you how IntelliconOps can simplify the work.

Book a demonstration