Menu
The New Stack·March 26, 2026

Bridging the Cloud Operational Gap with Integrated Governance

This article discusses the emerging 'Operational Gap' in cloud environments, where the rapid pace of infrastructure changes, often driven by AI, outstrips manual governance capabilities. It highlights the architectural challenge of disconnected Day 1 provisioning and Day 2 operations tooling, advocating for an integrated platform that provides continuous visibility and controlled remediation to enforce policy and manage compliance across the entire infrastructure lifecycle.

Read original on The New Stack

Understanding the Cloud Operational Gap

The article identifies a significant challenge in modern cloud operations: the "Operational Gap." This gap arises from the disconnect between observing what's deployed (visibility) and actually controlling or governing it. Historically, this gap was managed informally through manual scripts and institutional knowledge. However, the acceleration of software development, particularly with AI-generated infrastructure, has made these informal methods untenable due to the sheer volume and velocity of changes.

ℹ️

The Operational Gap is the divide between knowing what infrastructure exists and being able to safely and effectively govern or remediate misconfigurations and policy violations across dynamic cloud environments.

Split-Brain Problem in Platform Engineering

Platform engineering has traditionally faced a "split-brain problem," dividing concerns into Day 1 and Day 2 operations. Day 1 focuses on provisioning infrastructure safely with policies and approved workflows (e.g., using Infrastructure-as-Code). Day 2 encompasses post-provisioning activities like compliance, drift detection, cost management, and understanding the actual running state versus the intended state. These domains often use separate tooling and lack a shared data model, exacerbating the operational gap.

Integrated Platform for Continuous Governance

The merger of CloudQuery and env zero aims to address this by creating a unified platform. CloudQuery excelled at providing continuous, multi-cloud visibility and SQL-queryable data across infrastructure, security, and cost. env zero specialized in governing infrastructure at the point of delivery through policy enforcement, approval workflows, and audit trails. The combined platform seeks to close the loop by not only identifying issues (visibility) but also providing a governed remediation path, thereby treating the full infrastructure lifecycle as a single, governed system.

  • Day 1 (env zero's strength): Policy enforcement, approval workflows, audit trails, and drift detection during infrastructure deployment.
  • Day 2 (CloudQuery's strength): Continuous visibility, normalized and queryable data for deployed resources, security posture, and cost analysis.
  • Combined Value: When observed states diverge from declared intent, the platform has the context and mechanisms to act, not just alert, ensuring codified, continuous, and automatic governance.

The architectural approach focuses on making governance an inherent layer rather than an afterthought or a manual gate. This means encoding policies, automating remediation, and maintaining a complete, unambiguous record of infrastructure changes and states. This shifts governance from a human-dependent process to an integrated, infrastructure-level capability, crucial for managing the scale and complexity introduced by modern cloud-native development and AI-driven changes.

Cloud GovernancePlatform EngineeringInfrastructure as CodeComplianceObservabilityAutomationDay 2 OperationsCloud Security

Comments

Loading comments...