<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Quali Blogs - Medium]]></title>
        <description><![CDATA[This publication provides you with blogs from Quali about internal dev topics and related industry topics around DevOps, Platform Engineering and AI. - Medium]]></description>
        <link>https://medium.com/quali-blogs?source=rss----b65ab89c8023---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Quali Blogs - Medium</title>
            <link>https://medium.com/quali-blogs?source=rss----b65ab89c8023---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 02:36:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/quali-blogs" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Federated Infrastructure: The New Economics of IT Infrastructure]]></title>
            <link>https://medium.com/quali-blogs/federated-infrastructure-the-new-economics-of-it-infrastructure-6ffddf06a11f?source=rss----b65ab89c8023---4</link>
            <guid isPermaLink="false">https://medium.com/p/6ffddf06a11f</guid>
            <category><![CDATA[infrastructure-as-code]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[David Williams]]></dc:creator>
            <pubDate>Tue, 10 Nov 2026 18:06:13 GMT</pubDate>
            <atom:updated>2026-11-10T18:06:13.367Z</atom:updated>
            <content:encoded><![CDATA[<p>Turning infrastructure from a fixed cost into a reusable asset that can be shared, extended, valued and monetized.</p><p>By Lior Koriat, Quali CEO and Edan Evantal, Quali CTO</p><h3>1. The New Economics of IT Infrastructure</h3><p>IT infrastructure has traditionally been valued by the applications and services it supports. Compute, networks, storage, cloud capacity and increasingly scarce GPUs are acquired, integrated and operated within organizational boundaries. Yet the same investments frequently remain fragmented across sites, teams and providers. Capacity may be idle in one location while another team purchases more. Validated environments are rebuilt elsewhere because the original configuration cannot readily be consumed outside its home organization.</p><p>Federated Infrastructure changes the economic reach of those assets. An enterprise can make a governed GPU environment available to another business unit, extend a validated stack to a partner, or consume specialized capacity without reproducing its infrastructure. Providers keep ownership and operational control; consumers gain access to a defined capability. Organizations can begin with a single resource or relationship and expand as value is demonstrated.</p><p><strong><em>Federation does not make infrastructure valuable. It makes infrastructure value transferable.</em></strong></p><p>That distinction is the thesis of this paper. A capability can be consumed by one organization, combined with software or services from another, and incorporated into a new Offering. The economic benefit may be better utilization and avoided duplication within an enterprise, or new distribution, service revenue and commercial reach across organizations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/980/1*MbJn7cpP9_CSfa6AVY4BPg.png" /><figcaption>Figure 1. <em>Strategic drivers for Federated Infrastructure.</em></figcaption></figure><h3>2. A Common Language Across a Federated Mesh</h3><p>Federation begins with heterogeneous infrastructure: physical systems, private and public clouds, Kubernetes, GPUs, networks, storage and edge locations. Their APIs, policies, operational conventions and lifecycle requirements differ. Attempting to make every environment identical would defeat the purpose. Instead, an infrastructure control plane provides a common language for defining, governing, delivering and operating the capabilities they expose.</p><p>Each participating site or provider acts as a node in a wider mesh. At the node, stack automation turns complex infrastructure and software configurations into repeatable, validated environments, with lifecycle controls that local operators can enforce. Across the mesh, a federated operating layer discovers and presents those capabilities as governed Offerings, connects eligible providers and consumers, and maintains the context needed for capacity, policy, identity, isolation, metering and attribution. The node retains its implementation and control; the mesh enables consistent consumption across boundaries.</p><p>An Offering describes the capability delivered, its dependencies, applicable policies, capacity and reservation conditions, and the terms of consumption. Consumers receive an outcome rather than unrestricted access to underlying systems. A GPU service might specify accelerator class, approved software stack, location, reservation duration, security requirements and usage measurements. Local operators decide what can be exposed and under what conditions.</p><p>An enterprise is itself a natural federation. Its headquarters data center, regional facilities, manufacturing sites, branch locations and edge installations may each own different resources and face different operational constraints. A validated environment created centrally can be delivered at a regional site; a specialized edge capability can be shared with an application team; unused capacity in one location can support demand from another. Locality, sovereignty, latency and security policies determine where execution is appropriate. Federation allows the enterprise to coordinate these assets without centralizing their ownership or requiring every site to adopt the same technology.</p><p>Roles are fluid. A regional site may provide compute capacity, consume centrally maintained software and contribute local data or operational services to an application Offering. An enterprise may consume a partner’s GPU capacity while providing its own validated model environment to subsidiaries or customers. Every participant can be provider, contributor and consumer simultaneously, depending on the Offering and the relationship.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/980/1*Nd0hM43hZmFs_YXBvkbHuw.png" /><figcaption>Figure 2. <em>A common control plane enables a federated operating model.</em></figcaption></figure><h3>3. Three Transformations: From Complexity to Economic Value</h3><h4>Simplifying technical complexity</h4><p>A common control plane absorbs infrastructure-specific integration and lifecycle differences. Developers, data scientists and application teams work with consistent definitions rather than rebuilding technical expertise for every environment. Infrastructure teams retain control of credentials, security boundaries, allocation and operating policies. Standardization occurs at the level of consumption and governance, while the technologies underneath remain diverse.</p><h4>Changing the operating model</h4><p>Repeatable environments become reusable Offerings. A team can publish a validated AI stack, a reserved GPU environment, a secure development workspace or an edge application capability for authorized consumers. The Offering carries the definition and operational rules needed to reproduce and manage the environment throughout its life, not merely at initial deployment. The provider can serve more consumers without exposing every internal detail or negotiating a new integration project each time.</p><h4>Changing the economics</h4><p>Once capabilities are reusable across boundaries, ownership and value creation no longer have to reside in the same organization. Infrastructure providers can improve asset utilization and reach new demand; software vendors can distribute validated configurations without purchasing hardware; service providers can assemble differentiated services from independently supplied components. Enterprises can avoid duplicated capital investment and use scarce resources more efficiently. Measurable consumption and attribution connect these operational capabilities to commercial arrangements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/980/1*GqhFY-5s0RRex2UoAPTecg.png" /><figcaption>Figure3. <em>From technical complexity to reusable capabilities and economic value.</em></figcaption></figure><h3>4. Following the Money: How an Offering Accumulates Value</h3><p>Consider a sovereign cloud provider that has invested in GPU infrastructure, facilities, compliance controls and operational expertise. Demand fluctuates, leaving expensive capacity underused at some times and constrained at others. The provider publishes a governed Offering that specifies GPU resources, availability, reservation rules, locality, security requirements and consumption measures. It retains ownership and operational responsibility.</p><p>A technology partner consumes the capacity and adds a validated AI software stack, configuration and licensing. It publishes a new Offering: a ready-to-use AI environment. A managed service provider then adds monitoring, service assurance, security operations and support. The customer purchases the resulting managed AI capability without separately integrating the underlying infrastructure, software and operations.</p><p>The economic relationships can remain independent. The cloud provider may charge for reserved capacity or GPU-hours. The technology partner may charge for subscriptions, software usage or licensed entitlements. The managed service provider may charge for operations and service commitments. A customer can pay the managed service provider, which settles its obligations with upstream partners under their respective agreements. Federation supplies the consistent operational definitions and consumption context; pricing, invoicing and settlement are handled by the relevant commercial systems.</p><p>The same resources can participate in multiple Offerings. A validated stack can serve several managed services; GPU capacity can support different workloads at different times; specialist expertise can be reused across customers. The important change is the ability to attribute each contribution and allow its value to travel through more than one commercial relationship.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/980/1*vu8sZoko74QhrXCLHoHEbQ.png" /><figcaption>Figure 4. <em>Contributors combine capabilities and participate in the resulting revenue.</em></figcaption></figure><h3>5. From a Supply Chain to an Infrastructure Economy</h3><p>A linear sequence of providers illustrates the mechanics, but a mature federation operates as a mesh. An AI application may depend on an inference platform, a model service, regional GPU capacity, storage and security capabilities from different organizations. Each participant may itself assemble Offerings from other providers. A single customer request, measured in transactions or tokens, can generate linked consumption events across compute, software, storage and operations.</p><p>The final customer need not manage these underlying relationships. The service provider can present one product while the contributing organizations retain their own technologies, policies and commercial agreements. The federation must preserve the connection between the customer-facing Offering, the underlying capabilities and the consumption attributable to each contributor. Commercial systems can then calculate entitlements, charges and payments using that information.</p><p>The same model applies within enterprises before external monetization becomes relevant. A manufacturing edge site can contribute locally processed data and compute to a centrally managed application. A central platform team can provide standardized software; a regional infrastructure team can supply compliant capacity; the business unit consumes the assembled service. Internal chargeback, allocation and capacity planning can benefit from the same attribution mechanisms used in external commercial relationships.</p><p>Existing cloud marketplaces, partner distribution programs and cross-provider GPU services demonstrate individual ingredients of this direction: aggregated supply, intermediary distribution and multi-party commercial relationships. Their existence does not establish an industry-wide federation. The strategic opportunity lies in combining those practices with persistent cross-boundary governance, reusable Offerings and dependable consumption attribution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/980/1*XXUzs_OtqiETLQ6YYfsJNQ.png" /><figcaption>Figure 5. <em>An ecosystem of independently supplied and reusable Offerings</em></figcaption></figure><h3>6. The Strategic Cost of Standing Still</h3><p>Organizations face three broad strategic choices as these operating and commercial models develop. The distinction is less about predicting a single market outcome than about deciding how much capability, learning and commercial reach to build today.</p><h4>The Architects: Shape the Economy</h4><p>Architects establish reusable Offerings, federation-ready operating controls, metering and partner relationships early. Infrastructure providers extend distribution beyond their direct sales channels; software vendors package validated technologies for multiple environments; service providers assemble new products without owning every component. Their investment creates the opportunity to influence how capabilities are defined, governed and exchanged.</p><h4>The Observers: Preserve Optionality</h4><p>Observers defer major commercial commitments while building the foundations for participation. They standardize infrastructure definitions, improve lifecycle automation, measure usage and test selected provider-consumer relationships. This protects flexibility and reduces the cost of entering later. Waiting without preparation, by contrast, can leave organizations with fragmented estates and fewer established partner relationships.</p><h4>The Defenders: Protect the Existing Model</h4><p>Defenders continue to prioritize directly owned, integrated and distributed infrastructure. Dedicated capacity remains appropriate where security, performance, sovereignty or predictable demand justify it. The competitive exposure arises when distribution and access to partner demand become as important as the quality of the underlying assets. Two providers with comparable GPU infrastructure may produce different returns if one can participate in many partner-delivered services while the other relies primarily on direct sales.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/980/1*Jeze2WllKipA4YCpcpOiuQ.png" /><figcaption>Figure 6. <em>Three strategic approaches to the emerging infrastructure economy.</em></figcaption></figure><p>These business implications extend across several dimensions:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*PYXY4Ni8nuKxUCihEQNN0w.png" /></figure><h4>A measured strategic choice</h4><p>The complete, interoperable, multi-party infrastructure economy described here is emerging rather than established. Adoption will differ by workload, industry and geography; interoperability, governance, security, commercial incentives and execution costs will determine where it succeeds. Organizations can nevertheless prepare without making an irreversible bet: identify reusable capabilities, establish consistent governance and consumption measures, and pilot federation where the operational or economic benefit is concrete.</p><h3>7. From Vision to Reality: Building the Foundation</h3><p>The foundation of federation is the ability to turn complex environments into dependable, governed Offerings. Quali’s Torque platform approaches this through reusable definitions, stack automation and lifecycle management across heterogeneous infrastructure. These capabilities provide the node-level consistency needed for a broader federated mesh: validated environments that can be delivered repeatedly, operated under policy and made consumable without reproducing integration work at every site.</p><p>At enterprise scale, the next step is to connect these governed capabilities across sites, edge locations, business units and partners. A federated operating layer can make locally controlled Offerings discoverable and consumable according to policy while maintaining capacity, identity, operational and usage context. The long-term economic opportunity emerges when that context supports multiple contributors and commercial relationships. The technical foundation and the commercial mechanisms are distinct, complementary layers.</p><p>The path can begin with a single high-value use case: sharing scarce GPUs between teams, delivering a validated AI stack across locations, making an edge capability available to central applications or extending an environment to a trusted partner. Each pilot should measure time to availability, utilization, avoided duplication, governance overhead and the quality of consumption attribution. Those results provide a factual basis for expansion.</p><p>Infrastructure will increasingly be judged by the value it can help deliver beyond its original owner. The organizations best positioned for that shift will be those able to make their capabilities reusable, governable and economically visible across a network of participants.</p><h3>Take the next step: Federated Infrastructure briefing and readiness assessment</h3><p>Quali offers a working session to identify where federation could create practical value in your infrastructure estate. Together, we can map candidate sites and edge environments, identify reusable infrastructure and software capabilities, review control-plane and governance requirements, and select an initial pilot with measurable operational and economic outcomes. Contact Quali to arrange a Federated Infrastructure briefing and readiness assessment.</p><p><a href="https://www.quali.com/contact-us/">Contact Us | Quali</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6ffddf06a11f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/quali-blogs/federated-infrastructure-the-new-economics-of-it-infrastructure-6ffddf06a11f">Federated Infrastructure: The New Economics of IT Infrastructure</a> was originally published in <a href="https://medium.com/quali-blogs">Quali Blogs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why CI Pipelines Are Not Infrastructure Automation]]></title>
            <link>https://medium.com/quali-blogs/why-ci-pipelines-are-not-infrastructure-automation-6d623ceda089?source=rss----b65ab89c8023---4</link>
            <guid isPermaLink="false">https://medium.com/p/6d623ceda089</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[infrastructure]]></category>
            <category><![CDATA[ci-cd-pipeline]]></category>
            <category><![CDATA[platform-engineering]]></category>
            <dc:creator><![CDATA[Edan Evantal]]></dc:creator>
            <pubDate>Wed, 30 Jul 2025 11:18:53 GMT</pubDate>
            <atom:updated>2025-07-30T11:16:57.672Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Reframing the Both-And Fallacy in Modern DevOps</strong></p><p>In today’s software delivery lifecycle, infrastructure automation is no longer a differentiator, it is foundational. But the tools and patterns many teams use to achieve it are misaligned with the operational and architectural realities of modern systems. Chief among these misalignments is the overextension of Continuous Integration (CI) tools as infrastructure automation platforms.</p><p>This misuse is not incidental; it reflects an outdated assumption that application delivery and infrastructure provisioning share the same execution model. They do not. CI pipelines were built to trigger stateless workflows. Infrastructure, in contrast, is deeply stateful, governed by lifecycles, security policies, and cost structures that cannot be abstracted away inside a YAML file.</p><p>Over the past several years, teams under pressure to deliver faster began embedding provisioning logic into CI pipelines, believing they were achieving platform engineering through reuse. Instead, they introduced a brittle, opaque, and often dangerous dependency model. What began as pragmatism has evolved into technical debt at scale.</p><p><strong>The False Promise of “Both-And” Thinking</strong></p><p>The “both-and” mindset, the idea that a single pipeline engine can serve both application and infrastructure delivery, seems efficient. In reality, it creates an illusion of unification while degrading control, visibility, and developer experience.</p><p>CI tools do not track the environments they create. They offer no sense of ownership, duration, or cost association. Infrastructure spun up this way often becomes orphaned, leading to rising cloud spend and unmanaged resource sprawl. Reusability suffers, as provisioning logic becomes hardcoded per team, per pipeline. Governance is circumvented, since CI systems lack the policy engines and RBAC needed to comply with security standards. And self-service stalls, because YAML does not scale as an interface for developers.</p><p><strong>A New Approach: Environment-as-a-Service (EaaS)</strong></p><p>The answer is not to discard CI/CD, but to decouple it from infrastructure orchestration. The modern solution is an <strong>Environment-as-a-Service (EaaS) control plane</strong>: a system that treats infrastructure environments as managed, governed, reusable, and auditable assets, not just side effects of pipeline execution.</p><p>An EaaS model introduces a fundamental shift. Instead of embedding infrastructure logic in delivery tools, it defines environments as modular blueprints stored in version control and exposed through controlled, policy-aware interfaces. These environments are provisioned and decommissioned dynamically, with full lifecycle visibility, user attribution, tagging, and cost tracking. All activity is logged. Access is managed through roles. Compliance is enforced automatically through Policy as Code.</p><p>This architecture supports, rather than subverts, CI/CD. CI pipelines can invoke environments declaratively without managing their lifecycle. Developers can request environments on demand via UI, CLI, or API, not through YAML edits or Slack requests. DevOps teams regain control without becoming bottlenecks. Finance and security teams gain insight into usage, drift, and exposure.</p><p>The Infrastructure deserves a first-class citizen in the delivery process, one that understands lifecycle, access, cost, and governance. That means:</p><ul><li><strong>Stateful environments</strong> with expiration, ownership, and cost tracking.</li><li><strong>Separation of concerns</strong> between app logic and environment automation.</li><li><strong>Self-service provisioning</strong> without compromising control or compliance.</li><li><strong>Policy as Code</strong>, not hardcoded scripts buried in CI jobs.</li></ul><p>The diagram below illustrates the depth and breadth of capability enabled by EaaS when infrastructure is treated as a product, not a process:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/817/1*cfweypWqTl2zBLrA9zFPgg.png" /><figcaption>Environment-as-a-Service (EaaS)</figcaption></figure><p>On the left are the outcomes organizations demand reproducibility, governance, self-service, scalability. On the right are the operational pillars required to deliver them: drift detection, access policies, day-2 workflows, and cost control, all natively supported and integrated. At the center is the abstraction of infrastructure through version-controlled assets, orchestrated through automation and surfaced through GitOps. This is not an incremental improvement, it is a categorical upgrade.</p><p><strong>The Transition Is Not Optional</strong></p><p>Infrastructure complexity is accelerating, not declining. Multi-cloud, AI/ML workloads, ephemeral environments, and platform engineering mandates all require a more robust, intent-driven model of automation. CI pipelines are critical, but they cannot be asked to solve a problem they were never designed to address.</p><p>Organizations that continue to extend CI tools into infrastructure domains will pay for it in outages, cost overruns, compliance failures, and developer attrition. Those that adopt a true control plane for infrastructure, with governance, reusability, and self-service at the core will move faster, with greater consistency and lower risk.</p><p>The era of misusing CI as an infrastructure engine is over. What replaces it is not a toolchain, but a new operational layer: <strong>Environment-as-a-Service</strong> (EaaS).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d623ceda089" width="1" height="1" alt=""><hr><p><a href="https://medium.com/quali-blogs/why-ci-pipelines-are-not-infrastructure-automation-6d623ceda089">Why CI Pipelines Are Not Infrastructure Automation</a> was originally published in <a href="https://medium.com/quali-blogs">Quali Blogs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Cloud Chaos to Full Control: The Journey to Managed Environments with Torque]]></title>
            <link>https://medium.com/quali-blogs/from-cloud-chaos-to-full-control-the-journey-to-managed-environments-with-torque-13650735065b?source=rss----b65ab89c8023---4</link>
            <guid isPermaLink="false">https://medium.com/p/13650735065b</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[infrastructure-as-code]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[David Williams]]></dc:creator>
            <pubDate>Tue, 04 Feb 2025 13:23:58 GMT</pubDate>
            <atom:updated>2025-02-04T13:23:58.350Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/443/1*zjSbxhyeyXN53QcJoj2eHw.jpeg" /></figure><p>Cloud adoption was about getting things done. When AWS, Azure, and GCP made infrastructure instantly available, teams jumped at the opportunity to move fast, test ideas, and deploy without waiting on procurement or approvals. Cloud could be used at a very low cost of entry. While this helped with adoption, it created poor behaviors where cloud usage was poorly managed. However, engineers just wanted <strong>environments on demand</strong> without roadblocks, creating a cloud where innovation and the value it delivered pushed increasing issues of cloud waste to the side.</p><p>So instances spun up in seconds. Databases were provisioned on a whim. Entire Kubernetes clusters were created in the time it took to grab a coffee. <strong>Speed won.</strong> But something else happened too.</p><ul><li><strong>No one knew what was running — or why.</strong></li><li><strong>Orphaned resources accumulated, quietly racking up costs.</strong></li><li><strong>Security policies became an afterthought, only noticed when something went wrong.</strong></li></ul><p>What started as an advantage <strong>became a liability</strong>. Click-ops, the practice of manually provisioning resources through cloud consoles, led to an operational Wild West: <strong>zero standardization, zero visibility, and unpredictable spend</strong>.</p><p>And yet, organizations didn’t stop because the alternative, forcing teams through complex approval processes or cumbersome Cloud Management Platforms (CMPs), felt worse.</p><p>But this lack of governance came at a price:</p><ul><li><strong>Cloud Waste &amp; Rising Costs</strong>: Gartner reports that <strong>30% of cloud spend is wasted</strong> due to unused and over-provisioned resources (s<em>ource: Gartner Cloud Strategy Research</em>).</li><li><strong>Security &amp; Compliance Risks</strong>: According to IBM’s Cost of a Data Breach report, misconfigured cloud environments are among the <strong>top causes of security breaches</strong>, costing companies an average of <strong>$4.45 million per incident.</strong></li></ul><p>But what if there was a way to keep cloud agility while eliminating the chaos and still allow developers access to self-service environments without governance nightmares?</p><p>That’s where <strong>managed cloud environments</strong> come in. And that’s where Quali Torque starts.</p><h3>Cloud Management Maturity Model: From Click-Ops to Full Control</h3><h4>The Journey from Click-Ops to Full Cloud Control</h4><p>As organizations scale their cloud operations, they often begin in a state of cloud chaos<strong>,</strong> where unmanaged resources, rising costs, and security risks dominate<strong>. </strong>The path to<strong> </strong>optimized, governed cloud environments<strong> </strong>requires gradual adoption of automation, visibility, and policy enforcement<strong>.</strong></p><p>However, achieving full control over cloud environments is nearly impossible without intelligence<strong>. </strong>AI-driven automation<strong> </strong>plays a critical role in identifying waste, enforcing security policies, and dynamically optimizing environments — helping organizations progress faster through the cloud maturity model<strong>.</strong></p><p>The diagram below illustrates the step-by-step transformation from an ad-hoc, manual cloud approach (Click-Ops) to a fully managed, intelligent, and cost-optimized environment<strong>.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4Lvrh9wa36UnCkuTCwD8QA.png" /><figcaption>Cloud Management Maturity Model: From Click-Ops to Full Control</figcaption></figure><h3><strong>Step 1: Recognizing the Problem — Click-Ops Chaos (~10% Managed Resources</strong>)</h3><p>At less than 10% managed resources, cloud environments are in a state of uncontrolled sprawl. Engineers create cloud instances, databases, and Kubernetes clusters manually with no central governance. Over time, this results in:</p><ul><li><strong>Cloud cost overruns</strong> — Unused resources keep running, burning budget.</li><li><strong>Security risks </strong>— Lack of visibility leads to shadow IT and policy violations.</li><li><strong>Operational</strong> inefficiencies — Teams spend more time firefighting than innovating.</li></ul><h4>Torque provides the first critical step: V<strong>isibility.</strong></h4><p>Torque simplifies this process, transforming manually created resources into declarative templates that can be version-controlled and replicated with consistency. Torque can also connect to the organization’s Git repositories to discover existing IaC assets. These assets are mapped to the discovered cloud resources, helping in constructing healthy automation practices while shortening the adoption process and making it more efficient.</p><p>By automatically discovering and cataloging cloud resources, Torque maps out the sprawl, uncovering:</p><ul><li><strong>Orphaned resources</strong> driving unnecessary costs.</li><li><strong>Unused infrastructure</strong> left running due to lack of tracking.</li><li><strong>Security gaps</strong> caused by unmonitored, ad-hoc provisioning<strong>.</strong></li></ul><p>This single source of truth becomes the foundation for a more structured approach allowing organizations to start moving towards managed environments, ensuring resources are provisioned in a repeatable, scalable, and auditable manner. This shift begins to reduce cloud waste and empowers teams to take their first steps toward governance and compliance.</p><h3>Step 2: Curation — The First Step Toward Management (~50% Managed Resources)</h3><p>With visibility achieved<strong>,</strong> the next phase is Curation, bringing order to cloud resources by codifying them into Infrastructure as Code (IaC) using tools like HashiCorp Terraform<strong>, </strong>OpenTofu<strong> </strong>and Kubernetes manifests.</p><p>But even with IaC, challenges remain:</p><ul><li><strong>Legacy Cloud Resources</strong> — How do you manage resources that were manually created in the past?</li><li><strong>IaC Adoption Complexity</strong> — Writing Terraform from scratch is time-consuming and requires expertise.</li><li><strong>Integration with DevOps &amp; CI/CD </strong>— Infrastructure needs to align with application deployment pipelines.</li></ul><h4>Torque provides the first critical step: Curate</h4><ul><li><strong>Auto-discovering</strong> existing cloud resources and converting them into Terraform or OpenTofu.</li><li><strong>Mapping discovered resource</strong>s to Git repositories, accelerating IaC adoption.</li><li><strong>AI-Powered reusable Blueprinting</strong>, ensuring standardized, repeatable deployments.</li></ul><p>As more resources are codified and managed through Torque, the benefits become clear. Torque’s managed environments introduce features such as <strong>automated tagging</strong>, <strong>drift detection</strong>, <strong>impact mapping</strong> and <strong>update management</strong>, helping organizations track resource ownership, prevent configuration drift, and apply updates seamlessly.This shift from manual provisioning to declarative automation<strong> </strong>ensures<strong> </strong>repeatability, security, and efficiency<strong>.</strong></p><p>At this stage, businesses experience significant <strong>productivity gains</strong>, as developers focus on innovation instead of firefighting infrastructure sprawl. Additionally, Torque enables proactive cost-saving measures, such as detecting idle resources and automating shutdown schedules.By adopting this approach, organizations <strong>reduce cloud waste, improve governance,</strong> and move toward <strong>self-service</strong>, where developers deploy within well-defined guardrails instead of anarchy.</p><h3><strong>Step 3: Governed — Enforcing Policies &amp; Day-2 Operations (~75% Managed Resources)</strong></h3><p>With the majority of resources now under control, organizations enter a new phase of operational maturity — managed<strong>.</strong> At this stage, the focus shifts to:</p><ul><li><strong>Proactive cost optimization</strong> — Detecting idle resources, applying cost controls.</li><li><strong>Automated governance</strong> — Enforcing policies through Policy-as-Code<strong>.</strong></li><li><strong>Drift detection &amp; compliance</strong> — Ensuring infrastructure remains in sync with business needs<strong>.</strong></li></ul><p>Torque’s governance capabilities ensure that every deployed resource aligns with business objectives. Built-in guardrails prevent unauthorized changes, while real-time monitoring offers insights into usage patterns, further optimizing costs and performance.</p><h4>Torque provides the first critical step: Governance</h4><ul><li><strong>Real-time monitoring</strong> of cloud costs, usage, and trends.</li><li><strong>Enforcement of tagging policies</strong> to track ownership and purpose.</li><li><strong>Automated shutdown schedules</strong> for non-production environments.</li></ul><p>At this point, cloud complexity decreases<strong>, </strong>security improves<strong>,</strong> and developers spend less time managing infrastructure and more time building applications<strong>.</strong></p><p>Teams are now working in an environment that is largely automated, secure, and efficient. Manual interventions decrease, reducing operational overhead and allowing IT teams to focus on strategic initiatives rather than cloud resource wrangling.</p><h3>Step 4: Managed — End-to-End Control &amp; Cloud Maturity (~100% Managed Resources)</h3><p>At this stage, organizations operate in a fully managed cloud environment<strong>.</strong></p><p>Reaching the pinnacle of cloud maturity, organizations operate in a fully managed environment within Torque. While achieving exactly 100% managed resources may not always be feasible, Torque provides ongoing support to get as close as possible by continuously discovering and managing new resources. Every cloud resource that is codified ensures <strong>traceability, compliance, and security</strong>. Governance policies are consistently applied, and the risk of cloud sprawl is significantly reduced.</p><p>While reaching exactly 100% managed resources may not always be feasible, Torque ensures that as new cloud resources are created, they are automatically discovered, codified, and governed<strong>.</strong></p><ul><li><strong>No more cloud sprawl.</strong></li><li><strong>No more runaway costs.</strong></li><li><strong>No more guesswork.</strong></li></ul><p>Every deployed resource is fully traceable<strong>, </strong>compliant<strong>,</strong> and secure<strong>.</strong></p><p>Torque provides continuous lifecycle management<strong>,</strong> meaning:</p><ul><li>Automatic application of governance policies<strong>.</strong></li><li>Consistent IaC enforcement across all cloud environments<strong>.</strong></li><li>Proactive cost savings<strong>,</strong> eliminating unused or misconfigured resources.</li></ul><p>At this point, the organization experiences:</p><ul><li><strong>Maximum cost savings</strong> — Eliminating cloud waste and ensuring cost-efficient operations.</li><li><strong>Peak developer productivity</strong> — Teams self-service cloud environments without compliance concerns.</li><li><strong>Cloud peace of mind</strong> — No surprises, no hidden costs, just efficient, automated infrastructure<strong>.</strong></li></ul><p>At this stage, the organization enjoys maximum <strong>cost savings</strong>, having eliminated waste and optimized resource utilization. Productivity reaches new heights, as teams operate with full confidence in their cloud environments. However, the journey doesn’t end here, new resources will always be created, and Torque helps maintain control as cloud environments evolve.</p><p>However, cloud environments are always evolving<strong> </strong>and Torque ensures that even as new infrastructure is created, it remains controlled, compliant, and optimized<strong>.</strong></p><h3>The Value of the Journey</h3><p>Throughout this transformation, Torque empowers organizations to:</p><ul><li><strong>Eliminate cloud waste</strong> and automate cost controls<strong>,</strong> ensuring efficient resource utilization.</li><li><strong>Move from chaos to standardized cloud operations</strong>, enhancing governance and security.</li><li><strong>Boost productivity</strong>, enabling teams to focus on innovation rather than infrastructure maintenance<strong>.</strong></li></ul><h3>Conclusion</h3><p>The journey from unmanaged cloud sprawl to fully governed environments is one of transformation and growth.</p><p>With Torque, organizations navigate this path with confidence, leveraging automation,<strong> </strong>governance, and self-service<strong> </strong>to build a more efficient, cost-effective, and secure cloud strategy<strong>.</strong></p><p>By embracing a managed approach<strong>,</strong> they gain not only financial benefits but also the peace of mind that their cloud infrastructure is future-ready<strong>.</strong></p><p>The question isn’t whether to manage cloud resources — it’s how fast you can get there.</p><p>If you would like to see an example of how Quali Torque is changing how infrastructure is managed please visit <a href="http://www.quali.com/">www.quali.com</a> or watch the <a href="https://www.quali.com/cloud-curate/">Quali Torque video</a> to fully understand what a modern AI infrastructure automation platform delivers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=13650735065b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/quali-blogs/from-cloud-chaos-to-full-control-the-journey-to-managed-environments-with-torque-13650735065b">From Cloud Chaos to Full Control: The Journey to Managed Environments with Torque</a> was originally published in <a href="https://medium.com/quali-blogs">Quali Blogs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Infrastructure as Code Meets Continuous Integration: Simplifying the Inner and Outer Loop]]></title>
            <link>https://medium.com/quali-blogs/infrastructure-as-code-meets-continuous-integration-simplifying-the-inner-and-outer-loop-ed71db7cb916?source=rss----b65ab89c8023---4</link>
            <guid isPermaLink="false">https://medium.com/p/ed71db7cb916</guid>
            <category><![CDATA[platform-engineering]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[automation]]></category>
            <dc:creator><![CDATA[Edan Evantal]]></dc:creator>
            <pubDate>Mon, 02 Dec 2024 11:14:51 GMT</pubDate>
            <atom:updated>2024-12-02T11:14:51.887Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Infrastructure Complexity: A Hidden Bottleneck for Innovation</strong><br>Managing infrastructure has become more critical and complex, requiring more skills and time. DevOps teams are often pulled between two key phases: the inner loop and the outer loop of infrastructure development. Yet, without proper automation and tools, managing both loops effectively becomes a challenge, especially when Infrastructure as Code (IaC) is layered in. Misaligned configurations, inefficient workflows, and manual processes often lead to bottlenecks, slowing down deployments and frustrating developers.</p><p>According to <strong>McKinsey</strong>, the inner loop should be the focus of development activities because it drives value through coding, testing, and building infrastructure. On the other hand, the outer loop — deployment, integration, and testing — should be streamlined with automation to reduce developer interruptions and inefficiencies (<a href="https://www.mckinsey.com/industries/technology-media-and-telecommunications/our-insights/yes-you-can-measure-software-developer-productivity">McKinsey &amp; Company</a>).</p><p><strong>Enter Torque: Simplifying Infrastructure with IaC and CI</strong><br>Infrastructure as Code (IaC) and Continuous Integration (CI) have become essential for modern infrastructure management, allowing teams to provision cloud environments automatically and consistently. However, many organizations still struggle to align their infrastructure with development needs efficiently. <strong>The New Stack</strong> emphasizes how IaC addresses inconsistent deployments and helps manage infrastructure complexity (<a href="https://thenewstack.io/why-infrastructure-as-code-is-vital-for-modern-devops/">The New Stack</a>).</p><p>Torque solves this challenge by acting as a unified platform that integrates both loops of the infrastructure lifecycle, accelerating workflows and making infrastructure scalable, reliable, and easy to manage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/561/1*OOtyG17e8BX-xoYwmaSGVw.png" /><figcaption>Figure 1: Infrastructure Updates — Feature Branches</figcaption></figure><p><strong>The Inner Loop: What It Is and Why It Matters</strong><br>The inner loop refers to the iterative, fast-paced process where developers work on local environments to build, test, and validate their code. For infrastructure, this means platform teams and DevOps engineers work on IaC definitions locally, ensuring they are correct before committing to a shared repository. <strong>McKinsey </strong>outlines how organizations should aim to have developers spend most of their time in the inner loop, coding and testing, rather than being bogged down by outer-loop tasks like managing infrastructure (<a href="https://www.mckinsey.com/industries/technology-media-and-telecommunications/our-insights/yes-you-can-measure-software-developer-productivity">McKinsey &amp; Company</a>).The goal is to identify and fix issues early, avoiding costly mistakes down the line.</p><p><strong>Key elements of the inner loop include:</strong><br><strong>1. Local Development and Testing: </strong>DevOps teams use tools like Terraform or Pulumi to develop infrastructure code locally, ensuring that configurations work as intended.<br><strong>2. Unit Testing: </strong>Just as developers test their code, infrastructure definitions need tests. Tools like Terratest allow engineers to validate that their IaC works as expected in small, isolated scenarios.<br><strong>3. Linting and Static Analysis: </strong>By implementing linting and static analysis tools, teams can catch configuration issues or coding standard violations before pushing code further along the pipeline.<br><strong>4. Local Validation: </strong>Infrastructure configurations are tested and validated locally to avoid introducing errors that could compromise deployment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TfQDhdI2BgWxVUpLhBGf2w.png" /><figcaption>Figure 2. Updating an IaC Asset — Updating the Development Environment</figcaption></figure><p><strong>How Torque Elevates the Inner Loop: </strong>Torque automates and simplifies the inner loop by enabling teams to easily create reusable infrastructure blueprints. With Torque, developers and DevOps engineers can spin up environments on-demand for local testing, ensuring that they work exactly as expected. This removes the friction that often comes with setting up and managing environments manually, streamlining development, and increasing productivity.</p><p><strong>The Outer Loop: From Code Commit to Production </strong>The outer loop takes over once code leaves the local environment and is committed to a shared repository. Here, the focus shifts from development to testing, deploying, and managing infrastructure in a real-world, shared environment. This stage includes CI/CD pipelines, code reviews, and automated testing, ensuring that any infrastructure changes are seamlessly integrated and deployed without disrupting production.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/654/1*wexO-ja_g9ksE074brD36A.png" /><figcaption>Figure 3. Updating the Staging Environment</figcaption></figure><p><strong>Key components of the outer loop include:</strong><br><strong>1. Pull Requests (PRs): </strong>Opening a PR triggers a process of code review, automated testing, and collaboration, ensuring that infrastructure changes meet best practices and pass all required tests.<br><strong>2. Continuous Integration (CI): </strong>As PRs are created, CI tools like Jenkins, GitHub Actions, or CircleCI run automated tests, including syntax checks, integration tests, and security scans, ensuring that infrastructure is validated at every step.<br><strong>3. Continuous Deployment (CD): </strong>Once infrastructure changes are tested, they are deployed to staging environments for final validation. CD pipelines automate the process, running end-to-end tests and ensuring infrastructure is production-ready.<br><strong>4. Monitoring and Feedback: </strong>After deployment, monitoring tools help track the performance of the infrastructure, providing feedback to developers and enabling quick rollbacks if issues arise.</p><p><strong>Torque’s Role in the Outer Loop: </strong>Torque acts as the bridge between the inner and outer loops by integrating seamlessly with CI/CD pipelines. It ensures that the same IaC blueprints used during development are applied consistently across environments, eliminating the risk of misconfigurations. Torque also enhances governance by providing visibility and control over infrastructure changes, allowing teams to roll out updates faster without sacrificing stability or security.</p><p><strong>Bridging the Divide Between Inner and Outer Loops with IaC and Torque</strong><br>The divide between the inner and outer loops can often lead to friction in infrastructure workflows. On one hand, developers need fast, flexible environments to build and test their code. On the other, operations teams need to enforce strict policies to ensure stability and security in production. This is where IaC shines, allowing infrastructure to be treated like any other piece of code, but the challenge lies in aligning both loops under one unified process.</p><p>Torque bridges this gap by providing <strong>governed self-service</strong> capabilities, enabling developers to access pre-approved environments that meet the necessary security and compliance standards. This removes bottlenecks by allowing developers to focus on their work without waiting for manual approvals or dealing with complex configurations.</p><p><strong>Real-World Impact: Torque in Action</strong><br>A large financial institution recently used Torque to streamline its infrastructure management by integrating both the inner and outer loops into a single, cohesive workflow. The organization saw a dramatic reduction in deployment times and an increase in developer productivity, as engineers could quickly provision environments while maintaining strict governance controls. This unified approach eliminated configuration drift and reduced errors, enabling faster rollouts and improved collaboration across teams.</p><p><strong>Why Torque is Essential for Modern IaC and CI Workflows</strong><br>Managing infrastructure across both inner and outer loops can be a daunting task, but with the right tools, it becomes a streamlined process. Torque eliminates the complexity of managing infrastructure at every stage of the development lifecycle, ensuring that environments are consistent, compliant, and easy to deploy. By simplifying IaC workflows and bridging the gap between development and production, Torque delivers real value, making infrastructure a powerful enabler of innovation rather than a bottleneck.</p><p><strong>Ready to see the impact for yourself?</strong> Try out, without any obligation, the Quali Torque Playground and experience first-hand Torque will transform your software delivery process. Visit <a href="http://www.quali.com/">www.quali.com</a> for more information or contact us to discuss how Torque can change the way your teams can accelerate delivery, reduce costs, and simplify infrastructure management.</p><p>Content Referenced in the blog: <br>• <strong>McKinsey on Inner/Outer Loop and Developer Productivity: </strong>McKinsey on Developer Productivity (<a href="https://www.mckinsey.com/industries/technology-media-and-telecommunications/our-insights/yes-you-can-measure-software-developer-productivity">McKinsey &amp; Company</a>).<br>• <strong>The New Stack on Infrastructure as Code in DevOps:</strong> <a href="https://www.thenewstack.io/why-infrastructure-as-code-is-vital-for-modern-devops/">Why Infrastructure as Code Is Vital for Modern DevOps</a> (<a href="https://thenewstack.io/why-infrastructure-as-code-is-vital-for-modern-devops/">The New Stack</a>).<br>• McKinsey on DevOps and IT Infrastructure Agility: <a href="https://www.mckinsey.com/capabilities/mckinsey-digital/our-insights/digital-blog/devops-the-key-to-it-infrastructure-agility">DevOps and IT Infrastructure Agility</a> (<a href="https://www.mckinsey.com/capabilities/mckinsey-digital/our-insights/digital-blog/devops-the-key-to-it-infrastructure-agility">McKinsey &amp; Company</a>).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed71db7cb916" width="1" height="1" alt=""><hr><p><a href="https://medium.com/quali-blogs/infrastructure-as-code-meets-continuous-integration-simplifying-the-inner-and-outer-loop-ed71db7cb916">Infrastructure as Code Meets Continuous Integration: Simplifying the Inner and Outer Loop</a> was originally published in <a href="https://medium.com/quali-blogs">Quali Blogs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>