◆
Terraform terraform
HashiCorp Terraform — declarative infrastructure provisioning with plan/apply lifecycle.
Administration — IaC Engines
Govern infrastructure-as-code engines, version lifecycles, runtime images, and deployment compatibility across your organization.
Open Administration → IaC Engines
Permissions
| Action | Permission |
|---|---|
| View hub, engine directory, version inventory, runtime images, insights | iac:engine:admin |
| Add/edit/deprecate/delete versions, set default, runtime image policy | iac:engine:admin |
Members without iac:engine:admin cannot open this page. Version tables show Read only when manage permission is absent after load.
Engine governance overview
Top summary shows live metrics from the org catalog and dashboard — not fixed counts. Includes platform default engine chip, operational alerts, and Refresh.
Catalog enginesEngines in the organization catalog
Engines in useFrom org dashboard (
iacEnginesInUse)Managed stacksTotal stacks in the organization
Needs attentionMissing versions, deprecated default, or no supported versions
Click a metric to filter or navigate (for example Needs attention opens Engine Directory with the Needs attention filter). An info banner links to the Runtime Images tab for image policy and registry setup.
Engine Directory
Table view — search, filter, sort, and open engines. There is no Add engine action; the platform catalog includes six engine types. You add and manage versions per engine.
Search — engine name, slug, type, default version
Filter — All engines · Needs attention · Has deprecated versions · In use by stacks
Sort — Name · Configuration status · Stacks in use
| Column | Description |
|---|---|
| Engine | Name, slug, logo |
| Configuration | Not Configured, Warning, or Configured |
| Default version | Organization default for new stacks |
| Supported | Count of SUPPORTED versions / total versions |
| Deprecated | Count of deprecated, end-of-support, or archived versions |
| Stacks in use | Active stacks on this engine |
| Actions | Open (engine detail) · Versions |
Supported catalog engines
Six engine types are seeded per organization. Slugs and versions are provided by the engine catalog.
Terraform
◆
OpenTofu opentofu
Open-source Terraform fork with community-driven governance.
●
Pulumi pulumi
Modern infrastructure as code using familiar programming languages.
☁
Crossplane crossplane
Kubernetes-native control plane for cloud infrastructure.
▣
CloudFormation cloudformation
AWS-native infrastructure provisioning with stack sets and change sets.
<>
Azure ARM / Bicep arm-bicep
Azure Resource Manager and Bicep templates for Azure infrastructure.
Version Inventory
Organization-wide table of all engine versions. Filter by engine, lifecycle status, and search. Columns: Engine, Version, Lifecycle, Default, Support ends, Stacks, Manage (opens engine versions tab).
Lifecycle statuses: SUPPORTED, DEPRECATED, END_OF_SUPPORT, ARCHIVED. Insights charts may also bucket versions as Default / LTS / Supported / Deprecated for analytics.
Runtime Images
Organization policy and per-engine mappings:
- Runtime image policy — allow Public, Axio standard, and/or Custom images; set default source (
PUBLIC,AXIO, orCUSTOM) - Per-engine table — version count and default version
- Custom images — map overrides per version when custom images are enabled; requires container registries under Integrations
Runners use catalog default images (public or Axio) unless custom policy overrides apply.
Insights
Adoption trends, deployment health, and lifecycle recommendations:
- Engine adoption, version distribution, deployment distribution charts
- Engine adoption trend (7d / 30d / 90d range toggle)
- Execution KPIs — executions, success rate, average runtime, failed runs
- Lifecycle recommendations (for example upgrade deprecated defaults)
Version lifecycle
- Supported: Recommended for production; status
SUPPORTED - Default: Version used for newly created stacks (
isDefaultflag) - Deprecated: Available but not recommended; includes
DEPRECATED,END_OF_SUPPORT,ARCHIVED - Deprecation flow: Set replacement version, support end date, and message; banner shown when default is deprecated
Changing defaults affects new stacks only — existing stack executions keep their pinned version.
Engine detail page
Open any engine at with tabs:
- Overview — latest, default, installed counts, status summary
- Versions — search/filter; Add Version, Edit, Set Default, Deprecate, Delete
- Deprecation — deprecated version cards with replacement guidance
- Runtime Images — public/Axio images per version; custom image overrides
- Compatibility — platform, Kubernetes, plugin compatibility matrix
- Settings — slug, type, description metadata
- Audit History — engine-scoped audit events