The editorial argues this is the first time a U.S. federal agency has treated locking diagnostic tools behind an authentication wall as an antitrust violation rather than legitimate business practice. That framing has implications for every category of software-locked hardware — medical devices, industrial robotics, EVs — not just agriculture.
The editorial contrasts this settlement with Deere's 2023 MOU with the Farm Bureau, which was criticized as toothless because it let Deere define 'safety features' as anything they didn't want farmers touching. This deal includes federal enforcement, compliance reporting, and FRAND terms with no such carve-out.
The editorial credits nearly a decade of pressure — farmers organizing, Cory Doctorow's persistent writing, and Nebraska's near-miss right-to-repair law in 2021 — as the groundwork that made federal action possible. The settlement is framed as the payoff of a long grassroots and journalistic campaign, not a spontaneous regulatory decision.
By submitting the AP story to Hacker News where it drew 525 points and 104 comments, djoldman surfaced the settlement as a milestone worth celebrating in the developer community. The high engagement signals broad agreement that this outcome vindicates the years of right-to-repair advocacy.
The Federal Trade Commission announced a settlement with Deere & Company that finally forces the agricultural giant to let farmers — and independent repair shops — access the same diagnostic software, tools, and technical documentation Deere's own dealer network has monopolized for years. The core of the deal: Deere must make its Customer Service ADVISOR software available to equipment owners and independent technicians on 'fair, reasonable, and non-discriminatory terms.'
The FTC's complaint, filed in January 2025 and now resolved, alleged that Deere's practice of restricting repair software to authorized dealers constituted an unfair method of competition under Section 5 of the FTC Act. Farmers were routinely quoted five-figure repair bills and days of downtime during harvest windows for problems that amounted to clearing an error code — a diagnostic gesture that would take an independent mechanic ten minutes if they could plug in.
The settlement follows nearly a decade of pressure. Farmers organized. Cory Doctorow wrote about it for years. Nebraska nearly passed a state right-to-repair law in 2021. Deere signed a voluntary memorandum of understanding with the American Farm Bureau Federation in 2023 that was widely criticized as toothless — it explicitly denied farmers the right to modify embedded software or bypass 'safety features,' which was exactly the lock the dealers had been using. This settlement has teeth the MOU lacked: federal enforcement, compliance reporting, and no carve-out that lets Deere define 'safety' as 'anything we don't want you touching.'
For developers, this story is not really about tractors. It is the first time a U.S. federal agency has treated 'we locked the diagnostic tool behind an authentication wall' as an antitrust violation rather than a legitimate business practice. That framing has implications for every category of software-locked hardware — medical devices, industrial robotics, EV service, prosumer 3D printers, enterprise networking gear, and yes, consumer electronics.
The technical pattern Deere used will be familiar to anyone who has ever reverse-engineered a piece of hardware: signed firmware, an authenticated CAN-bus handshake, a proprietary diagnostic protocol layered over standard J1939, and a licensing gate on the PC-side tool. Each layer is defensible in isolation as a 'security feature.' Stacked, they constitute a moat that has nothing to do with security and everything to do with capturing the aftermarket. The FTC's willingness to look through the stack and call it what it is — market power dressed up in TLS — is the actual precedent here.
Compare this to the parallel fight in consumer tech. Apple's Self Service Repair program launched in 2022 with genuine-parts pricing that made third-party repair uneconomic on purpose. Tesla's service manuals technically exist but the diagnostic dongle is dealer-only. John Deere was actually further along on paper than either — the MOU, the promises, the 'Customer Service ADVISOR' branding suggesting the customer had any service authority at all. What the FTC action shows is that voluntary commitments in this space are worth exactly nothing without an enforcement mechanism, and the industry has just been shown one.
The farmer community's response has been mixed and worth reading. Kevin Kenney, who has been one of the most persistent voices on this, welcomed the settlement but flagged that the real fight is over software modifications — being able to actually change engine tunes, bypass emissions restrictions that Deere uses to force costly repairs, and run non-Deere implements without a handshake refusal. The settlement gets farmers diagnostics. It does not get them the source code, and it does not force interoperability with third-party attachments. That gap will define the next round.
If you build or sell hardware with authenticated diagnostics, service tooling, or firmware-locked features, the risk calculus just changed. The 'dealer-only tool' revenue model — where the physical device is sold at margin but the service ecosystem is a recurring rent — now carries federal antitrust exposure, not just brand risk. The specific FTC theory here (Section 5 unfair method of competition) does not require proving consumer harm in the traditional Sherman Act sense. It only requires that the restriction is unreasonable and anticompetitive on its face. That is a much lower bar, and the Commission has now shown it will use it.
Practical implications for engineering teams: expect procurement and compliance to start asking whether your diagnostic tooling is available on FRAND terms. Expect open-source alternatives to your proprietary service software to gain legal cover — the Deere community's Kubernetes-of-tractors project, farmOS, and the various CAN-bus reverse-engineering efforts around Right to Repair Association's work now operate in a regulatory environment that treats them as pro-competitive rather than as a lawsuit target. If your product line depends on gating diagnostics, start modeling what the business looks like when you have to sell that access at cost.
There is also a straightforward developer opportunity here. The market for third-party diagnostic tooling, repair-shop management software, and firmware-adjacent utilities for agricultural equipment has been artificially suppressed for a decade by legal risk. That risk just dropped. The install base is enormous — hundreds of thousands of Deere machines in the field, each with a serviceable lifetime measured in decades — and the incumbent tooling is, by all accounts from actual mechanics, terrible.
The FTC settlement is a template, not a finale. Expect the next enforcement action in this pattern to land on a consumer electronics vendor or a medical device maker within eighteen months — the theory has been proven and the political appetite is bipartisan. The interesting question for developers is not whether right-to-repair wins the broader war but which categories fall next, and whether any vendor gets ahead of it by opening diagnostics voluntarily under commercially sane terms before the FTC arrives with a consent decree. Betting markets, if they existed for this, would be short on the incumbents.
"Right to repair" isn't some kind of little negotiated contract fiddling. A company can't agree to a 5-year right to repair. Right to repair is a normal freedom, like speech, like using everyday objects you buy or make, generally walking around, meeting people, etc. Don't le
I've learned that I'm just not cynical enough. Here's the relevant Peter Girnus post[1], he tells the underlying truth through satire. 10 years. We report our compliance every 60 days, then once a year, which is to say we have turned handing you your own machine into a paperwork sched
Great news, the fine is so small doesn’t matter, but curing the wrong does. My hope is this standard will apply to modern cars as well, repair manuals and the software tools to interact with the cars are also heavily restricted by the manufacturers.
Bananas that stuff like this needs to get litigated in our society - if you asked 100 random people "should farmers be able to repair their equipment", you would get 100 yes's.
Top 10 dev stories every morning at 8am UTC. AI-curated. Retro terminal HTML email.
Shout out to Louis Rossmann for doing a ton of work on Right to repair.He started a website called Consumer Rights Wiki to document anti-consumer practices.https://consumerrights.wiki/w/Main_PageHe's also involved with FULU Foundation which has a bounty of 25k to get Ring ca