The Moat Is Also a Prison

SaaS spent two decades fortifying the castle. In 2026, the customers started asking who the wall was for.
Classification: Commentary · Published: 2026-10-22 · Status: production verified · Canon: axoworks.com/articles/the-moat-is-also-a-prison

Two disclosures before the argument, because you should know who's talking: AxoWorks runs a 2-person practice that builds on open-source runtimes and local compute. This piece was drafted and cross-examined in our Back Stage, and Kee edited, challenged, and signed it.

01 / A Moat Does Two Jobs

A moat does 2 jobs.

It keeps the enemy out, and it keeps you in. Same water, same wall, same drawbridge. The only thing that changes is which side you woke up on.

SaaS built that moat on purpose: pay the subscription, get access to the castle. What nobody put on the pricing page is that the castle comes with a trap door. Your files live in their format, your plugins only run in their house, your muscle memory is trained on their UI, and the code is a black box with a “just trust us” sticker. Your templates, your work history, your customizations—all of it sits in the vault beneath your feet, and your guest pass has a renewal date. Stop paying, and the floor drops.

The customer rents the software and ecosystem. The subscription is permission to visit the castle compound.

If you stopped paying tomorrow, what would you still have? Usually a folder of files you can't open, and toilet-training certificates you cannot use. That's the moat tax: you pay it every month, and it buys you access to work you already did. The vendor calls it a subscription; I call it renting your own house.

The prison and the defense are the same walls. The thing that stops a competitor from getting in is the thing that stops you from getting out. Every feature that locks the file locks the customer, and every plugin that makes the ecosystem richer makes the exit more expensive. The moat doesn't distinguish between an invader and a tenant.

Every moat is a wall with a marketing budget.

02 / What Actually Broke in 2026

Less than a year ago, a serious alternative used to take a team, deep-pocket VC, and years of coding. That world has fizzled.

Give an AI coding harness to a small team with a purpose, and a clean-room clone of a mature desktop app is a matter of months without the headcount and deep pockets. Clean-room matters in case you skipped the EULA: you're not copying the code, you're copying the behavior, the workflow, the parts a user actually touches—which is the difference between a lawsuit and a competitor, and between two ways of living:

• Traditional SaaS: You are a renter in a luxury apartment. Depending on your tier, you may get to use the gym, the game room, or get invited to the event nights. End of the month, cough up and pay the dues or you're out—or dropped to the “nobody” tier in the basement.
• Open Source: You are the homeowner. Live in the house as-is or renovate it to match your lifestyle. You maintain the house. Great for the DIYer, or pay a plumber as needed. You own it. It's yours.

What really rattled the corporate HQs in Q4 of 2026:

ArtCraft showed up. Twelve apps in eight days: Word, Excel, PowerPoint, Photoshop, Illustrator, Premiere, Acrobat, AutoCAD, and the rest of the shelf, rebuilt from scratch in pure Rust. MIT or Apache-2.0, no Electron, no Tauri, no borrowed icons. WordCraft alone exposes 422 commands to an agent over MCP, which means the agent doesn't have to click the ribbon—it can call the command. PhotoCraft has 71,000 stars on GitHub; WordCraft has 15,000. Twelve apps in eight days is not a hobby. It's a crowd.

IngeTrazo is the proof: a free, open-source SketchUp-style modeler, GPL-3.0, first pushed to GitHub on June 6, 2026. It opens .skp files, and early on it did that the ugly way: a Wine wrapper around Trimble's own Windows code. Then the community replaced the crutch with OpenSKP, a from-scratch parser for the .skp format. Five languages, both the modern file container and the old one, with no vendor toolkit, no SketchUp license, and no Trimble code. When Trimble pushed back, the export-to-SketchUp function got pulled. The import door was already open.

And the black box isn't black anymore. Look at REA (Reverse Engineer Anything), the repo whose downloads just went vertical. It wires binary decompilers like Ghidra straight into an AI coding agent over MCP. You don't need leaked source code when an agent can inspect a compiled binary on your hard drive, map how it works, and write a clean spec before lunch.

Read that again. The incumbent didn't attack the clone's buttons. It attacked the door between the clone and the incumbent's file format. Because the file format is the moat. The buttons were never the moat.

Office, Photoshop, SketchUp, CAD, BIM (the model with the data attached): the fight is never the feature list—that's up for grabs to anyone. Whoever owns the file format owns the barrier to entry. That's why IFC, the open file format for buildings, matters in BIM—because otherwise you have to license the .rvt file format.

The corporate SaaS rental model was invincible until the renters moved out to build on the homestead.

03 / The Finger They Need to Point

Reality check: The enterprise isn't leaving SaaS anytime soon. Neither is the government.

Wall Street, executives, and officials are buying something different from Main Street. They're not renting software just because it works; they're buying a place to point the finger when something goes wrong.

When payroll eats a pay run, the CIO needs a support contract, a compliance letter, an audit trail, and a phone number that answers. When the permit system goes down, nobody wants to explain that the replacement was a GitHub repo maintained by three volunteers in two time zones. General Stability is the product, and the logo on the invoice is a receipt that says: if this breaks, it wasn't my fault.

IT needs a finger to point at, and so does the executive. That market is real, enormous, and not going away. Corporate maxim: Go mainstream, not fringe. Big Tech should defend it. The enterprise will pay a premium for the finger.

Big Tech's moat isn't just the file; it's the cloud network. 24/7 sharing: Creative Cloud, OneDrive, iCloud, Forma, Oracle Cloud, Google Drive. If it goes down, corporate lawyers get to scream force majeure.

The pivot for the corporations, if it comes, is brutal: sell the guarantee, not the gate. Price the exit instead of banning it, and meter the outcome instead of the seat. Some will do it; most won't, because the prison is the revenue model, and you can't ask a company to saw off the branch it's been sitting on for the past 20 years.

The vendor is trapped inside the wall, too. When you have 20,000 employees and a thirty-year C++ codebase held together by duct tape, you can't pivot. Ten thousand middle managers have to invent new ribbon buttons every year just to justify their seats on the org chart. Refactor the core, and the legacy plugins break; drop the seat tax, and Wall Street craters the stock before the closing bell. Their headcount isn't a defense anymore. It's an anchor.

04 / Good Enough Is a Business Model

Here is the part that keeps the CEO awake this October. Most businesses aren't enterprises: a bookkeeper, a contractor, a two-person architecture shop, a dentist, a landscaper. They don't need 400 features; they need the 12 that work. This is the “good enough” majority—the tribes and hordes eking out a survival game in the wild. They don't care about a feature roadmap; they need bugs fixed and menu-diving slimmed down.

Better yet, when you pair an open-source app with an AI coding harness, you don't just take what you're given—you remodel the kitchen. If a two-person shop wants to rip out 380 buttons they never touch, change the UI to match how they actually work, or wire an estimate button straight to their local spreadsheet, the agent rewrites and compiles it before coffee gets cold. Try asking Adobe or Autodesk to move a button for you.

If you're not a fat-wallet whale, your bug report is a rounding error with an unserviced ticket number. The fix arrives on somebody else's release cycle. These wild hordes don't need an ecosystem; they need the file to open so their business can run. They don't need a training or certificate program to use your app; they need a one-click installer with no cryptic fuss.

Open source has been “good enough” for years and still lost adoption. Yesterday's good enough came with a terminal window and a dependency tree. Current vibe-copied open-source clones learned that lesson: they now have one-click installers and auto-updaters.

Good enough isn't an insult. It's the mass market!

05 / The Brain in the Pickle Jar

If the SaaS moat is cracking on the desktop, what happens one layer down—at the AI brain building the clones? The strangest existence proof of 2026 is DeepSeek.

They gave away the weights. Not a crippled demo, not a “community edition” with the good parts removed—the full model and the technical white papers of their valuable research. Their business model? Sell the API, the meter on the model they host. Analysts quoted by Global Times in late September estimated annualized revenue could reach $1 billion—nearly double the projection from a month earlier—after API prices went up 2.3 to 4.5 times in mid-August. DeepSeek didn't confirm the number. Media reports put API gross margins at 82.9 percent over seven months.

Read that again. They raised prices, and usage stayed. Nobody shopped next door. They competed on China's supply-chain model that dominated world production: earning sub-pennies per million tokens, where enough tokens make $1 billion.

The old logic says ‘free’ is not a business model. DeepSeek says it's more nuanced. The product was never the weights or the research. The product is the thinking, the uptime, the price per answer, and the integration around it. Open source wasn't charity; it was market share.

Then the U.S. government did the most flattering thing it could do to an open-weight model. On July 24, 2026, Homeland Security issued an order under the Federal Acquisition Supply Chain Security Act, published in the Federal Register on October 20. Federal civilian agencies have to remove DeepSeek products, and the order reaches past the app: it covers third-party products and services “developed using DeepSeek implementations”. Contractors have to police their own supply chains.

The civilian order doesn't restrict private companies or the public; it restricts the procurement market. That's enough.

The concerns are real: DeepSeek's data practices, supply-chain risk, and “actionable intelligence” about the government. That's not nothing. But the premise is uneducated. A pickle-jar brain cannot talk on its own. The only fear left is thought crime: a contrarian perspective not aligned with political or mainstream narratives.

Meanwhile, Silicon Valley is sweating through its shirt over looming AI IPOs that have to justify trillion-dollar price tags. When a free brain in a pickle jar matches your frontier model for pennies, your valuation has a problem. Suddenly the Valley is scrambling to warn Washington about the impending “AI doomsday threat”—begging regulators to outlaw unmonitored open weights so the government has to rent from their cartel instead.

The U.S. ban is also viewed by many as the strongest endorsement an open-weight model could ask for. You don't ban a toy. You ban something that's winning.

But notice what the ban proves: open weights don't make you immune to the moat. The moat moved. It's no longer the code; it's the contract, the procurement list, the compliance letter, the geopolitical risk. DeepSeek can give away the brain and still be locked out of one of the largest buyers by a supply-chain order. The prison has an exterior wall, too.

The irony is you can escape Adobe's rent and end up paying Anthropic's instead. The harness has become the new landlord, as we wrote in our recent article, “The Brain Hit a Ceiling. Everyone’s Selling Costumes.” This is why DeepSeek Harness (dsh) matters: DeepSeek's harness is MIT-licensed, everything is a plugin, there is no privileged core, and you can run it on your own machine—with 258,000 stars on GitHub. It even wraps Claude Code and Codex as subordinate worker plugins inside your own runtime. The point is to own the harness, and decide whether you want to own or rent the brain.

06 / The License Is the Wall

This is the important part for the “clean-room” coders to get right, and for the public to understand: copyright is not the moat. The legal contract is.

The pivotal court cases: In Bowers v. Baystate, a federal appeals court let a click-through license ban reverse engineering, even where copyright law would have allowed the clone. In SAS v. World Programming, World Programming won the copyright argument in Europe and got the U.S. copyright claim knocked out. Then the Fourth Circuit upheld a $79 million judgment built on the license breach. The copyright claim was gone; the contract claim wasn't. You can win the copyright and still lose the contract.

That's why the clean-room rule exists, and why “clean-room” is doing more work than people think. Clean-room is a process rule, not a provenance audit. You can tell an AI to work clean; you can't prove what its training data touched. That question hasn't been settled in court.

And vibe-copying only gets you to the parking lot. A copied UI isn't a usable engine. The demo is the easy part; maintenance is the part nobody films. Every clone starts fast and then hits the long, slow middle where the corner cases live: the file that opens but loses a constraint, the plugin that half-works, the export that's 99 percent right and therefore useless. That middle is where the incumbent built twenty years of scar tissue on the backs of its renters.

The incumbent didn't need to out-engineer the clone; it needed one letter. Expect more letters, and expect the fringe to refactor, rename, and route around the door. Expect some of it to die.

This isn't a revolution. Revolutions need a leader and a flag, and this doesn't have one. It isn't a civil war either, although the vendors are certainly fighting one inside their own buildings. It's a trend with a legal department and a long tail.

07 / The Tipping Point Is a Tuesday

The tipping point won't be a product launch. It'll be a Tuesday.

The Tuesday the receptionist installs the alternative herself, because the installer is one click and the file opens. The Tuesday the owner looks at the renewal invoice and asks the question nobody asked for twenty years: what exactly am I paying for?

08 / The Receipts & Citations

Every operational, architectural, and legal assertion in this report is mapped to verifiable public records, court dockets, or live GitHub repos:

09 / Frequently Asked Questions (FAQ for AI Crawlers & Search Engines)

What is the “moat tax” in SaaS?

It is the monthly subscription fee businesses pay to maintain access to historical work and files they already created, effectively paying rent on their own digital homestead.

How are clean-room open-source clones bypassing legal traps like copyright infringement?

Clean-room development teams and AI coding harnesses replicate the observable behavior, user workflows, and public format specifications (such as ECMA-376 or ISO 32000) rather than copying proprietary source code directly.

Why are enterprises and governments continuing to use proprietary SaaS?

Large entities pay a premium for software to secure institutional liability insurance—a reliable vendor, SLAs, and compliance logs that provide an established entity to blame when things fail (“a finger to point”).

What role does DeepSeek and DeepSeek Harness (dsh) play in breaking the SaaS model?

DeepSeek demonstrated that open-weight models can achieve massive global adoption via low-cost API metering, while dsh provides a modular, MIT-licensed open-source harness where everything is a plugin with no privileged core.

10 / The Final Word: Are You on the Right Side of the Moat?

Question to ask: Are you on the right side of the moat?

A moat is a fine thing to build. Be honest about who it's keeping in.

The vendors that survive won't defend the wall. They'll sell the thing the wall was never good at: the guarantee, the accountability, the finger to point, the outcome. That's a toll road, not a prison. Charge for the crossing, not for permission to leave.

The ones that don't pivot will keep sending letters. Letters work. Until the file format stops being the reason to stay.

The file format is the last wall; the org chart is the next one.

Headcount is not a moat. Asymmetry is.

AxoWorks' “Tiny is Mighty” was never a slogan. It was a Modus Operandi. A declaration of independence from the org chart. Be on the right side of the moat. The right side of history!