After EV maker Fisker's collapse, ~4,000 car owners formed a nonprofit to keep their cars working by reverse-engineering software and building open-source tools
When Fisker Inc. filed for Chapter 11 bankruptcy in June 2024, it left roughly 11,000 Ocean SUV owners holding the keys to vehicles …Forums:Hacker News,r/InterstellarKinetics, andSlashdotForums:Hacker News:Fisker went bankrupt and owners built an open source car company from the ashesr/InterstellarKinetics:EXCLUSIVE: Fisker Took $70,000 From 11,000 People Then Went Bankrupt and Vanished, So the Owners Taught Themselves to Reverse-Engineer a Car …Slashdot:How Owners of EVs from Bankrupt Fisker Sa
Context & Ripple Effects
Related coverage has repeatedly treated vehicle software as an operational dependency rather than a peripheral feature: Volkswagen’s ID.3 problems prompted a software-business reset, while GM paused Blazer EV sales to address software faults. Fisker’s bankruptcy turns that dependency into an ownership-continuity problem.
The relevant contrast is between an automaker-led software recovery and a customer-led one. With Fisker no longer providing the normal support path, a portion of Ocean owners has organized to preserve access to the software needed to maintain their vehicles.
First-order effects
- The nonprofit gives roughly 4,000 participating Fisker owners a shared channel for reverse-engineering vehicle software and developing open-source maintenance tools after the manufacturer’s collapse.
- Fisker Ocean owners are less wholly dependent on a defunct company’s software infrastructure for the specific functions and repairs the community can document or support.
Second-order effects
- Independent repairers and service providers may gain a clearer route to work on Oceans if the nonprofit’s tools and documentation are usable beyond the core member group.
- The episode raises the practical importance of software access in the residual value and serviceability of EVs from financially fragile manufacturers; buyers and fleet operators may weigh that risk more explicitly.
Third-order effects
- If similar owner efforts prove sustainable, software-defined vehicles could develop a stronger aftermarket maintenance layer, resembling the role independent repair ecosystems play for conventional cars.
- The case reinforces pressure for durable access to diagnostic, update, and repair capabilities when an automaker exits the market, though community-built tooling is not a substitute for every manufacturer-controlled service.
The trend: This is one data point in the shift from automaker-controlled vehicle software toward a broader fight over whether software-defined cars remain repairable and usable after the original vendor fails.