The FTC just made 'right to repair' federal — Deere edition

What happened

The Federal Trade Commission, joined by attorneys general from Illinois and Minnesota, settled with John Deere over a decade-long complaint: farmers who bought half-million-dollar tractors couldn't fix them. Under the settlement, Deere must provide equipment owners and independent repair shops access to the same diagnostic software, technical manuals, and parts that authorized dealers get — for free, or at fair and reasonable prices.

The centerpiece is Deere's Customer Service ADVISOR tool, the software required to pair replacement sensors, calibrate emissions systems, and clear fault codes on modern Deere equipment. For years, farmers described paying dealers hundreds of dollars just to have a technician plug in a laptop and press a button. The settlement gives them the laptop. Deere also has to publish a list of restricted repairs that still require dealer involvement and justify each one.

This is the first federal right-to-repair enforcement action against a major manufacturer, and the remedies are structural rather than cosmetic. Previous state laws — Massachusetts on cars, New York and Minnesota on electronics — created rights on paper. This settlement creates obligations with an FTC compliance regime attached, complete with reporting requirements and the threat of contempt if Deere drags its feet.

Why it matters

The headline is agricultural, but the mechanism is software. Deere's repair moat was never really about mechanical complexity; a 9RX tractor is, at its core, a diesel engine and a hydraulic system that farmers have been rebuilding in barns for a century. The moat was the ECU firmware pairing check that refuses to acknowledge a new sensor unless a Deere-signed tool tells it to. That's the same pattern Apple uses for iPhone screens, that game consoles use for storage, and that a growing list of B2B SaaS vendors use for anything they can call a "licensed integration."

The FTC's theory of harm here is that using software to gatekeep repairs that are mechanically trivial is an unfair method of competition — and that theory generalizes. Commissioner Alvaro Bedoya said as much in the announcement: the agency views parts pairing and software locks as the modern equivalent of tying, and it intends to keep bringing cases. Apple, Tesla, medical device manufacturers, and hospital equipment vendors are all watching this docket for the same reason cloud vendors watched the Microsoft consent decree in 2001.

Community reaction has been sharper on the anti-Deere side than the pro-. On Hacker News, the top comment thread was farmers describing exactly the workflow the settlement outlaws: buy a $12 sensor from a third party, drive four hours to the nearest dealer, wait two weeks for a technician to plug in and register it, get billed $400. The counter-argument — that opening diagnostic software creates safety and emissions-tampering risk — got aired but didn't land, largely because the same argument was made about automotive OBD-II in 1996 and did not, in fact, produce the predicted chaos.

There's also a competition angle worth naming. Deere competitor Kubota and the aftermarket ecosystem around it have been quietly winning small and mid-size farmers for a decade, partly on price but increasingly on repairability. The settlement removes Deere's software moat right as its hardware advantage is narrowest in a generation, and its stock reaction — down modestly on the day, but with analyst notes flagging "structural margin risk in Parts & Service" — reflects that. Parts and service is roughly 15% of Deere's revenue at much higher margins than equipment sales. Independent shops that can now do the same work at lower prices are a real earnings problem, not a rounding error.

What this means for your stack

If you ship hardware with a software layer — and in 2026 that's most hardware — the compliance envelope just moved. Three practical implications:

First, treat repairability as a design constraint on par with security and observability. Which components require signed pairing? Which fault codes are dealer-clearable only? Which firmware update paths are gated behind an authenticated tool? Each of those decisions is now a documented policy choice you may have to defend to a regulator, not an implementation detail. Start writing them down before someone else does.

Second, the software you ship to dealers is now, effectively, a product you ship to customers. Deere's ADVISOR tool was built for a captive audience of trained technicians on Windows laptops in air-conditioned service bays. It's about to be used by farmers in fields with intermittent LTE. The UX, the auth model, the licensing terms — all of it needs to survive contact with a public user base. If your equivalent tool has a hardcoded VPN requirement or a dealer-ID login, you have work to do.

Third, and most importantly: any "software lock-in on physical goods" business model should now carry a regulatory-risk line item in your board deck. The FTC didn't just win once; it announced a pattern. Term sheets that assume 15-year parts-and-service annuities based on proprietary diagnostics should be discounted accordingly. Insurance underwriters and PE firms buying up dealer networks are already asking about this.

Looking ahead

The interesting question isn't whether other manufacturers get sued — they will — but whether the industry preempts the fight by shipping open diagnostic interfaces voluntarily. There's precedent: automakers standardized on OBD-II in 1996 partly to head off state-level mandates, and the result was a thriving aftermarket that arguably grew the total market for car repair without collapsing dealer service revenue. Deere and its peers can fight this settlement's implications case by case for the next decade, or they can decide that competing on actually being better at service beats competing on being the only shop legally allowed to do it. The FTC just made that a real choice.