InfraOrcinus Insights

Technical essays on governed infrastructure as code: Terraform and OpenTofu architecture, AI agent guardrails, human approval, state, security and audit.

• Azure Bicep and AWS CloudFormation in InfraOrcinus: What-If, Change Sets and One Approval Gate - Azure Bicep and AWS CloudFormation now run through the same validate, plan, approve and apply lifecycle as Terraform, OpenTofu and Pulumi. How Bicep what-if and CloudFormation change sets map onto one plan model, how tightly each binds the approval to the apply, and what is not supported yet.
• How InfraOrcinus Detects and Reconciles Cloud Drift - How InfraOrcinus finds drift with scheduled, plan-only checks on every engine, shows the per-resource diff, alerts the team, and fixes drift only through the normal named approval gate. What a check does and does not tell you, and the limits today.
• Guarding the Supply Chain: The Four Automated Security Gates of the InfraOrcinus Control Plane - How InfraOrcinus secures its own control plane before code merges: race-detected tests against real PostgreSQL, Semgrep OWASP rules, OSV-Scanner and Trivy for dependencies and images, and full-history gitleaks with local hooks. Plus the gates that once looked green without checking anything, and how we fixed them.
• Unifying Terraform, OpenTofu, and Pulumi: How InfraOrcinus Normalizes Multi-Engine Delivery - How InfraOrcinus abstracts diverse IaC dialects into a canonical PlanSummary model. Enabling enterprise platform teams to enforce unified security policies, pre-flight cost estimation, and human approvals regardless of the underlying engine.
• The Named Human Approval Gate: Human-in-the-Loop Governance in InfraOrcinus - Why InfraOrcinus deterministically halts before applying infrastructure changes. An exploration of the named approval protocol, separation of duties enforced on every run, attribution of each decision, and applying the exact plan that was approved.
• The InfraOrcinus Native State Backend: Atomic Locking and Encrypted State - How InfraOrcinus implements its own native HTTP remote state backend. An architectural deep-dive into atomic PostgreSQL locks, AES-256-GCM encryption of state at rest with optional Vault Transit, and what the backend does and does not yet provide.
• Inside the InfraOrcinus Runner: Ephemeral Execution, Job Leases, and Command Defense - An engineering deep-dive into the InfraOrcinus execution runner. How atomic job claims, single-use container sandboxing, POSIX parameter quoting, and structured JSON serialization reduce command-injection risk. Container hardening and network isolation are partly operator responsibilities, and the article says which parts.
• Why InfraOrcinus Runs on PostgreSQL: Relational Rigor, ACID Governance, and Sovereign Architecture - Why we deliberately chose PostgreSQL over cloud-native document stores like Azure Cosmos DB. An architectural deep-dive into state locking, relational ACID guarantees, application-layer encryption, and zero-vendor-lock-in sovereignty.
• Why I Am Building InfraOrcinus: The Future of Governed Infrastructure in the Era of AI - Large-scale infrastructure delivery remains one of modern computing's most brittle frontiers. Here is why passive automation fails, why unconstrained AI agents pose severe risks, and how InfraOrcinus bridges autonomous speed with sovereign, human-in-the-loop governance.