AWS
Amazon Web Services
- IAM Roles Anywhere account identity
- EC2 create, discover and lifecycle operations
- Instance type, AMI, VPC and subnet-aware inputs
- Guided VPC and WireGuard private connectivity
Three connected cloud providers
One operating model across AWS, Azure and Google Cloud.
IntelliconOps puts provider-aware provisioning, lifecycle operations, approvals, execution history and inventory behind one control plane—without hiding the real differences between EC2, Azure Virtual Machines and Google Compute Engine.
Discuss your cloud environmentIntelliconOps control plane
Identity · policy · automation · jobs · audit · inventory
AWSConnected
Microsoft AzureConnected
Google CloudConnected
Provider capabilities available now
A real adapter for each cloud—not three labels on one generic form.
Each integration authenticates within its own cloud boundary and understands that provider’s compute, network and lifecycle semantics.
Azure
Microsoft Azure
- Subscription and service-principal account boundary
- VM, disk, network and lifecycle operations
- SKU, image, subnet, quota and pricing controls
- VNet, WireGuard, browser SSH and Bastion paths
GCP
Google Cloud
- Project and service-account boundary
- Compute Engine create, start, stop, restart and delete
- Machine-type, zone, subnet, preflight and cost controls
- Guided VPC, firewall and WireGuard connectivity
Capability map
Shared experience. Explicit provider coverage.
The control plane stays consistent while capability labels show where provider implementation and acceptance are at different stages.
| Capability | AWS | Microsoft Azure | Google Cloud |
|---|---|---|---|
| Cloud account and credentials | AvailableIAM Roles Anywhere | AvailableSubscription identity | AvailableProject service account |
| VM provisioning and lifecycle | AvailableEC2 | AvailableAzure Virtual Machines | AvailableCompute Engine |
| Provider-aware Blueprint inputs | AvailableAMI, type and subnet | AvailableImage, SKU and subnet | AvailableImage, machine type and subnet |
| Private cloud connectivity | AvailableVPC and WireGuard | AvailableVNet and WireGuard | AvailableVPC and WireGuard |
| OpenTofu Linux VM module | FoundationControlled planning implemented | Live apply provenVM and NIC synchronised | Next milestoneControlled module not yet implemented |
Shared control plane
Keep organisational controls above the provider boundary.
Identity and access
Use the same users, roles, effective permissions and scoped groups to govern platform access.
Provider-aware catalogue
Keep the provider, input contract, version and supported actions visible on each Blueprint.
Requests and approvals
Route work through visible group, permission and approval boundaries before execution.
Jobs and evidence
Track events, workflow results, errors, decisions and resource outcomes in a durable record.
Shared inventory
Bring discovered, Blueprint-created and OpenTofu-managed resources into connected operational views.
Provider-specific execution
Normalise the workflow—not the cloud itself.
The private worker selects the relevant provider adapter and credentials. Each adapter returns a normalised result while retaining cloud-specific diagnostics and resource identifiers.
- Use cloud-native authentication within the selected account boundary
- Discover provider-specific regions, zones, sizes, images and networks
- Run preflight and lifecycle operations through supported APIs and tools
- Return sanitised state, correlation identifiers and resource records
Provider-neutral does not mean provider-identical. IntelliconOps shares governance and evidence while leaving provider differences explicit.
OpenTofu across providers
One execution lifecycle, delivered provider by provider.
The validate, plan, approve and apply controls are shared. Module implementation and live-cloud acceptance remain explicit for each provider.
AWS planning foundation
The controlled AWS Linux VM module, typed inputs, credential adapter, plan parsing and inventory-linking foundation are implemented. Repeat-plan and live apply acceptance remain to be completed.
Azure live apply proven
A saved and approved OpenTofu plan has created a live Azure VM and NIC, synchronised inventory and retained encrypted state across worker rebuilds.
Google Cloud module
The working GCP account and provider integrations will be reused, but the controlled gcp/linux_vm OpenTofu module and its UI discovery controls are not yet implemented.
Provider-aware Blueprints
A shared catalogue that keeps the target cloud visible.
Blueprints use the same publication and request lifecycle while exposing the inputs appropriate to AWS, Azure or Google Cloud. This screenshot is an Azure catalogue example.
Explore prompt-led BlueprintsBuild a consistent cloud operating model
Connect the clouds you use without losing provider context.
Bring AWS, Microsoft Azure and Google Cloud operations into one governed platform while retaining the identities, inputs, diagnostics and resource models that make each provider different.
Explore the platformSee 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