From Bankruptcy to Community Ownership: The Fisker Ocean Owners' Open-Source Revolt

When Fisker Inc. collapsed under Chapter 11 bankruptcy in mid-2024, approximately 11,000 owners of the Ocean SUV faced a grim reality: their $40,000–$70,000 vehicles were losing the digital infrastructure that made them drivable. But rather than resigning themselves to worthless machinery, these owners launched an unprecedented grassroots movement. They reverse-engineered proprietary systems, hacked into CAN bus networks, and built open-source tools — effectively creating a volunteer-run car company from the wreckage. Below are the key questions and answers about this remarkable story.

What exactly happened to Fisker Inc. in June 2024?

Fisker Inc., the electric vehicle startup behind the Ocean SUV, filed for Chapter 11 bankruptcy in June 2024. The company had been struggling with production delays, cash flow issues, and quality control problems. The bankruptcy filing meant the manufacturer ceased operations almost entirely, leaving no official support for its vehicles. This was not a simple restructuring; Fisker essentially dissolved, abandoning its customer base. The court process would eventually liquidate assets, but for owners, the immediate effect was a total loss of warranty coverage, over-the-air updates, and connected services — the very software brain that kept the Ocean functional.

How many owners were affected and what did they pay?

Roughly 11,000 Fisker Ocean SUVs were in the hands of customers at the time of the bankruptcy. Purchase prices ranged from $40,000 to $70,000, depending on trim and options. Many owners had also leased their vehicles. For context, this represented a combined value of hundreds of millions of dollars. These were not early pre-order deposits; they were fully delivered, road-registered cars that suddenly lost their manufacturer support. Owners feared their vehicles would become digital bricks — unable to receive critical software patches, navigation updates, or even basic functions like smartphone app access.

What specific problems did owners face immediately after bankruptcy?

Within days of the bankruptcy filing, Ocean owners encountered several urgent issues:

• No over-the-air updates: Future software improvements or bug fixes were impossible. Existing bugs — such as battery management glitches or infotainment freezes — remained permanent.
• Connected services shut down: Features like remote climate control, live traffic, and emergency roadside assistance stopped working because the cloud servers went dark.
• Warranty void: Any mechanical or electrical failure would require out-of-pocket repairs with no OEM parts availability.
• No technical support: Fisker’s customer service line went silent. Owners had no way to get help for even basic issues.

Without intervention, these cars risked becoming rolling paperweights — fully physical vehicles with rapidly degrading digital capabilities.

How did owners organize their response?

Immediately after the bankruptcy news spread, owners flocked to existing online forums and social media groups, such as the Fisker Ocean Owners Club on Facebook and dedicated subreddit. Within weeks, a core team of technically adept volunteers emerged. They formed a steering committee and began coordinating efforts through Discord and GitHub. Their initial goal was simple: document every software and hardware detail of the Ocean to understand what could be preserved or replaced. The community quickly grew to include software engineers, mechanics, cybersecurity experts, and even former Fisker employees who shared insider knowledge. They named their project Fisker Open Source (FOS) — a volunteer-run car company in all but legal name.

What technical steps did owners take to regain control of their vehicles?

The community’s work was deeply technical. First, they reverse-engineered the proprietary software stack by dumping firmware from the vehicle’s infotainment system and ECUs. Using tools like CAN bus sniffers, they mapped out the vehicle’s internal communication protocols. They then wrote open-source programs to emulate Fisker’s cloud servers — creating local alternatives for functions like navigation, climate control, and battery monitoring. Key achievements include:

• A self-hosted server that can run on a Raspberry Pi inside the car, providing OTA update capabilities.
• Custom diagnostics software to read and clear error codes.
• Community-built app for smartphone integration (lock/unlock, pre-conditioning).
• Open-source firmware patches to fix known bugs.

All code is hosted on GitHub under permissive licenses.

What is the current status of this open-source car company?

As of early 2025, the Fisker Open Source (FOS) project is fully operational on a volunteer basis. Hundreds of owners have installed the community software, and the project maintains a self-hosted server solution that works with over 90% of remaining Ocean units. They have also established partnerships with independent repair shops to source compatible parts. Legally, FOS operates as a non-profit cooperative. While they do not manufacture new cars, they provide everything needed to keep Oceans roadworthy — including software updates, diagnostic tools, and a shared knowledge base. The project has even attracted interest from other orphaned EV communities, such as owners of defunct startup vehicles.

What does this story mean for the future of electric vehicle ownership?

The Fisker Ocean revolt challenges the traditional car ownership model — where manufacturers hold ultimate control over software. It proves that community-driven open-source can rescue vehicles from planned obsolescence and corporate collapse. This precedent could inspire similar movements for other orphaned EVs. It also raises legal questions: copyright issues around reverse engineering, liability for modified vehicles, and the right to repair. Regulators may need to consider mandates for software escrow or mandatory open-sourcing of critical systems when an automaker goes under. For owners, the lesson is clear: with enough technical skill and collaboration, even a bankrupt company’s product can be kept alive.