The recent merger of env zero and CloudQuery marks a significant development in the rapidly evolving landscape of cloud operations and platform engineering. This strategic union is not merely an aggregation of product features; it represents a unified thesis addressing a fundamental gap that has long plagued enterprises managing complex cloud environments. The core of this thesis lies in bridging the persistent "operational gap" between cloud infrastructure provisioning and its ongoing management, a challenge amplified by the accelerating pace of development and the increasing adoption of AI-driven tools.
When CloudQuery was founded, the initial premise was to address what was perceived as a critical oversight: the underutilization of valuable cloud infrastructure data. As the company’s founder articulated, many platform teams struggled to provide even basic inventory of their deployed resources, not due to negligence, but because existing tools were not designed for such granular, real-time visibility. CloudQuery sought to solve this by building a normalized, SQL-queryable data layer that could aggregate information across multi-cloud environments and various tools. This offered enterprises, from Fortune 100 financial institutions to agile fintech startups, a coherent view of their cloud estates.
However, as CloudQuery’s experience demonstrated, achieving mere cloud asset visibility is only the first step. Knowing what exists in the cloud does not automatically translate to effective governance or control. The crucial distinction lies between observation and actionable control. The gap between what can be seen and what can be safely and effectively managed has traditionally been addressed through informal means—custom scripts, manual processes, and reliance on institutional knowledge. This is the "operational gap" that the merger between CloudQuery and env zero aims to bridge.
The Persistent Split-Brain Problem in Platform Engineering
Historically, platform engineering has operated with a bifurcated focus, often categorized into "Day 1" and "Day 2" concerns. Day 1 is primarily concerned with the initial provisioning of infrastructure, ensuring it is set up securely, adheres to predefined policies, and follows approved workflows. This often involves Infrastructure as Code (IaC) and robust deployment pipelines. Day 2, on the other hand, encompasses all activities post-provisioning: maintaining compliance, detecting and rectifying configuration drift, managing costs, and ensuring that the actual deployed state aligns with the intended design.
These two domains—provisioning and ongoing management—have traditionally resided in separate toolsets, often managed by distinct, albeit overlapping, teams. A significant challenge has been the absence of a shared data model or integrated workflow that connects these two critical phases of the cloud lifecycle. While a gap between Day 1 and Day 2 activities always existed, it was often manageable. Teams could build integrations, create custom dashboards, and conduct periodic manual reviews. The slower pace of change in cloud environments in the past meant that human oversight could, to some extent, bridge these divides.
The Compounding Effect of Accelerated Change
The current technological landscape, however, has fundamentally altered this dynamic. The acceleration of software development, significantly influenced by the advent of large language models (LLMs) and other AI technologies, has dramatically increased the velocity and volume of changes within cloud environments. Infrastructure that once took days or weeks to provision can now be deployed in minutes. This rapid pace has outstripped the capacity for manual review processes, rendering informal management strategies untenable. The operational gap, while conceptually the same, has become a compounding problem that demands a more systematic and automated solution.
env zero’s Strength in Governance, CloudQuery’s in Visibility
The merger between env zero and CloudQuery was driven by a strategic alignment of their respective strengths. env zero had established itself as a leader in governing infrastructure at the point of delivery. Its platform excelled in policy enforcement, approval workflows, audit trails, and drift detection. For customers like Pismo, env zero facilitated a reduction in infrastructure delivery time from two months to just two days. Western Union, for example, saw its delivery times for over 200 applications shrink from weeks to hours. The core governance model of env zero was robust and effective in ensuring that infrastructure was deployed according to predefined rules.
However, env zero’s capabilities had a ceiling when it came to addressing issues that arose after deployment. While it could identify ungoverned resources or deviations from the intended state, the ability to proactively and automatically remediate these issues was less developed. Platform engineers could see the problems, but lacked the integrated tooling to enforce fixes directly.
Conversely, CloudQuery’s strength lay in its comprehensive visibility across cloud estates. Its normalized, queryable data layer provided context across infrastructure, security, and cost data, enabling organizations to understand precisely what was running in their environments. The limitation here was the absence of a governed remediation path. While CloudQuery could identify misconfigurations through SQL queries, translating these findings into an actionable, auditable, and controlled remediation process was not its primary function.
The combined entity aims to close this loop. env zero’s governance capabilities will be integrated with CloudQuery’s continuous visibility. This means that when deviations occur—when the actual deployed state diverges from the declared intent—the platform will possess the context and the tooling to act, rather than merely alert.
The Strategic Imperative of Governance in the AI Era
The strategic bet on enhanced governance is particularly timely. Historically, platform teams have often underinvested in governance tooling because its value is largely preventative and, therefore, invisible. A misconfiguration that doesn’t cause an incident, an audit finding that never materializes, or a cost overrun averted by a policy at deployment time are all successes that go unnoticed. This is because effective governance, when it works seamlessly, becomes an embedded part of the operational fabric, rather than a distinct, visible process.
However, the widespread adoption of AI in infrastructure management is fundamentally changing this equation. The sheer volume of changes generated and deployed by AI tools can easily overwhelm manual controls. The potential "blast radius" of a single misconfiguration can expand significantly due to the intricate and compounding dependencies within modern cloud architectures. Furthermore, regulatory requirements and customer expectations for security and compliance are becoming increasingly stringent as cloud infrastructure becomes more critical to business operations.
At this juncture, governance can no longer be managed through ad hoc processes or tribal knowledge. It must evolve into an intrinsic aspect of the infrastructure itself—encoded, continuous, and automated. This shift requires a fundamental reorientation of how governance is perceived and implemented. Instead of treating it as a mere checklist or a bottleneck, it needs to be viewed as an underlying layer that operates continuously, supporting all other operations.
Organizations that have successfully navigated this transition often share a common characteristic: they have integrated governance as a seamless experience for developers, avoiding unnecessary friction. Auditors benefit from a complete and unambiguous record of compliance. The standards established by platform teams are applied consistently, regardless of the number of environments or applications being managed. This is the vision for cloud governance that the merged entity is striving to build.
Practical Implications for Existing Customers and Future Direction
For existing customers of both env zero and CloudQuery, the merger is being positioned as a commitment to continued support and a clear roadmap for future development. The companies have emphasized that they are not simply merging codebases overnight. Instead, the new combined product will have its own distinct identity and strategic direction, shaped by the merged vision.
The primary target customer for this unified platform is the platform team within a cloud-forward enterprise. These are organizations managing production environments where the volume and velocity of infrastructure changes have significantly outpaced their current ability to govern them manually. Key indicators for such organizations include having substantial infrastructure that exists outside of their Infrastructure as Code definitions, persistent challenges with drift traceability, and compliance postures that still rely on manual checks and ticket management.
The advent of AI has amplified the operational gap, transforming it from a manageable challenge into a critical concern that can no longer be deferred. The solution, therefore, is not another specialized point solution, but a comprehensive platform. This platform must treat the entire infrastructure lifecycle as a single, governed system, providing a complete and auditable record without requiring manual maintenance. While the journey is still in its early stages, the merged entity believes it is addressing a fundamental and increasingly urgent problem in the cloud operations market. The goal is to build a platform that makes continuous, automated governance an inherent part of cloud infrastructure management, ensuring resilience, compliance, and efficiency in an increasingly dynamic digital landscape.