Food retail: supermarket samples. Cheese cut in small cubes. Sausage on a cocktail stick. Free. No commitment. Just to taste. The food industry discovered in the 20th century that physical product experience converts better than any advertising. Once you have tasted, the need exists. It did not exist before.

Video game industry: the free-to-play model. The game is free. Progression is free. Until the game is designed to create a frustration only a purchase resolves. Loot boxes, slowly recharging "energy," levels blocked before a paywall — same principle: free sample, paid friction. The European Union began regulating these practices in 2022.

Pharmaceutical industry: sample medicines distributed to doctors. Free for the patient in the first months. When the prescription follows, the molecule is patented and the generic does not yet exist. The medical need is real — but it was created by free initial access.

AWS · GCP · Azure: Free Tier. Startup Credit. AWS Educate. Free Ingress. Same principle. Same mechanic. Same economic structure. The only difference: the product is not food, entertainment, or medical. It is digital infrastructure. But the sequence is identical: free sample → creation of need → functional dependency → monetisation of the impossibility of exit.

Bare-Metal has no Free Tier. No Startup Credit. No free Ingress. It costs from day one — electricity, rack, maintenance, competent staff. This absence of a sample is often cited as a disadvantage: "cloud is easier to start." Correct. And that is precisely why Bare-Metal creates no functional dependency. A product that costs from day one has no need to make you dependent — you have already made your decision in full knowledge of cost. It has nothing to offer you for free. It does not need to push you through a tipping threshold. It has no exit friction because there is no exit — you own the hardware.

Not all industries adopted the sample mechanic. The craftsman invoices from the first cut of the chisel. The architect charges fees from the first sketch. The independent consultant sends an invoice from the first call. These professionals have no Free Tier because they do not need one — their value is visible without a free sample.

The sovereign managed service provider who offers services to a client is in the same position: it invoices from day one. It cannot offer 12 free months because it does not have Amazon's financial reserves. But this constraint is also its freedom: it does not need to create dependency to retain clients. It retains them because it serves them well.

The Sunk Cost Fallacy (Thaler 1980, Kahneman 2011) is one of the most robust and universal cognitive biases: the tendency to continue a commitment not because it is rational to continue, but because one has already invested non-recoverable resources. Spectators watch a bad film to the end because they paid for the ticket. States continue lost wars because they have already invested soldiers. CIOs continue paying egress fees because they have already invested five years of their career in the cloud migration.

This bias is particularly powerful when past investment is public and documented. And cloud migrations are public — they are the subject of LinkedIn posts, conferences, use cases published on the vendor's website, internal testimonials. The CIO who evangelised cloud for five years has not only invested time and money. They have invested their professional reputation.

The CIO concerned has typically: published LinkedIn posts on the successful migration · presented the use case at conference · received a promotion or internal recognition linked to the digital transformation · convinced their CEO and board that cloud was the right decision · trained their teams on AWS/GCP certifications.

Five years later, they read the Dindon corpus. The figures are correct. The 7.5x bare-metal vs cloud ratio is verifiable. Terms §14.12 are in their contracts. They understand. And they cannot retreat — not because they cannot calculate the TCO, but because retreating means publicly admitting that five years of LinkedIn posts were a mistake. The fear of losing face before their CEO and peers is stronger than economic rationality. This is sunk cost operating at its maximum.

In all industries documented in Section 1, the sample creates functional dependency — but does not modify the consumer's structure. A cheese sample creates a desire for cheese. It does not transform your digestive system to be able only to ingest that precise cheese. A sample medicine creates a treatment need. It does not reconfigure your biology to make your body incompatible with other molecules.

The cloud sample does something fundamentally different: it modifies the very structure of the product you build. When a developer builds on AWS Free Tier with Lambda + DynamoDB + API Gateway + SQS + Cognito + CloudFront, they are not building an application that runs on AWS. They are building an application that can only run on AWS. The architecture becomes biologically incompatible with any other environment.

Each nested managed service is an additional atom of captivity. Lambda triggering SQS triggering another Lambda writing to DynamoDB with a Global Secondary Index read by an API Gateway with a Cognito authorizer — each link in this chain is a service that does not exist outside AWS in this exact form. The entire chain is proprietary. Migrating this system to bare-metal or another vendor is not a migration — it is a total rewrite.

Cloud-Washing (MU'ALLAQA IV) presents this complexity as modernity. The terms "serverless," "event-driven," "fully managed," "cloud-native" are modernity labels applied to what is in reality artificial complexity — an architecture designed not to solve a technical problem but to make exit impossible.

"Can this component run outside AWS without a rewrite?"

If the answer is no — it is artificial complexity, not modernity. The question does not condemn using the service. It requires a conscious decision: I choose this service knowing it ties me to AWS. That is a sovereign decision. What Free Tier prevents is this decision being made consciously — because free-ness anaesthetises judgment on real costs, including the cost of architectural captivity.

The developer who asks this question before each managed service does what The Maths Teacher's Bag teaches the student: see the physical reality behind the abstract symbol. The managed service is the symbol. Architectural captivity is the physical reality.