Fisker Ocean Owners Built an Open-Source Car Company After Bankruptcy

When Fisker Inc. filed for Chapter 11 bankruptcy in June 2024, it left roughly 11,000 Ocean SUV owners holding the keys to vehicles that cost them $40,000 to $70,000 — and that were rapidly losing the software brains that made them work. No more over-the-air updates. No more connected services. No more warranty. The manufacturer was dead.

What happened next is one of the most remarkable stories in the history of the electric vehicle industry. Instead of accepting that their cars would become rolling paperweights, Fisker Ocean owners organized, reverse-engineered their vehicles' proprietary software, hacked into CAN bus networks, built open-source tools on GitHub, and effectively stood up a volunteer-run open-sourced car company from the ashes of Fisker.

What Happened When Fisker Went Bankrupt

The speed of Fisker's collapse was staggering. The company, once touted as a Tesla rival that had secured over 31,000 Ocean reservations totaling $1.7 billion in potential revenue, produced just 11,000 vehicles before the money ran out. Bankruptcy filings revealed more than $1 billion in debts.

The core problem was architectural. Fisker had built what Cory Doctorow pointedly called a "software-based car." Virtually every subsystem in the Ocean — brakes, airbags, shifting, battery management, door locks — needed to periodically connect with Fisker's cloud servers for diagnostics or regular operations. When those servers went dark, the cars didn't just lose their infotainment screens. They lost critical functionality.

4,000 Strangers Build a Car Company

Within months of the bankruptcy filing, thousands of Ocean owners formed the Fisker Owners Association (FOA) — a nonprofit that quickly grew to 4,000 members and began operating as something between a car club, a tech startup, and an independent automaker.

The FOA accomplished things that would make most startups jealous:

• Reverse-engineered software patches — hired independent tech experts to decode Fisker's proprietary firmware
• Bulk parts procurement — negotiated key fob prices down from ~$1,000 each through coordinated group buys
• Free global key fob pairing events — saving each owner $100–$250
• "Flying Doctors" program (Europe) — a mobile repair network where technically skilled members travel to help other owners
• Insurance preservation — convinced several insurers to maintain coverage for a vehicle whose manufacturer no longer existed
• Court representation — pushed to ensure safety recalls were included in bankruptcy proceedings

In other words, they were doing the work that Fisker left undone.

The Open-Source Arsenal on GitHub

The technical work happening beneath the surface is where this story gets truly fascinating. What started as desperate troubleshooting has evolved into a genuine open-source ecosystem around the Fisker Ocean.

Home Assistant Integration

A developer named MichaelOE reverse-engineered the API behind Fisker's official "My Fisker" mobile app and built a Home Assistant integration that exposes every cloud API value as a sensor — with all the app's buttons available as Home Assistant controls. The project has 135 commits, 20 releases, and is licensed under Apache 2.0.

CAN Bus Reverse Engineering

CAN bus files for the Fisker Ocean have been published on GitHub, including DBC files for CAN viewer filtering and processing. The Ocean runs multiple CAN buses — CCAN, PTCAN, Inverter CAN, and BCAN, all at 500kbps — and community members have been systematically mapping them.

DIY Diagnostics

Majd Srour published a multi-part series documenting how to sniff CAN traffic and decode Diagnostic Trouble Codes on the Ocean. The goal: put diagnostic capabilities into mobile apps so owners can run their own DTC scans, instead of relying on dealer tools that no longer exist for a company that no longer exists.

Why Vitalik Buterin Called for Open-Source Cars

Ethereum co-founder Vitalik Buterin captured the mood on X in July 2024:

"We really need much more open source in the auto industry. Really sad that 'if the manufacturer disappears, the car is useless now' has seemingly so quickly become a default."

He was right. But what neither Buterin nor anyone else could have predicted was what the owners would do about it. The Fisker Ocean story has become a real-world proof of concept for open-source automotive — not as an idealistic philosophy, but as a survival strategy.

Lessons for the Auto Industry

The Fisker saga exposes several critical issues that the entire auto industry needs to confront:

The right to repair movement has argued for years that consumers should be able to fix what they own. The Fisker case takes that argument further: when the manufacturer dies, the community should be able to keep the product alive.

What's Next for the Fisker Community

The community's path hasn't been smooth. A promising deal with American Lease — which spent $2.5 million to acquire Fisker's source code and cloud services — fell through when it was never formally signed. The relationship collapsed over cost-sharing disputes.

But the FOA continues to push forward. On community forums, there are active discussions about whether it's feasible to fully open-source Ocean OS. The consensus: safety-critical systems developed by Magna and other suppliers can't simply be forked like a web application. But the infotainment layer, connectivity stack, and diagnostics are all fair game.

The Fisker Ocean story isn't just about one failed car company. It's a blueprint for what happens when ownership meets open source — and a warning to every automaker building cloud-dependent, walled-garden vehicles.

Source: Electrek | Trending on Hacker News