SAN MATEO, Calif.–(BUSINESS WIRE)–Armory, the open source continuous delivery software company, announced significant growth of its easy-to-use Spinnaker deployments, as the overall user community grew, evidenced in part by the 100% increase in attendees at the upcoming Spinnaker Summit. Spinnaker is the open source, multi-cloud continuous delivery (CD) platform for releasing software changes with high velocity and confidence.

Armory will participate at Spinnaker Summit June 22-24 with a number of sessions discussing the value of making Spinnaker more accessible and easier to use. Armory will take part in a keynote panel session moderated by Kelsey Hightower called A Deep Dive into the Benefits of CD. The Birds of a Feather session titled Continuous Delivery: Spinnaker at Scale includes speakers from Armory, Autodesk, AWS, Cox Automotive, Netflix, and Salesforce.

“Everything we do revolves around making Spinnaker more accessible and easier to use so that engineering teams are able to ship better code faster,” said Daniel R. Odio, co-founder and CEO, Armory. “And that’s achieved by working closely with partners like AWS and customers like Autodesk, who are leading the way by empowering developers and delivering code as efficiently as possible.”

Armory Frees Engineers to Focus on Delivering Value

One way Armory is making Spinnaker more accessible is through its Managed Services Offering, providing expert engineers to manage Spinnaker installations with 24/7 support and guaranteed 99.95% uptime—including break-fix, debugging and troubleshooting. Not only does this offering remove the management overhead of Spinnaker, customers typically see at least a three-times cost savings over hiring an internal team to install, configure, manage and provide 24/7 support of Spinnaker.

“Armory Managed Services eases our life with their expertise—from installation to service management—allowing us to focus on building CI/CD pipelines rather than troubleshooting Spinnaker,” said Leon Xiao, site reliability engineering manager, eHealth.

Scale Spinnaker Deployments to Kubernetes

Armory’s Agent for Kubernetes is a lightweight, scalable service that monitors each Kubernetes cluster and streams changes back to Spinnaker’s Clouddriver service, solving the following problems:

Latency issues that arise when caching large Kubernetes resources in Spinnaker;
Security and access issues that exist when Kubernetes clusters are managed by a central resource;
Bottleneck issues that surface when new Kubernetes clusters require onboarding by a central resource; and
Complexity issues stemming from supporting thousands of Kubernetes clusters that have tens of thousands of objects and multiple edge cases.
Armory and AWS Extend Use of Spinnaker

In collaboration with AWS, Armory recently added blue/green and canary support into Lambda deployments within Spinnaker. Learn more about the Lambda integration and Autodesk’s success with Armory and AWS here.

Armory will also soon be releasing an AWS Quick Start to make it simple to deploy a production-grade instance of Armory on AWS EKS. To learn more, AWS has a workshop scheduled on June 24 about continuous deployment for cloud-native applications that includes hands-on labs from Armory and others.

Simplified Spinnaker Installation

Armory Minnaker is a virtual machine leveraging K3s and the Armory Operator to enable software deployments in 10 minutes instead of 10 days. Armory Minnaker is a full Spinnaker installation packaged inside a virtual machine running the certified K3s Kubernetes distribution. Minnaker automatically handles authentication, security such as SSL/TLS, namespaces, custom resources in Kubernetes (CRD) and more.

Additionally, Armory has created pre-built DevOps pipelines, along with a self-guided tour of the platform to acquaint new users. All of this enables integration of Armory into DevOps toolchains, such as continuous integration (CI) systems, Git repositories, security tools, and targets for software distribution.

Spinnaker

Spinnaker is an open source, multi-cloud continuous delivery platform for releasing software changes with high velocity and confidence. Created at Netflix, it has been battle-tested in production by hundreds of teams over millions of deployments. It combines a powerful and flexible pipeline management system with integrations to the major cloud providers. Learn more at www.spinnaker.io.

Armory

Armory is the company driving modern digital transformation with its enterprise version of Spinnaker. Armory’s scalable, flexible, and secure platform automates software delivery, enabling software teams to ship better software, faster. The core of Armory’s platform is powered by Spinnaker, the continuous delivery platform developed and open-sourced by Netflix and Google to help companies quickly and safely deploy software into multiple clouds. Armory builds on open-source Spinnaker’s foundation, adding proprietary features for bolstered enterprise scale, along with 24×7 enterprise-grade support. Armory’s platform is trusted by dozens of Global 2000 customers in financial services, technology, retail, healthcare and entertainment. Armory is also a proud sponsor of, and contributor to, the Continuous Delivery Foundation (CDF), the vendor-neutral home of the fastest-growing projects for continuous delivery.

What Is a Spinnaker Pole?

A spinnaker pole is a spar used on sailing vessels to extend the foot of a spinnaker sail away from the mast, allowing the sail to fill with wind on downwind or reaching points of sail. Unlike a boom, which is attached to the mast and the foot of the mainsail, a spinnaker pole is typically clipped to the mast at one end and to the spinnaker’s tack at the other, and it is removed and stowed when not in use. The pole must be strong enough to handle significant compressive and lateral loads while remaining as light as possible to minimise the effect on the vessel’s centre of gravity.

Material Types: Composite vs. Metal

Spinnaker poles are broadly manufactured in two material categories:

Composite Poles

Carbon fibre and fibreglass composite poles have become the dominant choice in performance and racing applications. Carbon fibre poles offer an exceptional strength-to-weight ratio, allowing sailors to carry longer poles without the associated weight penalty. The reduction in polar moment of inertia at the bow of the boat can make a meaningful difference in light-air performance and boat handling. Composite poles are also more resistant to corrosion in salt water environments, reducing long-term maintenance demands.

Metal Poles

Aluminium alloy poles remain widely used in cruising and club-racing contexts where cost, repairability, and durability take priority over minimum weight. Aluminium is easier to machine and repair than carbon fibre, fittings can be replaced or modified in the field, and the material is less susceptible to catastrophic failure from impact. For amateur leisure sailors or budget-conscious club racers, an aluminium pole represents a practical and affordable solution.

Application Segments

The market is generally divided into two end-use segments:

• Professional Sports: Offshore racing classes, grand prix inshore racing, and fully crewed ocean races such as the Rolex Fastnet Race or Jules Verne Trophy campaigns demand the highest-specification poles. Budgets in this segment are less constrained, and teams routinely commission custom-built poles engineered to specific class rules and structural load calculations.
• Amateur Leisure: Club racers, cruiser-racers, and coastal cruising sailors make up the larger volume segment by unit count. Price sensitivity is higher, replacement cycles are longer, and the emphasis is on reliability and ease of use over marginal weight savings.

Key Manufacturers in the Spinnaker Pole Industry

The following companies were identified in the original market research teaser as notable participants in the global spinnaker pole market. Brief descriptions are based on publicly available information about each manufacturer’s positioning; no claims about market share or revenue are made.

• AG+ Spars: A specialist spar manufacturer known for carbon fibre masts and poles for racing yachts.
• Allen Brothers: A UK-based marine hardware and rigging company supplying components and poles across cruising and racing markets.
• Axxon Composites: A composite spar builder focused on high-performance racing applications.
• Competition Composites Inc. (CCI): A Canadian manufacturer of carbon fibre spars with a long history supplying offshore and grand prix racing teams.
• CST Composites: An Australian composite manufacturer producing carbon tubes and spars for the marine industry.
• Forespar: A US-based company well known for aluminium and carbon spinnaker poles as well as associated hardware, popular in the cruising market.
• Hall Spars & Rigging: A high-end spar builder with a strong presence in grand prix racing and superyachts.
• Heol Composites: A French composite manufacturer supplying performance sailing hardware and spars.
• Offshore Spars: A specialist in offshore racing spar solutions.
• Optiparts – Windesign: A Dutch company primarily known for dinghy and one-design class equipment, supplying poles for smaller racing classes.

Regional Dynamics

Demand for spinnaker poles is closely correlated with sailing participation rates and the density of racing and cruising fleets. The following regions represent the primary markets:

• United States: A large base of cruiser-racers and a well-established offshore racing scene support consistent demand across both composite and aluminium poles.
• Europe: Home to some of the most competitive offshore racing fleets in the world, including the IRC Grand Prix circuit and the IRC offshore championships. European markets — particularly the UK, France, Germany, and the Netherlands — are strong consumers of high-specification composite poles.
• China and Southeast Asia: Growing sailing participation and an expanding recreational boating sector represent longer-term growth opportunities, though the market remains at an earlier stage of development compared to Western Europe and North America.
• Japan: A mature sailing market with established racing circuits and a preference for quality marine hardware.
• India and Central & South America: Emerging markets where coastal recreational sailing is growing, though these regions currently represent a smaller share of total spinnaker pole demand.

Factors Influencing the Market

Several structural factors shape the competitive landscape and purchasing decisions in the spinnaker pole market:

• Class rules: Many racing classes prescribe pole length, diameter, or material constraints, which directly limits the specification manufacturers can target for those fleets.
• Carbon fibre supply chain: The cost of aerospace-grade carbon fibre prepreg and raw tube stock has a direct impact on composite pole pricing, making the segment sensitive to broader aerospace and materials market conditions.
• Advances in resin systems: Improvements in epoxy and toughened resin systems continue to improve the impact resistance and fatigue life of composite poles.
• Self-tacking and furling sail systems: On some modern cruising designs, asymmetric spinnakers launched from a bowsprit are replacing traditional symmetric spinnakers entirely, reducing demand for conventional poles on new builds.

Summary

The spinnaker pole market is a specialised segment of the broader marine hardware and rigging industry. It is characterised by a clear division between composite products targeting performance racing applications and aluminium products serving the larger cruising and club-racing base. Manufacturers range from specialist composite spar builders serving grand prix racing to broad-line marine hardware companies whose pole ranges form part of a wider cruising hardware catalogue. Demand is geographically concentrated in established sailing markets in North America and Western Europe, with emerging growth in Asia-Pacific.

For specific market sizing, forecast data, or competitive share analysis, consult a specialist marine industry research provider directly.

Spinnaker Trust Increases McDonald’s (MCD) Stake by 25.31%

Spinnaker Trust added to its position in McDonald’s Corporation (NYSE: MCD) during Q1 2019, purchasing 3,358 additional shares — a 25.31% increase over the prior quarter. According to its 13F regulatory filing with the SEC, the firm held 16,626 shares of MCD at the end of Q1 2019, valued at approximately $3.16 million, up from 13,268 shares the previous quarter.

The increased position signals continued bullish sentiment from Spinnaker Trust toward the fast-food giant. At the time of the filing, McDonald’s carried a market capitalization of approximately $163 billion. The stock had risen roughly 8.52% during the quarter and was up approximately 32.83% on a year-over-year basis from August 25, 2018, outperforming the S&P 500 over that same period.

In the most recent trading session referenced in the source data, MCD shares declined 2.20% (–$4.83), closing at $214.66, with approximately 3.66 million shares traded — roughly 23.39% above its average daily volume.

Notable McDonald’s Headlines (2018)

• McDonald’s announced plans to cut greenhouse gas emissions from its restaurants and offices by 36% (March 2018).
• The company reported that fresh beef advertising lifted sales across its full burger lineup.
• Breakfast was cited as representing 25–30% of daily sales and the most profitable daypart.
• McDonald’s committed to replacing plastic straws with paper straws across all UK locations starting May 2018.
• Comparable sales growth was reported in April 2018 results.

Spinnaker Trust Portfolio Context

Spinnaker Trust manages approximately $994.89 million in US long positions. Alongside its increased MCD stake, the firm made several reductions during Q1 2019:

• Healthcare Select Sector SPDR (XLV): Reduced by 34,310 shares to 359,919 shares, valued at approximately $33.02 million.
• Financial Select Sector SPDR (XLF): Cut by 75,696 shares, leaving a holding of approximately 1.06 million shares.
• Vanguard FTSE Developed Markets ETF (VEA): Stake reduced (specific share count not disclosed in source).

Night Owl Capital Management Trims Visa (V) Position by 5.54%

Night Owl Capital Management LLC reduced its exposure to Visa Inc. (NYSE: V) in Q1 2019, selling 11,888 shares — a 5.54% reduction. The hedge fund held 202,848 shares of Visa at the end of Q1 2019, valued at approximately $31.68 million, down from 214,736 shares in the prior reported quarter.

Despite the reduction, Visa’s stock rose 9.34% during the quarter. At the time of the source data, Visa held a market capitalization of approximately $392.59 billion. On the most recent trading session referenced, V shares fell 2.70% (–$4.86) to $175.23, with approximately 7.05 million shares traded — about 0.98% above average daily volume. Visa had gained approximately 30.42% year-over-year from August 25, 2018, outpacing the S&P 500 over that period.

Broad Institutional Sentiment on Visa in Q1 2019

Overall investor sentiment toward Visa edged slightly higher in Q1 2019. The aggregate sentiment score rose to 1.05, up from 1.00 in Q4 2018. While 49 investors exited Visa shares entirely and 631 reduced their holdings, 164 funds opened new positions and 551 raised their existing stakes. The total institutional share count fell to approximately 1.54 billion shares — down 4.83% from 1.62 billion in Q4 2018.

Selected institutional holders as of Q1 2019 included:

• Wellington Management Group LLP: Approximately 17.78 million shares
• First Republic Investment Management: Approximately 1.09 million shares (0.89% of portfolio)
• Bryn Mawr Trust: Approximately 134,958 shares (1.15% of portfolio)
• Jackson Square Partners LLC: 3.23% of portfolio in Visa
• Vision Capital Management: 2.28% of portfolio in Visa
• Mackenzie Financial Corporation: 0.88% of portfolio in Visa
• Sumitomo Life Insurance: Approximately 66,330 shares
• Brown Advisory Securities LLC: 2.16% of portfolio (58,822 shares)
• Carnegie Capital Asset Management: 0.83% of portfolio
• UMB Bank N.A. (MO): 46,648 shares (0.22% of portfolio)

Visa Earnings Outlook (as of August 2019)

Analysts at the time of the original filing anticipated Visa would report earnings around October 23, 2019. The consensus estimate called for earnings per share (EPS) of $1.43 — an 18.18% increase from the prior year’s $1.21. If achieved, this would represent approximately $3.20 billion in profit, implying a price-to-earnings ratio of roughly 30.63 at prevailing prices. Visa had reported actual EPS of $1.37 for the previous quarter, meaning Wall Street was then forecasting quarter-over-quarter EPS growth of approximately 4.38%.

Additionally, one insider purchase of approximately $171,130 was recorded for Visa between August 6, 2019 and the publication date, with no insider sales during the same period.

Recent Visa News Coverage (as of August 2019)

• Benzinga: “How To Open A Credit Card At 18” (July 31, 2019)
• Motley Fool: “Your Guide to the 10 Biggest Bank Stocks” (August 14, 2019)
• Seeking Alpha: “Buy Visa: Great Total Return And A Cash Machine” (August 2, 2019)
• Yahoo Finance: “Visa and J.P. Morgan Help Businesses Make Payments Faster with Billtrust’s Business Payments Network” (July 31, 2019)
• Seeking Alpha: “Load Up On Visa” (August 14, 2019)

Key Takeaways

• Spinnaker Trust’s increased MCD position reflects confidence in McDonald’s continued growth trajectory heading into mid-2019.
• Night Owl Capital Management’s modest trim of its Visa position does not necessarily indicate a bearish turn — the fund still held over 200,000 shares valued above $31 million.
• Visa’s broad institutional ownership base and strong year-over-year price performance underscore its status as a core holding for many large funds.
• Both MCD and V had meaningfully outperformed the S&P 500 in the year leading up to August 2019.

This article is based on Q1 2019 SEC 13F regulatory filings and market data as reported by stocksbeat.com. It is intended for informational purposes only and does not constitute investment advice.

This article is based on reporting originally published by ITPro Today, drawing on an interview with Armory CEO Daniel Odio.

What Is Spinnaker?

Spinnaker is an open-source, multi-cloud continuous delivery platform that Netflix originally developed to manage its large-scale cloud deployments. It has since evolved into a community-governed project with contributors from multiple organizations. Spinnaker supports deploying to a wide range of targets — virtual machines, containers, AWS, Google Cloud, Microsoft Azure, and other public cloud providers — making it appealing for teams that need flexibility across deployment environments.

According to Odio, Spinnaker effectively codifies the deployment best practices developed at Netflix and Google into a reusable platform: “You can think of Spinnaker as codifying kind of the best practices of Netflix and Google in a platform.”

A key strength is its role as an orchestration layer across cloud providers — what Odio described as “the conductor of the cloud orchestra” — handling the provisioning, management, and teardown of cloud infrastructure across different targets from a single control plane.

An Enterprise Distribution of Spinnaker

Armory follows an open-core business model: the foundation of its platform is the open-source Spinnaker project, with proprietary features layered on top for commercial customers. This approach lets Armory contribute to the upstream open-source project while building differentiated capabilities for enterprise use cases.

Odio highlighted two notable enterprise-specific capabilities:

• Air-gap deployment support: Armory can deploy Spinnaker in highly secure, network-isolated (“air gap”) data center environments where servers have no direct connection to external networks — a common requirement in regulated industries such as finance and defense.
• Pipelines as Code (GitOps): Armory introduced a feature that allows teams to define Spinnaker pipeline configurations as code, check those definitions into Git, and then share them as reusable modules across an organization. This GitOps approach ties deployment orchestration directly to version-controlled source code, improving auditability and consistency.

GitOps — the practice of using Git commits and pull requests to drive infrastructure and deployment operations — was an emerging pattern in the DevOps community at the time. Armory’s pipelines-as-code feature positioned Spinnaker as a natural fit for teams already using GitHub or other Git-based workflows.

Why Enterprise Teams Need CD Tooling at Scale

Odio’s core argument was that large enterprises — particularly Global 2000 companies — face a different class of CD challenge than smaller organizations. With thousands of developers, multiple business units, and a mix of on-premises and cloud infrastructure, they need:

• A single, standardized deployment path to production (a “golden path”)
• Centrally enforced compliance and security policies
• The ability to route workloads to the appropriate cloud target automatically
• Visibility across multiple cloud providers in one interface

Spinnaker’s multi-cloud architecture directly addresses these requirements. Developers can define what to deploy without needing to specify the underlying infrastructure details — whether a VM, container, or a particular cloud provider’s native service. Spinnaker handles the target-specific orchestration transparently.

Odio acknowledged that adopting Spinnaker is a significant investment: “Spinnaker is absolutely a big commitment and investment.” To support enterprise onboarding, Armory maintains a professional services and customer success organization that embeds with clients during implementation.

Multi-Cloud and Hybrid Cloud as Primary Use Cases

While Netflix built Spinnaker for aggressive, all-in cloud deployment, most large enterprises in 2019 were still in the early stages of cloud migration. Hybrid cloud — running workloads across both on-premises data centers and public cloud — was a common intermediate state. Spinnaker’s ability to manage deployments across both environments made it a practical tool for enterprises gradually shifting workloads rather than performing a hard cutover.

Odio positioned Spinnaker’s multi-cloud capabilities as a business differentiator: teams can visualize infrastructure state across all providers and deployment targets in a single view, reducing operational complexity during and after migration.

The CD Foundation

Spinnaker’s governance received a further boost in early 2019 when the Linux Foundation launched the Continuous Delivery Foundation (CDF) on March 12. The CDF provides a vendor-neutral home for key open-source CD projects. At launch, the foundation’s project portfolio included:

• Spinnaker — multi-cloud CD platform
• Jenkins — widely used open-source CI/CD automation server
• Jenkins X — cloud-native CI/CD for Kubernetes
• Tekton — Kubernetes-native pipeline framework (also a founding project)

Armory was a founding member of the CD Foundation. Odio expressed strong support for the initiative, framing it as an education and advocacy vehicle: “The CD Foundation is a platform through which cloud-native and leading projects that enable more modern ways to get to production can have a voice.”

He also argued that the broader DevOps community still had work to do in helping engineering leadership at large organizations understand that continuous delivery is a strategic priority, not simply a tooling choice: “DevOps is strategic, it’s no longer just tactical.”

Key Takeaways

• Armory builds an enterprise distribution of the open-source Spinnaker CD platform using an open-core model.
• Its $28M Series B (announced August 2019) was intended to expand product capabilities and go-to-market for Global 2000 customers.
• Proprietary capabilities include air-gap deployment support and GitOps-style pipelines as code.
• Spinnaker’s multi-cloud architecture makes it suited for hybrid cloud migration scenarios.
• Armory is a founding member of the Linux Foundation’s Continuous Delivery Foundation, alongside Jenkins, Jenkins X, and Tekton.

Background: Agile Stacks and HPE’s Kubernetes Strategy

At HPE Discover 2019, Agile Stacks — a company that counts Hewlett-Packard Enterprise (HPE) among its investors — announced expanded capabilities for its DevOps automation platform. The announcement coincided with HPE’s own public positioning of Kubernetes as a cornerstone of its hybrid cloud computing strategy, signalling growing industry alignment around container orchestration as the connective tissue between on-premises and cloud environments.

What the Agile Stacks Platform Does

The Agile Stacks platform is designed to automate the creation and management of DevOps pipelines across a wide range of tools and CI/CD platforms. Rather than requiring teams to manually integrate and maintain individual toolchains, Agile Stacks provides a structured framework that orchestrates those integrations automatically.

The platform’s Service Catalog includes more than 80 DevOps tools and platforms, among them:

• CI/CD & Source Control: Jenkins, GitLab, Spinnaker
• Machine Learning Pipelines: Kubeflow
• Container Registry: Harbor
• Object Storage: Minio
• Distributed Storage: Ceph, Portworx

SuperHub: Automating the Automation

At the heart of the Agile Stacks platform is the SuperHub automation hub. SuperHub accelerates software delivery through composable, configurable stacks. Each component within a stack is auto-configured to handle the full lifecycle of a service, including:

• Deploy, upgrade, and rollback
• Promote across environments and clone
• Backup and restore
• Test script generation and functional testing
• Performance testing and vulnerability scanning
• Code merges

The goal, as articulated by Agile Stacks, is to automate the DevOps automation itself — essentially removing the manual configuration overhead that grows as organisations add more tools and platforms to their delivery pipelines.

Addressing Tool Sprawl with a GitOps Framework

One of the persistent challenges in mature DevOps environments is tool sprawl. Organisations that have adopted best practices rarely standardise on a single vendor’s toolchain — they assemble purpose-fit tools from multiple vendors. This creates isolated silos of automation that can conflict, duplicate effort, or simply fail to share state.

Agile Stacks addresses this with an extensible GitOps framework that integrates heterogeneous toolchains under a single operational model. Because the framework is GitOps-based, infrastructure and pipeline configuration is version-controlled and auditable — a practical advantage as DevOps processes evolve and team membership changes over time.

Hybrid Cloud Complexity and Cloud Cost Visibility

Hybrid cloud adoption — driven in significant part by the maturation and widespread uptake of Kubernetes — introduces additional operational complexity. Most organisations want to run workloads across multiple public clouds and their existing on-premises infrastructure simultaneously, but the DevOps processes for each platform tend to be fragmented rather than unified.

Agile Stacks positions SuperHub as a tool to unify these processes across platforms. Beyond pipeline orchestration, SuperHub also supports automated cloud tagging — enabling teams to maintain better visibility into cloud spending by systematically labelling resources at provisioning time, rather than trying to retrofit tagging policies after the fact.

Lowering the Barrier to DevOps Adoption

Agile Stacks also stated an intent to make DevOps more broadly accessible by reducing the initial complexity that discourages adoption. Most organisations still struggle to automate software delivery reliably on a single platform. By abstracting toolchain integration through a composable, catalogue-driven model, the platform aims to let teams start with a working, opinionated baseline rather than building integration logic from scratch.

As hybrid cloud becomes a standard rather than an exceptional architecture, the pressure on engineering teams to implement consistent, enterprise-wide DevOps processes will only increase. Platforms like Agile Stacks represent one approach to managing that complexity — centralising orchestration while preserving the flexibility to adopt new tools as the ecosystem evolves.

Key Takeaways

• Agile Stacks announced expanded platform capabilities at HPE Discover 2019, backed by HPE investment.
• The platform’s SuperHub hub orchestrates composable DevOps stacks across more than 80 integrated tools.
• An extensible GitOps framework addresses tool sprawl in multi-vendor DevOps environments.
• Automated cloud tagging via SuperHub helps organisations track and control cloud spend.
• The platform targets both mature DevOps teams dealing with hybrid cloud complexity and organisations earlier in their DevOps journey.

Overview

Agile Stacks announced at the HPE Discover 2019 conference that it was expanding its DevOps automation platform to support Google Cloud Platform (GCP), Microsoft Azure, and Red Hat OpenShift — the Kubernetes distribution — alongside its existing support for Amazon Web Services (AWS). The move positions the company to help enterprises manage DevOps pipelines across heterogeneous, hybrid cloud environments from a single control plane.

Hewlett-Packard Enterprise (HPE), an investor in Agile Stacks, used the same conference to outline how Kubernetes sits at the center of its own evolving hybrid cloud strategy — making the timing of the announcement strategically significant.

What the Agile Stacks Platform Does

According to company CEO John Mathon, the Agile Stacks platform provides a framework for automating the creation of DevOps pipelines across multiple tools and CI/CD platforms. Key capabilities include:

• Service Catalog: More than 80 DevOps tools and platforms available out of the box, including Kubeflow, Jenkins, GitLab, Spinnaker, Harbor, Minio, Ceph, and Portworx.
• Composable Stacks: DevOps teams configure custom stacks from catalog components. Each component is auto-configured to handle deployment, upgrades, rollbacks, promotions, cloning, backups, test-script generation, merges, performance testing, vulnerability scanning, and functional testing.
• GitOps Framework: An extensible GitOps-based integration layer ties together tools from multiple vendors, reducing the automation silos that typically emerge when organizations adopt best-of-breed tooling.
• Automated Cloud Tagging: Cost visibility across clouds is improved through automated cloud tagging applied via the SuperHub, helping teams track cloud spending without manual overhead.

The SuperHub: Automating DevOps Automation

At the core of the platform is the SuperHub automation hub. Rather than requiring DevOps engineers to wire together individual tools manually, SuperHub orchestrates the entire pipeline lifecycle — from initial provisioning through ongoing operations — using composable, version-controlled stack definitions.

Mathon described the product philosophy as “automating the DevOps automation.” Organizations that have matured their DevOps practices typically accumulate tools from multiple vendors. Without a unifying layer, those tools create isolated automation islands that can work at cross-purposes. The SuperHub and its GitOps framework are designed to resolve that fragmentation, allowing tooling choices to evolve as organizational DevOps maturity improves.

Addressing Hybrid Cloud Complexity

The multi-cloud expansion reflects a broader industry reality: as Kubernetes adoption accelerates, organizations increasingly want to run workloads across public clouds and on-premises infrastructure simultaneously. However, each platform carries its own DevOps tooling assumptions and operational patterns, which compounds complexity for platform and DevOps engineering teams.

Mathon argued that hybrid cloud adoption will ultimately push many organizations to standardize DevOps practices enterprise-wide — something that is difficult to achieve without a platform layer that abstracts away provider-specific differences. Agile Stacks positions its platform as that abstraction layer, enabling consistent pipeline behavior whether workloads run on AWS, GCP, Azure, OpenShift, or on-premises Kubernetes clusters.

Lowering the Barrier to DevOps Adoption

Beyond serving mature DevOps organizations, Mathon noted that Agile Stacks aims to reduce the initial complexity that prevents less experienced teams from adopting DevOps practices at all. By providing pre-integrated, auto-configured stacks through a service catalog, teams can get functional pipelines running without deep expertise in every individual tool.

This is particularly relevant for enterprises that are simultaneously navigating their first hybrid cloud deployments and trying to establish consistent delivery practices — two challenges that, when tackled together, can be overwhelming without appropriate tooling.

Key Takeaways

• Agile Stacks extended its platform to GCP, Azure, and Red Hat OpenShift in June 2019, adding to existing AWS support.
• The SuperHub automation hub uses composable, GitOps-managed stacks to orchestrate end-to-end DevOps pipelines.
• A service catalog of 80+ tools — including Jenkins, GitLab, Spinnaker, and Kubeflow — is available out of the box.
• Automated cloud tagging through SuperHub provides cost tracking across multi-cloud environments.
• The platform targets both DevOps-mature organizations struggling with tool fragmentation and newer adopters facing initial setup complexity.
• HPE is an investor in Agile Stacks and is aligning its own hybrid cloud strategy around Kubernetes.