In this article:

• What Does Varoufakis Mean by Technofeudalism and Cloud Capital
• What Does Cloud Capital Own That Traditional Capital Does Not
• How Does the Feudal Dependency Show Up in Daily SaaS Operations
• How Does Dependency on SaaS Accumulate Without Anyone Noticing
• Why Does Market Competition Fail to Correct Technofeudal Extraction
• Frequently Asked Questions
• What is technofeudalism according to Yanis Varoufakis?
• How is SaaS dependency similar to feudal land dependency?
• How does private equity make technofeudalism worse in SaaS?
• References

Technofeudalism, as Yanis Varoufakis defines it in his 2023 book of the same name, is not a metaphor or a rhetorical flourish. It is a precise economic description of a structural shift that has been underway for two decades and is now the dominant mode of value extraction in the digital economy. The argument is this: capitalism, which extracted profit by producing goods and services in competitive markets, has been displaced at the commanding heights of the economy by something different, a system in which cloud capital extracts rent from every transaction, every workflow, and every piece of data that passes through infrastructure it owns and others depend on. For digital agencies and small businesses running their operations on a stack of SaaS subscriptions, this is not an abstract observation about macroeconomics. It is a description of their monthly billing cycle.

The distinction Varoufakis draws between capital and cloud capital is the analytical key. Traditional capital produces things: a factory produces goods, a firm produces services, a software company produces software that customers license and run. The profit comes from production and from competition among producers. Cloud capital does something different. It positions itself as the necessary infrastructure through which others produce, then charges rent for access to that infrastructure regardless of whether the infrastructure itself improves. The agency whose entire client operation runs through a platform it does not control, the merchant whose store depends on Shopify's payment processing, the small business whose customer communication lives inside Mailchimp's systems: these are not market participants in a competitive sense. They are tenants.

Cloud capital does not own the agency's expertise. It does not own the merchant's product knowledge, the consultant's client relationships, or the judgment that comes from years of operational experience. What it owns is the infrastructure through which that expertise is expressed and stored: the platform where data accumulates, the system where history compounds, the environment where work product is generated and delivered. It owns the land, not the labor. But because the labor has been performed on the land long enough that separating the two is prohibitively costly, it can charge for both.

This is precisely the feudal structure Varoufakis is describing. The feudal lord did not own the serf's agricultural knowledge or the serf's relationship with the soil they had farmed for generations. The lord owned the land, which was the infrastructure through which agricultural production occurred. The serf's dependency on that land to perform their labor gave the lord the leverage to extract tribute without providing proportional value in return. The platform that holds years of accumulated operational data in a format the user cannot meaningfully export owns something analogous to land. The user's switching cost is the contemporary equivalent of the serf's inability to simply move to a different field.

Shopify offers a useful illustration of this mechanism without any judgment on the product's genuine strengths. The platform solved a real problem: it made building an online store accessible to merchants who could not build their own. The features are well-designed, the ecosystem is substantial, and the tooling has genuinely helped independent merchants compete in a market dominated by large retailers. That product quality is real and should be acknowledged. The structural relationship that product quality creates is also real: a merchant who has built years of product listings, customer relationships, order history, and store customizations inside Shopify's infrastructure has accumulated switching costs that give Shopify pricing leverage that has nothing to do with whether any individual pricing decision is fair or reasonable.

The feudal dependency shows up in specific, observable ways. It shows up when a pricing restructure moves a feature built into existing workflows into a higher tier, not because the feature became more expensive to produce but because the user's dependency on it became legible to the platform's pricing team. It shows up when an API that supported third-party integrations gets restricted or deprecated, forcing users back inside the platform's native workflow. It shows up when years of operational data cannot be exported in a format that preserves its analytical value, making departure from the platform economically equivalent to starting over.

Each of these is a rent increase. Each is executed without competitive consequence because the switching cost the platform has accumulated makes the cost of leaving higher than the cost of paying the new rate. The small business that has used the same email marketing platform since 2015 has not built a business asset inside that platform. It has improved the landlord's land. The improvement is real, the labor was genuine, and the value compounds over time. None of it belongs to the business in any operationally meaningful sense.

Mailchimp's trajectory after the Intuit acquisition illustrates this cleanly. The product that freelancers and small businesses adopted because it was genuinely the most accessible email marketing tool available did not stop working after the acquisition. The features remained functional. What changed was the pricing structure and the tier architecture, which progressively repositioned the platform toward mid-market and enterprise customers and away from the small business segment that built its reputation. The product quality that generated the lock-in and the pricing strategy that exploited it are two separate things that are structurally connected to each other.

The technofeudal dependency does not arrive fully formed. It accumulates incrementally, through individually rational decisions that aggregate into structural capture. A business adopts a tool because it solves a real problem and the price is proportional to the value. The tool works. Operations improve. Workflows build around the tool's outputs. A year passes. The tool now holds twelve months of operational data that contextualizes everything the business does.

At this point the switching cost has changed character. In month one, switching tools cost the price of learning a new interface and migrating some settings. In month thirteen, switching costs the loss of baseline data that operations depend on. The platform did not change. The dependency did. And the platform's pricing team, which watches churn data carefully, knows exactly when the switching cost crosses the threshold that makes price increases safe to execute.

This is the mechanism Varoufakis is describing at the macro level, playing out at the operational level of every business that has built its workflow around infrastructure it does not control. The platform earns the dependency by being genuinely useful in phase one. It exploits the dependency by raising prices in phase three. The intervening period, during which the platform is still good and the prices are still reasonable, is the phase during which the land is being enclosed. The enclosure is invisible while it is happening. It becomes visible when you try to leave.

The standard response to the technofeudal diagnosis is that competition will correct it. If one platform extracts too aggressively, a competitor will offer better prices and the market will rebalance. This response misunderstands what makes cloud capital different from traditional capital. In a competitive market for goods or services, the customer can switch producers without losing the value accumulated through prior purchases. A restaurant that raises its prices too high loses customers to competitors offering comparable meals. The customer does not lose their appetite or their knowledge of good food by switching restaurants.

In the technofeudal model, switching producers means losing the accumulated value stored on the platform's infrastructure. The business that leaves a SaaS platform does not take its operational history with it. It leaves that history behind and starts accumulating new history on a competitor's platform, which is now in phase one of its own enshittification arc. The switching cost is not the price of learning a new interface. It is the price of losing years of compounding data. That cost is not reduced by competition. It is maintained by the architecture of dependency the platform built during its phase one, regardless of what competitors charge.

Varoufakis's argument is that this structural condition, where the accumulated value of users' labor is trapped inside private infrastructure and cannot be transferred to competing providers, represents the end of competitive market dynamics at the level of digital infrastructure. Not the weakening of competition. The end of it. The market for SaaS is not a competitive market in any economically meaningful sense. It is a set of fiefdoms competing for new tenants while the existing tenant base pays whatever rent the lord sets.

Understanding the dependency as technofeudal rather than merely inconvenient clarifies what the alternative requires. It is not finding a better SaaS platform with fairer pricing. Better pricing in phase one does not change what phase three looks like. The alternative requires a different infrastructure relationship: one in which the accumulated value of operational work is stored on infrastructure the business controls, in formats it can read and migrate, governed by its own decisions rather than the platform's pricing team.

Self-hosted infrastructure is the most direct expression of this alternative at the operational level. The business that runs its tooling on infrastructure it controls, with data in a database it owns, has changed the infrastructure relationship from feudal to sovereign. The data compounds inside the business's own asset base rather than inside the platform's. The switching cost for any individual component drops to the cost of migrating a database rather than the cost of abandoning years of accumulated operational intelligence.

This is not a return to some pre-cloud simplicity. It is a specific, contemporary response to a specific, contemporary form of economic extraction. Varoufakis names the system. The self-hosted alternative names the response. The connection between the two is not incidental. Understanding why you are paying cloud rent is the precondition for deciding to stop.

Varoufakis defines technofeudalism as the replacement of market capitalism with a system in which cloud capital extracts rent from every transaction and workflow that passes through infrastructure it controls. Unlike traditional capital which profits from producing goods, cloud capital profits from taxing the infrastructure others must use to produce anything.

In feudalism, serfs improved land they did not own and paid tribute to the lord who did. In SaaS, businesses generate operational data and workflow value on infrastructure they do not control and pay monthly fees to the platform that does. Cancel the subscription and the accumulated asset disappears. what paying cloud rent looks like in operational terms.

Private equity acquires platforms specifically to monetize accumulated lock-in rather than to improve the product. The acquisition does not change what the platform does. It changes who captures the extraction and optimizes how efficiently it is done. how the private equity SaaS rollup works and what it means for users.

Varoufakis, Yanis. Technofeudalism: What Killed Capitalism. Bodley Head, 2023.

Varoufakis, Yanis. yanisvaroufakis.eu.

Doctorow, Cory. Pluralistic. pluralistic.net.

Intuit Inc. "Intuit Completes Acquisition of Mailchimp." Press release. November 2021.