<?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[Stories by Fintan Ryan on Medium]]></title>
        <description><![CDATA[Stories by Fintan Ryan on Medium]]></description>
        <link>https://medium.com/@fintanr?source=rss-45656b37e1dd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*rZoIthdzlCaqitsCe0OlMw.jpeg</url>
            <title>Stories by Fintan Ryan on Medium</title>
            <link>https://medium.com/@fintanr?source=rss-45656b37e1dd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 11:20:48 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@fintanr/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Mapping the Cloud — A Look at Major Cloud Providers, 2006 to Now]]></title>
            <link>https://medium.com/@fintanr/mapping-the-cloud-a-look-at-major-cloud-providers-2006-to-now-44f7802d1f7d?source=rss-45656b37e1dd------2</link>
            <guid isPermaLink="false">https://medium.com/p/44f7802d1f7d</guid>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud]]></category>
            <dc:creator><![CDATA[Fintan Ryan]]></dc:creator>
            <pubDate>Wed, 20 May 2026 08:12:26 GMT</pubDate>
            <atom:updated>2026-05-20T08:12:26.791Z</atom:updated>
            <content:encoded><![CDATA[<p>From an understated launch by AWS in 2006 to the massive capex investments we see in 2026, cloud computing has utterly revolutionized how we think about acquiring and using compute capacity.</p><p>I have found this entire space fascinating since 2008, and I wanted a simple way to plot and compare the overall growth over time. So I created a <a href="https://fintanr.com/cloudmap">Cloud Region Launch History</a> tool. You can filter to specific times, across providers, sovereign regions, government clouds and industry specific offerings.</p><p>For example when my analyst career started in 2015 at <a href="https://redmonk.com/">RedMonk</a>, the map for AWS and GCP looked a bit like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5TeSw92yHL4mMqKu.png" /></figure><p>And by the time I led the <a href="https://www.linkedin.com/pulse/cloud-application-platform-services-aws-azure-google-fintan-ryan/">Cloud Application Platforms</a> research at <a href="https://gartner.com/">Gartner</a> in early 2021 the map was:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JBvNdCakwzxFIHIV.png" /></figure><p>When I left the analyst game and joined GitHub later in 2022, Azure’s footprint was:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*S4hWAuhuJypiZGb2.png" /></figure><p>And these days it looks like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*84YLQ2pfqyvmzQqu.png" /></figure><p>The <a href="https://fintanr.com/cloudmap">tool</a> is available to anyone to use. Constructive comments and feedback on any obvious glaring data gaps (there are a few where the number of AZs needs to be further verified) appreciated.</p><p><strong>Notes on the Data</strong></p><p>Data is sourced from public announcements and documentation. We will have gaps where vendor specific details are behind a login or paywall. We include a filter to eliminate regions with less than 3 AZs. That said, the definition of an AZ, and in particular the geographic distances between each AZ, varies between providers — so do check this data yourself.</p><p><strong>Providers covered:</strong></p><p>We included the three hyperscalers:</p><ul><li><a href="https://aws.amazon.com/"><strong>AWS</strong></a></li><li><a href="https://azure.microsoft.com/"><strong>Azure</strong></a></li><li><a href="https://cloud.google.com/"><strong>GCP</strong></a></li></ul><p>And a set of smaller or regional providers:</p><ul><li><a href="https://www.alibabacloud.com/en?_p_lc=1"><strong>Alibaba</strong></a></li><li><a href="https://cloud.huawei.com/"><strong>Huawei</strong></a></li><li><a href="https://cloud.ibm.com/docs"><strong>IBM</strong></a></li><li><a href="https://www.oracle.com/cloud/"><strong>Oracle</strong></a></li><li><a href="https://www.tencentcloud.com/"><strong>TenCent</strong></a></li></ul><p>The providers I included for this iteration are the same as those Gartner included in the (catchily titled) <a href="https://www.gartner.com/interactive/mq/6808434">Magic Quadrant for Strategic Cloud Platform Services,</a> published in August 2025. Gartner have a minimum revenue requirement of at $1Bn for vendors with more than three years GA, or $500M with 40% CAGR for those who have been GA for less than three years. There are a bunch of other criteria, but I find this useful as a guideline.</p><p>Originally published on <a href="https://fintanr.com/links/2026/05/18/cloudmap.html">fintanr.com</a></p><p><strong>Disclosures</strong>: I covered cloud, and specifically application development in cloud environments extensively at Gartner and RedMonk. During that time I attended numerous analyst events related to each of the hyperscalers. I currently work at GitHub.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=44f7802d1f7d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Strategy Behind MCP]]></title>
            <link>https://medium.com/@fintanr/the-strategy-behind-mcp-5d1cea61ee7b?source=rss-45656b37e1dd------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d1cea61ee7b</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[llm]]></category>
            <category><![CDATA[model-context-protocol]]></category>
            <category><![CDATA[mcp-server]]></category>
            <category><![CDATA[strategy]]></category>
            <dc:creator><![CDATA[Fintan Ryan]]></dc:creator>
            <pubDate>Tue, 01 Apr 2025 15:15:59 GMT</pubDate>
            <atom:updated>2025-04-01T15:15:59.805Z</atom:updated>
            <content:encoded><![CDATA[<p>Model Context Protocol (MCP), first defined by Anthropic, is surfing a wave of enthusiasm right now. MCP has, incredibly quickly, become a de-facto standard for integration with LLMs. OpenAI’s announcement of support for MCP in the last week of March 2025 essentially confirms this position. New announcements of MCP support are emerging on an almost hourly basis.</p><p>Away from the wave of MCP servers and integrations, the bigger question that arises is how to interpret Anthropic’s underlying strategy with MCP, and what are the wider implications for the industry. We briefly look at this from two angles, consumer vs enterprise positioning and platforms.</p><h3>Consumer vs Enterprise Positioning</h3><p>Anthropic is not positioned as a consumer brand. Everything in their actions and intent thus far has been positioned towards enterprises or power users. Yes, they support consumers, but not as the first port of call. ChatGPT and by extension OpenAI is, as Ben Thompson at Stratechery often notes, <a href="https://stratechery.com/2025/an-interview-with-openai-ceo-sam-altman-about-building-a-consumer-tech-company/">an accidental consumer brand at scale</a>. That is not to say that OpenAI is not focused on enterprise, they absolutely are, but their GTM is distinctly different from that of Anthropic.</p><p>While Anthropic, OpenAI and other foundation model providers have similar problem sets to deal with, this focus on enterprise and power users means that Anthropic have a much more urgent need to bring external context into the LLM and allow for additional integration points. Hence MCP.</p><h3>From a Platform Layer to the Platform Core</h3><p>Enterprises, and software vendors in particular, currently view LLMS as being a layer of a platform they leverage, providing input to and consuming its output. The bottom of the implementation pyramid one might say.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/942/0*TVziTyWX3yUB0FkQ.png" /></figure><p>However, Anthropic, and probably all new LLM providers, see the LLM very much at the core of what happens next. They provide analysis, decision and orchestration layers. Which in turn increases usage and ultimately drives revenue. The tools using the LLM are there to serve it, provide context and execute its decisions. Not the other way round.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*m-1bVimIT6BkQsJy.png" /></figure><p>But how do you manage such a feat, you can’t just disintermediate the tools — you need the tools to disintermediate themselves. That, at its core, is the goal of MCP and in my opinion a core strategy for Anthropic.</p><p>Right now, technologists are rushing headlong into this world. That is entirely justifiable. They see an immediate set of largely technical problems to be solved.</p><p>However, companies doing even a cursory analysis of their strategy will quickly ask if they really want to be mere conduits for an LLM or organisations that deliver products that leverage the capabilities of LLMs.</p><p>My bet is very much on leveraging the capabilities of LLMs. But we have six months to a year of the LLMs as the Platform Core to go through first.</p><p>First posted on <a href="https://fintanr.com/links/2025/03/31/mcp-strategy.html">fintanr.com</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d1cea61ee7b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Do Software Vendors Communicate Big Releases?]]></title>
            <link>https://medium.com/@fintanr/how-do-software-vendors-communicate-big-releases-b8540f2929cf?source=rss-45656b37e1dd------2</link>
            <guid isPermaLink="false">https://medium.com/p/b8540f2929cf</guid>
            <category><![CDATA[analyst-relations]]></category>
            <category><![CDATA[marketing-strategies]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[software]]></category>
            <dc:creator><![CDATA[Fintan Ryan]]></dc:creator>
            <pubDate>Wed, 24 Jul 2024 21:59:47 GMT</pubDate>
            <atom:updated>2024-07-24T21:59:47.221Z</atom:updated>
            <content:encoded><![CDATA[<p>Every software vendor needs attention on their big releases. Marketing and communications teams are measured on the views and interactions they receive. Sales pipelines depend on demand generation. Yet the amount of noise in every sector is louder than ever, and only increasing.</p><p>This leads to two questions — what is the best approach for vendors to adopt to garner the most attention for big releases? And what are the common approaches that various vendors take? We discuss the five most common approaches below.</p><figure><img alt="how do software companies communicate big releases" src="https://cdn-images-1.medium.com/max/1024/1*B3I31SMGMxmRZBTa3mr_Cg.png" /></figure><ul><li><strong>Continuous</strong>: A mixture of incremental improvements and major releases, but with no defined cadence. Only the people who very closely observe your company are likely to be paying attention, otherwise you are reliant on creating a media event for attention.</li><li><strong>Quarterly Cadence</strong>: Every three months you have a launch announcement / event. This approach provides a reliable cadence of marketing moments to build on. Cloudflare, with their quarterly “weeks” about a specific topic, and GitLab, with their quarterly release schedule, are among the leading examples of this approach. Companies that adopt the quarterly cadence will generally deliver their products in a continuous manner, but bundle the major announcements together.</li><li><strong>Conference Driven</strong>: Major vendors normally have one to two very large events that focus on different customer segments, and internal timelines target releases (or at the very least a beta or waitlist announcement) at these events. Oracle have historically been the best example of this approach. Every major project is a “Larry project” [1] for Oracle OpenWorld. However, in recent years AWS has challenged to take up that mantle with a huge amount of releases and announcements during re:Invent. Legacy vendors, which do big annual releases, will also often follow this approach.</li><li><strong>Foundation Conference Driven</strong>: These are announcements that are centred around Open-Source Foundation events. The CNCF, for example, has done an exceptional job of marketing Kubecon and ensuring attention from press and analysts. In the early days of Kubernetes, you would see various vendors, particularly startups, announcing new products during Kubecon. However most companies have backed away from making significant product announcements at Foundation events, and there is now more focus on momentum and project related press releases.</li><li><strong>Seasonal Releases</strong>: Companies do two to three major releases of their offering each year and run community-focused events around the release. Salesforce is the classic example of this approach.</li></ul><p>The reality of modern software is that most cloud first and SaaS companies are continuously releasing updates, but they also need to have marketing events and these marketing events set specific timelines that have larger ramifications.</p><p>The approach a company takes to communicating the big commercial moments around its software releases is usually a manifestation of its tactical execution, rather than any grand strategic vision. You can infer a lot about a company’s internal operating culture from its approach to product announcements.</p><p>Simply put if the communications feel chaotic and ad-hoc, it is very likely the company operates that way internally. If it is deliberate and clearly planned on a regular cadence, that is likely to be how the company also approaches product releases. If it is batched and annual or bi-annual, large parts of the organisation will be heads down preparing for that big event and only come up to look around after that point.</p><p>These varying approaches cascade through the day-to-day work of many parts of the company, such as product, engineering, marketing, communications and sales. They will dictate a significant part of the company culture. In many organisations the approach has been set by years, or decades, of corporate history.</p><p>There is no single right way to do this, quarterly and conference driven announcements work for many companies.</p><p>In my time as an analyst the quarterly cadence approach was by far the easiest to follow. Most enterprises are never right at the cutting edge of product releases, but they are interested in reasonably regular updates, particularly in faster moving areas.</p><p>1. Larry project: a project which the product and engineering team thinks will make one of the Oracle OpenWorld Keynotes.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b8540f2929cf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On IBM acquiring HashiCorp]]></title>
            <link>https://medium.com/@fintanr/on-ibm-acquiring-hashicorp-c9c73a40d20c?source=rss-45656b37e1dd------2</link>
            <guid isPermaLink="false">https://medium.com/p/c9c73a40d20c</guid>
            <category><![CDATA[hashicorp]]></category>
            <category><![CDATA[ibm]]></category>
            <category><![CDATA[mergers-and-acquisitions]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[cloud-native]]></category>
            <dc:creator><![CDATA[Fintan Ryan]]></dc:creator>
            <pubDate>Thu, 25 Apr 2024 17:44:24 GMT</pubDate>
            <atom:updated>2024-05-03T09:24:50.645Z</atom:updated>
            <content:encoded><![CDATA[<p>On April 24th, 2024, IBM confirmed they are <a href="https://newsroom.ibm.com/2024-04-24-IBM-to-Acquire-HashiCorp-Inc-Creating-a-Comprehensive-End-to-End-Hybrid-Cloud-Platform">acquiring HashiCorp for $6.4Bn</a>. HashiCorp has a wide reach across the cloud ecosystem, with multiple partnerships and close relationships across all the major cloud service providers. This acquisition presents opportunities and challenges for IBM.</p><p>Four core questions arise:</p><ul><li>How has HashiCorp ended up being an acquisition?</li><li>Has the BSL licensing change contributed and what are the implications for OpenTofu?</li><li>Where might IBM position HashiCorp in their portfolio?</li><li>Will the acquisition of HashiCorp help grow IBM Cloud?</li></ul><p>To answer these questions, we will look at the HashiCorp customer base, net dollar retention and then look at the possible approaches IBM may adopt.</p><h3>HashiCorp Subscriber Growth &amp; Net Dollar Retention</h3><p>HashiCorp is highly dependent on a subset of customers with above $100K ARR. As <a href="https://medium.com/@fintanr/the-hashicorp-bsl-move-ee79659a0b54">we noted last year</a> when the HashiCorp relicensed Terraform to the BSL:</p><blockquote>Moreover 89% of HashiCorp’s revenue comes from customers with over $100K ARR, who represent just 19% (830 of 4392 customers as of Q1FY24) of their paying customer base. On top of this, revenues are also highly geographically concentrated, with 71% of sales in the United States.</blockquote><p>In the subsequent three quarters the level of growth in this $100K+ segment has slowed even further, while the revenue concentration has stayed the same at 89%.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R7TkTfHQHMcUfr5zqBiUSw.png" /></figure><p>Alongside this HashiCorp’s Net Dollar Retention (NDR) has continued to decline, with a very substantial drop in the last two quarters to 115. While the days of 130+ NDR are in the past for many companies given the wider macro-economic environment, the drop has been exceptionally fast here.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C9Pa6QSE-eES8uf96z6wnA.png" /></figure><p>Simply put this is a business with rapidly slowing growth that cannot support its existing valuation, never mind the valuation at IPO. It has been an acquisition target for a while, but the price is still, even with the decline since IPO, relatively high.</p><p>However, no one doubts the utility of the products HashiCorp created — Vault and Terraform in particular — are extremely popular offerings, but utility by itself does not translate into enterprise revenue. IBM has enough enterprise relationships to make this acquisition worthwhile.</p><h3>Terraform, Open ToFu and the BSL</h3><p>At the <a href="https://medium.com/@fintanr/the-hashicorp-bsl-move-ee79659a0b54">time of the BSL change I stated</a>:</p><blockquote>It is still too early to see how the move to BSL licenses will play out for HashiCorp</blockquote><p>While correlation is not causation, the level of new customer growth, the wider base for the $100K customer funnel, slowed dramatically once Terraform was relicensed, dropping to a low of a 1.5% quarter on quarter growth immediately after the BSL change. It is hard not to conclude that the two events are connected.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aI2MT5ngcP7PWLmFLdR45w.png" /></figure><p>Alongside this we have had the <a href="https://opentofu.org/blog/our-response-to-hashicorps-cease-and-desist/">recent cease and desist with the OpenTofu project </a>which has undoubtedly led to more negative headlines for, and sentiment towards, HashiCorp overall.</p><p>More importantly, as shown above, the NDR numbers have moved from a gradual decline to a much steeper slope. At a time when overall cloud spend is still, despite everything happening, continuing to grow, this would seem to indicate hesitation and churn in the HashiCorp customer base.</p><p>Now all of this does lead to a question of what happens next for Terraform? Before OpenTofu there were a lot of rumblings and community pressure for Terraform to move to the Linux Foundation.</p><p>IBM has historically had a very strategic approach to open source (their investments in Linux, Eclipse, Node and most recently Kubernetes highlight this). Could there be a route to Terraform and Open Tofu becoming one again?</p><p>Where IBM positions HashiCorp internally will be key to this decision.</p><h3>Positioning HashiCorp in IBM</h3><p><em>Update 4/26: a number of IBM employees have reached out privately to comment on the </em><a href="https://newsroom.ibm.com/2024-04-24-IBM-to-Acquire-HashiCorp-Inc-Creating-a-Comprehensive-End-to-End-Hybrid-Cloud-Platform"><em>details in the main announcement</em></a><em> of HashiCorp remaining a separate division within IBM Software. Given the length of time it will take for the acquisition to complete, and the types of managerial changes that normally ensue during an acquisition, I still feel the scenarios discussed below are more likely in the next 18 to 24 months. I will revisit this again once the aquistion completes.</em></p><p>When IBM acquired Red Hat there were many serious questions raised as to how Red Hat would be allowed to operate. IBM have largely allowed Red Hat to operate as a separate entity, bolstered by additional IBM sales personal and enterprise account reach.</p><p>Red Hat has a successful business model, and a track record of moving technologies from acquired companies from an Open Core to Open-Source model, for example what they did with Ansible.</p><p>Red Hat, at its heart, had developed into an exceptionally good sales organisation that could take and scale new products across their client base. IBM leaned into this with OpenShift, and now control a significant portion of the Kubernetes market.</p><p>HashiCorp is a much smaller entity and is unlikely to be able to be left alone in the manner that Red Hat has been. This leaves us two options:</p><p>· Bring HashiCorp into the Red Hat entity.</p><p>· Run HashiCorp as part of the IBM Cloud division.</p><p>My money is on the former here. Strategically it is a reasonably good fit, Terraform and Ansible combined makes a strong story, the other components work well with the wider Red Hat portfolio. The trick is not to tie HashiCorp into an OpenShift bundle.</p><p>The big move, and obvious desire among the wider open source community, is for Terraform to have its license changed back to the MPL-2.0 license. The <a href="https://opentofu.org/manifesto/">OpenTofu manifesto</a> would need IBM to go further, donating Terraform to a foundation, such as the Linux Foundation, and agreeing to impartial governance of the project.</p><p>If HashiCorp becomes part of IBM Cloud, that is a whole other P&amp;L, with a different set of pressures as we discuss below. The incentive to work with the community to re-license Terraform may not be there.</p><p>The other part of the deal, which I have not seen commented on elsewhere, is the value of the data in Terraform Cloud and in the Terraform registry. HashiCorp have a unique view into cloud deployments world-wide, and IBM could, and should, use this data to inform their own strategy.</p><h3>IBM Cloud?</h3><p>The other open question is will Hashicorp help drive IBM Cloud adoption. The short answer here is that no, it will not.</p><p>The gaps with IBM cloud are well documented, Gartner have placed the offering as a <a href="https://aws.amazon.com/blogs/aws/read-the-2023-gartner-magic-quadrant-for-strategic-cloud-platform-services/">niche player in their IaaS MQs</a> now renamed to MQ for Strategic Cloud Platform Services) for the last five years. While they note a focus on regulated industries, Gartner repeatedly cite reliability issues (2021, 2022, 2023) alongside disjointed architectures, reliability, and poor experience issues (2019, 2020, 2022, 2023). Forrester last placed IBM as a Contender in their <a href="https://www.forrester.com/report/the-forrester-wave-tm-public-cloud-development-and-infrastructure-platforms-global-q4-2022/RES176392">2022 Public Cloud Development and Infrastructure Platforms Wave</a>, but also noted IBM needs to bolster core offerings.</p><p>Alongside these criticisms, there is also the question of CapEx. I will leave it to others to<a href="https://platformonomics.com/platformonomics-clownwatch/"> provide a deeper analysis of IBMs CapEx</a>, but you can’t be a serious player in cloud without significant CapEx and IBMs own financial reporting shows that it is just not investing here.</p><p>At its core HashiCorp has always been an infrastructure compliance and security play, and the one area where IBM Cloud has some potential differentiation is <a href="https://www.ibm.com/cloud/financial-services">IBM Cloud for Financial Services</a>, but even in that the number of public logos is minimal and dated — all from 2020. However, HashiCorp could easily augment some of the offerings here.</p><p><strong><em>Side note</em></strong><em>: it is clear reading analyst reports that IBM are focusing a large part of their briefings on cloud to the IBM Cloud for Financial Services offering, hence its frequent mentions. The lack of reference logos does raise questions, but financial services are traditionally more hesitant than most to give public endorsements. That said, the three leading cloud vendors — AWS, Google and Microsoft — all have multiple references in this sector.</em></p><h3>Conclusion</h3><p>The HashiCorp acquisition is a net positive for IBM, however the execution will be key. From the press release it is clear that IBM see Terraform as highly complementary to Ansible, and this will give IBM an end-to-end deployment capability.</p><h3>Disclaimers</h3><p>I covered HashiCorp as an industry analyst from 2015 until 2022, at RedMonk and then at Gartner. At Gartner my primary published research touched more on Consul but Terraform and Vault frequently featured in conversations with end user clients. HashiCorp paid for my T&amp;E to several pre-pandemic HashiConf’s.</p><p>I covered IBM and Red Hat as an industry analyst from 2015 until 2022, at RedMonk and then at Gartner. OpenShift was a frequent topic of discussion with clients. IBM and Red Hat paid for my T&amp;E to several pre-pandemic events.</p><p>I covered the cloud native ecosystem, including the CNCF, as an industry analyst from 2015 to 2022 at RedMonk and Gartner. At Gartner Cloud Foundry, Kubernetes, and the wider Kubernetes ecosystem, including numerous projects and companies associated with the CNCF and the Cloud Foundry Foundation featured in conversations with end user clients. The CNCF, Cloud Foundry Foundation and the Linux Foundation paid for my T&amp;E to a significant number of pre-pandemic events.</p><p>Paying for T&amp;E is common practice for analysts attending vendor and foundation events.</p><p>The opinions posted in this piece are entirely my own.</p><p><strong>Edits</strong></p><p>4/25 — updated with clarification on the OpenTofu manifesto f<a href="https://www.linkedin.com/feed/update/urn:li:activity:7189322253275131905?commentUrn=urn%3Ali%3Acomment%3A%28activity%3A7189322253275131905%2C7189323982410526721%29&amp;dashCommentUrn=urn%3Ali%3Afsd_comment%3A%287189323982410526721%2Curn%3Ali%3Aactivity%3A7189322253275131905%29">ollowing a comment from Ohad Maislish</a>, CEO of <a href="https://www.env0.com/">env0</a>.</p><p>4/26 — clarification on license from a comment by Matt Wilson.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c9c73a40d20c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The HashiCorp BSL Move]]></title>
            <link>https://medium.com/@fintanr/the-hashicorp-bsl-move-ee79659a0b54?source=rss-45656b37e1dd------2</link>
            <guid isPermaLink="false">https://medium.com/p/ee79659a0b54</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[hashicorp]]></category>
            <category><![CDATA[cloud-native]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Fintan Ryan]]></dc:creator>
            <pubDate>Sun, 27 Aug 2023 13:47:03 GMT</pubDate>
            <atom:updated>2023-08-29T13:12:51.483Z</atom:updated>
            <content:encoded><![CDATA[<p>On August 10th, 2023, HashiCorp <a href="https://www.hashicorp.com/blog/hashicorp-adopts-business-source-license">announced</a> that they have adopted the Business Source License (BSL) for all future releases of core HashiCorp products, switching from the Mozilla Public License (MPL 2.0). The wider community and, understandably, vendors that are building their commercial offerings on these products, reacted negatively.</p><p>A fork of the latest MPL 2.0 version of Terraform, one of the most widely used of HashiCorp products and open-source projects, has been <a href="https://opentf.org/announcement">announced</a> on August 25th, 2023 by the OpenTF. They aim to submit this project to the Cloud Native Compute Foundation (CNCF).</p><p>Three core questions arise:</p><ul><li>What is the commercial reasoning for this move by HashiCorp?</li><li>Is it advisable for individual companies to continue to use HashiCorp related open-source projects?</li><li>What are the wider implications for open-source projects going forward?</li></ul><p>To answers these questions, we will look at the current financial position of HashiCorp and some key competitive pressures, what the BSL means for enterprises and then the wider implications of the license change.</p><h3>The Commercial Reasoning</h3><h4>A Look at HashiCorp’s Financials and Customer Base</h4><p>To understand the commercial pressures and risks HashiCorp are under, we first look at their quarterly earnings releases.</p><p>HashiCorp, like many of the companies in the cloud native space who IPOed between 2019 and 2022, has never turned a profit. In the low interest rate era up to mid 2022, growth was all that mattered. But since that time, we have had a marked shift in investor sentiment from growth to profitability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OHXhhfq_o4Ibz2L0srtrlg.png" /></figure><p>As of the end of HashiCorp’s Q1FY24 (<a href="https://www.sec.gov/ix?doc=/Archives/edgar/data/0001720671/000162828023021271/hcp-20230430.htm">SEC 10Q filing</a>, <a href="https://ir.hashicorp.com/static-files/e75cec96-3e99-4742-a8c2-c14991edccc0">investor relations presentation</a> , June 2023) ,HashiCorp revenue is hugely concentrated into two products (Terraform and Vault). These generate 85% of their revenue. Moreover 89% of HashiCorps revenue comes from customers with over $100K ARR, who represent just 19% (830 of 4392 customers as of Q1FY24) of their paying customer base. On top of this, revenues are also highly geographically concentrated, with 71% of sales in the United States.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7ygGmmRCZHomISxnLWTdDw.png" /></figure><p>This dependence on a small subset of enterprise customers is not unusual for firms like HashiCorp. What is more challenging from a HashiCorp perspective, however, is having several competitors explicitly targeting one of your core products while using a project you are the major contributor too within their products. That is, however, a direct trade off from developing software under an open-source license.</p><p>Indeed, HashiCorp, and in turn investors, are more than aware of this. Hashicorp has included the following statement in their all their financial filings, including the initial S1 prior to IPO:</p><blockquote>“Because of the permissive rights accorded to third parties under our open-source and source available licenses, there are limited technological barriers to entry into the markets in which we compete and it is, and may continue to be, relatively easy for competitors, including public cloud operators, to enter our markets and compete with us.”</blockquote><p>At same time HashiCorp acknowledge that the open-source nature of their projects, and the community associated with them, is a key customer acquisition strategy.</p><h3>An Interesting Market?</h3><p>As noted above, 85% of HashiCorp revenue comes from Terraform and Vault. However, most of the competitive action has been around Terraform, and it has attracted some VC interest.</p><p>Many companies have emerged around the Terraform ecosystem. While the majority are of these companies deliver professional services, a few have product offerings and have attracted VC funding. Overall, this market is still in a nascent stage, but <a href="https://www.env0.com/">Env0</a>, <a href="https://spacelift.io/">SpaceLift</a> and <a href="https://digger.dev/">Digger</a> collectively received $52.8M in funding between 2020 and 2023. <a href="https://www.scalr.com/">Scalr</a> received a series A much earlier, back in 2016. There are also several bootstrapped companies, <a href="https://gruntwork.io/">Gruntwork</a> being the most well-known among them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-V1u_GnrsR9_iVi8XLr0gA.png" /><figcaption>VC Funding of Select TerraForm Competitors, 2020–2023</figcaption></figure><p>The common thread with the four VC funded vendors mentioned above is that they compete directly with Terraform Enterprise and build upon the opensource Terraform project. This also means they are competing for the highly concentrated customer base that HashiCorp has developed in recent years.</p><p>The ins and outs of exactly how many community contributions HashiCorp has received is a topic for others debate. However, HashiCorp state they received less than 5% of the overall contributions from the community to the core projects. In contrast, several orgs have pointed out that they tried, and were unable, to contribute.</p><p>The wider Terraform ecosystem is extremely vibrant. Terraform is designed to be extensible, and the provider, modules and additional tooling ecosystem has a wide variety of contributors.</p><p>But with all of that said, HashiCorp’s R&amp;D spend for Q1FY24 was $54M alone — more than then the total amount of VC funding highlighted above. Obviously, only a subset of this goes directly to Terraform, but GitHub commits alone do not tell the full story of any project.</p><h3>Ongoing Usage</h3><p>Enterprises generally have a list of approved open-source licenses, managed out of some form of Open-Source Program Office (OSPO) and/or approved by procurement and legal teams. Getting a new open-source, or restrictive, license approved is a non-trivial task in most enterprises.</p><p>HashiCorp have been very clear in their <a href="https://www.hashicorp.com/blog/hashicorp-updates-licensing-faq-based-on-community-questions">FAQs</a> about the license change that the target for this change is other competitive offerings. If, for example, you are using Terraform in your CI/CD pipelines internally, your risk profile is unlikely to change significantly by continuing you to use it.</p><p>Whatever your philosophical thoughts on this, if you are already using products like MongoDB or ElasticSearch, your legal, procurement and OSPO teams will have already done their due diligence on the overall framework of the BSL license, and you are unlikely to have any legal concerns about this change. The one thing to be crystal clear on is that the BSL is not an open-source license.</p><p>So, what does the change to BSL mean for most enterprises using an existing HashiCorp project? Business as usual for now.</p><h3>Industry Implications</h3><p>The wider implications of HashiCorp’s relicensing are more profound for the technology industry. Over the last decade we have seen a large amount of “single company” open-source projects emerge. Open-source in and of itself has become a key marketing component and adoption funnel, something which HashiCorp acknowledge in their quarterly financial reports.</p><p>Relicensing to the BSL changes this approach. As my former colleague, Stephen O’Grady at RedMonk, <a href="https://redmonk.com/sogrady/2023/08/03/why-opensource-matters/">recently noted</a>:</p><blockquote>“Generally, what they are trying to sell you is a license that allows them to have their cake — the immensely successful and popular brand that is “open source” — and eat it too, which is to say the benefits without any of the costs of open source. Typically this means the addition of the ability to restrict a behavior, use or model that they feel impinges on their ability to exclusively monetize an asset… “</blockquote><p>Sometimes a project appears, and a company emerges around it. Other times it is, intentionally, the opposite direction. Or, as in HashiCorp’s case, a project starts (Vagrant, initially released in 2010), a firm emerges later (HashiCorp, founded 2012) and then other projects appear (Terraform, initially released in 2014). Terraform falls squarely into the single company open-source pattern.</p><p>A large and vibrant community has developed around TerraForm, in part due to its open-source nature and extensibility, but also as it provides a solution to one of the key challenges in cloud — the consistent provisioning of infrastructure. But HashiCorp has always retained control of the source and required contributor agreements from any external parties contributing to the project that assigned the contributions ownership and copyright to HashiCorp. To be clear, they are far from the only company with this model.</p><p>However, this model also requires a lot of trust on the side of the contributors and the wider community. Where Terraform differs from many other projects with this model is the size of ecosystem developed on top of TerraForm itself. HashiCorp attempted to address this with the license change by keeping APIs, SDKs and Terraform providers under the MPL 2.0 license. It is unclear if this is enough to satisfy the wider community. The OpenTF fork (more below) demonstrates that it is clearly not enough for a significant group.</p><p>Prior to the widespread adoption of open-source software, having source code available in escrow was enough of a risk mitigation for many enterprises. This is, in some ways, analogous to having source available under the BSL.</p><p>This gives us three (very generic) models:</p><ul><li>Single Vendor, restrictive license, source available</li><li>Single Vendor, permissive license</li><li>Foundation supported (providing corporate structure, IP assignment), permissive license</li></ul><p>The longer-term question is if we see more of a shift to single vendor, restrictive, but source available licenses, or foundation supported open-source projects. There are other widely used projects primarily supported by a single vendor that could just as easily go the route of the BSL.</p><h3>The OpenTF Fork</h3><p>As of August 25th we now know there will be a fork of Terraform, OpenTF, with a goal to have the project become part of the <a href="https://cncf.io/">Cloud Native Compute Foundation</a> (CNCF). The CNCF must of course agree to accept the project.</p><p>There is also a strategic question for the CNCF in doing so. As an organisation they have always stated they do not want to choose the winners, but it is also clear that a project that graduates within the CNCF is, to a large extent, an anointed winner in the cloud native landscape.</p><p>Up to now, projects may have been competing against each other, but they have not been direct forks of an existing project. If the OpenTF project is accepted (and I do not see a reason for it to be rejected), it breaks new ground for the CNCF. It is far too early to judge if this will have an impact on the overall structures and governance within the CNCF. However, some organizations with projects that are essentially single company open-source, even if under the auspices of a foundation, may have concerns that other forks follow.</p><h3>Conclusions</h3><p>It is still too early to see how the move to BSL licenses will play out for HashiCorp. Parts of the Terraform community are clearly upset by the change, but it is also obvious that some are upset for very commercial reasons.</p><p>Does the licensing matter greatly? In my opinion it does and for commercial entities trying to build businesses it matters massively. But, turning once again to Stephen O’Grady at RedMonk, when it comes to the definition of open-source, by far the largest group is <a href="https://redmonk.com/sogrady/2023/08/03/why-opensource-matters/">“<em>those that don’t care</em>”</a>.</p><h3>Disclaimers</h3><p>I covered HashiCorp as an industry analyst from 2015 until 2022, at RedMonk and then at Gartner. At Gartner my primary published research touched more on Consul but Terraform and Vault frequently featured in conversations with end user clients. HashiCorp paid for my T&amp;E to several pre-pandemic HashiConf’s.</p><p>I covered the cloud native ecosystem, including the CNCF, as an industry analyst from 2015 to 2022 at RedMonk and Gartner. At Gartner Cloud Foundry, Kubernetes, and the wider Kubernetes ecosystem, including numerous projects and companies associated with the CNCF and the Cloud Foundry Foundation featured in conversations with end user clients. The CNCF, Cloud Foundry Foundation and the Linux Foundation paid for my T&amp;E to a significant number of pre-pandemic events.</p><p>Paying for T&amp;E is common practice for analysts attending vendor and foundation events.</p><p>The opinions posted in this piece are entirely my own.</p><h3>Edits</h3><p>Clarified foundation definition thanks to a comment from <a href="https://twitter.com/_msw_/status/1695805977977852192">Matthew Wilson.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ee79659a0b54" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On Logos, References, Companies and Analysts]]></title>
            <link>https://medium.com/@fintanr/on-logos-references-companies-and-analysts-972d7c0a4921?source=rss-45656b37e1dd------2</link>
            <guid isPermaLink="false">https://medium.com/p/972d7c0a4921</guid>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[analyst-relations]]></category>
            <category><![CDATA[technology-strategy]]></category>
            <category><![CDATA[competitive-intelligence]]></category>
            <category><![CDATA[customer-references]]></category>
            <dc:creator><![CDATA[Fintan Ryan]]></dc:creator>
            <pubDate>Sat, 11 Jun 2022 20:10:12 GMT</pubDate>
            <atom:updated>2024-10-15T09:48:03.427Z</atom:updated>
            <content:encoded><![CDATA[<p>Company logos are used, particularly by start-ups, to lend a product or project extra credibility. However, not all displayed logos are equal. A full reference customer is markedly different to a logo added because someone is experimenting with a product in an innovation project. This can lead to significant and often unseen credibility issues.</p><p>How as a vendor should you approach adding logos and a company acquiring new technology approach evaluating their credibility?</p><p>Last week I commented on twitter:</p><figure><img alt="Picture of tweet on customer references" src="https://cdn-images-1.medium.com/max/1024/1*jgCAl49XygiWlKiIq-UV4A.png" /></figure><p>There is more nuance than a single tweet allows. As several people pointed out, the proverbial lawsuit rarely happens. The lawyers’ letters absolutely do.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZvjZjIWg45g0SPtEXFx9BQ.png" /></figure><p>There are 4 Types of Logos:</p><ul><li><strong>Customer References</strong>: these are full on case studies where both the customer in question and the vendor have gone through a writing, publication and review cycle. Legal and marketing on both sides will have approved the use of the logo. Press, analysts and prospective customers will often speak directly to such reference customers.</li><li><strong>Customer Approved Logo</strong>: these are instances where a customer logo is displayed, for example in a keynote speech, but there are very few additional details. Legal and marketing on both sides will have approved the use of the logo. Press, analysts and prospective customers may manage to speak to such reference customers, but it generally takes some persistence.</li><li><strong>Informal Approval Logo</strong>: these are the most problematic of all logos. Someone somewhere has said “sure, use our logo”, but no formal approval has been given. In this scenario it is very likely that the logo company’s marketing and legal teams have no idea that this informal approval has occurred. When a follow up question is asked no one from the logo owner is available to confirm, deny or comment on their usage of the vendors product.</li><li><strong>Word of Mouth Logo</strong>: these are the logos we most commonly see with open-source projects. A company is using the project, someone has given a talk at a conference or meetup, been on a mailing list asking about a feature or is an active contributor. At an open-source project level these logos are fine. Where an issue can arise is when a vendor starts to use the company logos to advertise their commercial offering.</li></ul><p>Now where do analysts play into all of this? Analysts advising on purchasing decisions are frequently asked by their clients “can you introduce me to another customer of vendor x”. The analyst duly declines as it would be a breach of confidentiality.</p><p>However, the analyst may be able to do is point the client at a validated public reference — that is a company logo the analyst has confirmed independently of any vendor pitches or marketing as being true.</p><p>If there is no reference that can be validated? As a vendor, particularly as a start-up, you are now in a position where a potential client is asking an analyst, someone they view as being independent, if they are aware of other companies that they can talk to as they finalise their purchasing decision (and to be clear this question is always relatively late in the sales cycle). The analyst is not able to suggest anything.</p><p>The informal approval logo is always risky. Companies invest a huge amount of capital into their brand and reputation. For companies where impartiality is of critical importance to their business (which was the case in the logo that prompted my tweet in the first place) are particularly sensitive to how their brand is used. If you rarely, or never, see the company’s logo elsewhere think carefully about the informal approval you got to use it.</p><p>Large companies can, and do, use start-ups as a means of negotiation. If you are a start-up and you think you have a customer logo you can add, take a little time and make sure you really can use it. It will be worth the time in the long run.</p><p><em>Updates: Oct 15th 2024, updated embedded tweet to image as embedding no longer works here 🤷‍♂</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=972d7c0a4921" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>