Adafruit vs. Flux.ai: The Open Source Trap That Just Sprung

Ladyada got a letter from Fenwick & West last month. Not the kind you frame.

Fenwick represents Flux.ai, the EDA startup that wants to make PCB design as easy as Figma. They're demanding Adafruit stop using Flux's software to design boards. The allegation? Adafruit reverse-engineered Flux's cloud platform.

Here is what most people will miss about this story: it's not about code theft. It's about the open source hardware community eating its own tail.

Flux.ai launched in 2020 with a slick browser-based PCB editor. They raised $15 million from Sequoia and others. Their pitch was simple — we'll be the Google Docs of circuit design.

But Flux built on top of KiCad's open source core. And Adafruit has been one of KiCad's biggest contributors. They've shipped thousands of boards designed in KiCad. They've written documentation, fixed bugs, pushed the project forward.

So when Flux wraps that same KiCad core in a subscription service and sends lawyers after a major contributor, something stinks.

Let me be precise about the data. Adafruit releases over 250 open source hardware designs per year. Every schematic, every layout, every BOM — it's all public on GitHub. Flux's entire business model depends on keeping user designs locked inside their cloud.

This is the tension that nobody in the open source hardware world wants to talk about. You can build your company on top of community infrastructure. You can add value with cloud features, real-time collaboration, and managed libraries. But the moment you send legal threats to the people who built the foundation you're standing on, you've revealed your hand.

Adafruit didn't steal anything. They used KiCad. KiCad is GPL-licensed. Flux's modifications to KiCad are also GPL-licensed. That's how open source works — you take, you improve, you share back.

But flux.ai wants it both ways. They want the community's contributions to build their product, and they want proprietary control over how people use their cloud platform. Those two things are fundamentally at odds.

The real question is whether Adafruit even needs Flux's platform. They've been shipping open source hardware since 2005. They have their own tooling. Their own supply chain. Their own community of 500,000+ makers who trust them.

Flux.ai has 50,000 users and a VC deadline. That's the math that explains this letter.

What's happening right now is a test case for the entire open source hardware ecosystem. If a startup can send legal threats to a major contributor and get away with it, every open source project becomes a liability. Every company that builds on community code becomes a potential target.

The counterargument is that Flux has a right to protect their IP. Their cloud platform includes proprietary collaboration features, version control, and component libraries that they invested millions to build. Fair enough.

But you don't send lawyers after your own user base. You don't threaten the people who made your product possible in the first place. That's not business strategy. That's desperation.

I expect this to settle quietly within 60 days. Fenwick knows they've overplayed their hand. Adafruit knows they have the moral high ground and the community behind them.

But the damage is already done. Every open source hardware company will now ask the same question: is the next legal threat coming for me? And that fear is exactly what kills the collaborative spirit that made all of this work in the first place.

The future belongs to the companies that can build sustainable businesses without poisoning the well they drink from. So far, Flux.ai hasn't learned that lesson. Let's hope they learn it before the community learns to stop trusting them entirely.