Necessary storage
Your selected language is stored for twelve months. This setting and the choice made here are used only to operate this website.
Tools · Infrastructure as Code
OpenTofu & Terraform
Describes infrastructure declaratively and calculates a reviewable change plan from configuration, provider schemas and known state. OpenTofu and Terraform are treated as separate tools with their own governance, licensing and version evolution.
Tools · Orthevs
OpenTofu & Terraform as an integrable tool
This technology may become part of a Factory. The Factory defines the domain tool function; scope, version, permissions, target environment and outputs must be evaluated for each integration.
Technical purpose
OpenTofu & Terraform
OpenTofu and Terraform translate declarative configurations into concrete resource operations through providers. Configuration and state first produce a plan that exposes intended creations, changes and deletions; only a subsequent apply step executes approved operations. Resource dependencies are evaluated as a graph, while modules encapsulate reusable infrastructure components. The tools share historical foundations but evolve independently and therefore must not be assumed to be universally interchangeable.
Technology profile
Technology profile
- Category
- Infrastructure as Code
- Operating model
- Configuration and state produce a plan; apply executes the approved plan through providers
- Definitions
- HCL configurations, providers, modules, variables and outputs
- State model
- Local or remote state; protection and locking depend on the backend
- Project governance
- OpenTofu: Linux Foundation · Terraform: HashiCorp
- License status
- OpenTofu: MPL-2.0 open source · Terraform: current code is source-available
Integration in Orthevs
Orthevs Ecosystem
IEL Factories separate initialization, validation, planning, policy checks, approval and apply into traceable steps. The selected tool, exact version, provider and module dependencies, backend configuration and digest of the approved plan are defined in the capability contract. State is accessed only through protected backends with locking, while plans and apply results are referenced as evidence. A Foundation describes the intended outcome without binding its domain logic to the CLI behavior of a single IaC tool.
Relevant capabilities
Relevant capabilities
- Provider-based resource models for infrastructure and platform-service APIs
- Explicit plan before mutation with visible creations, changes and deletions
- Dependency graph and controlled parallelization of independent operations
- Modules, variables and outputs for reusable infrastructure definitions
- Import of existing resources and detection of deviations from known state
- Backend-based state with locking and protection mechanisms available according to the implementation
Operating boundaries
Operating boundaries
State can contain sensitive values and extensive infrastructure information. Encryption, access control, locking, backup and recovery are mandatory operating requirements.
Providers and modules are executable supply-chain dependencies. Provenance, version, checksum, required privileges and updates must be controlled.
An error-free plan does not prove a safe or domain-correct architecture. Policy, security and qualification gates remain separate validations.
Compatibility between OpenTofu and Terraform is validated per version, provider and module. Licensing and governance differences remain explicitly visible.
IAC · Orthevs
Shape the target model together.
The content will be deepened step by step with concrete concepts, contracts, maturity levels and verifiable evidence.