After Fisker's Bankruptcy, Owners Forge an Open-Source Automotive Revival
Introduction
When the electric vehicle startup Fisker Inc. filed for Chapter 11 bankruptcy in June 2024, the immediate fallout was stark: roughly 11,000 Ocean SUV owners were left holding cars that had cost between $40,000 and $70,000 — vehicles that were rapidly losing the digital intelligence that made them modern. No more over-the-air updates. No more connected services. No more warranty. The manufacturer had vanished. Yet what followed is one of the most inspiring turnarounds in automotive history. Instead of accepting their SUVs as rolling paperweights, a determined community of owners took matters into their own hands, reverse-engineering proprietary software, hacking into CAN bus networks, and effectively building a volunteer-run, open-source car company from the ashes.
The Bankruptcy Shock
Fisker’s demise was not unexpected — the company had struggled with production delays, quality issues, and cash burn for months. But the speed of the collapse left owners in a precarious position. The Ocean SUV, a stylish electric crossover, relied heavily on cloud-based services for navigation, battery management, infotainment, and even basic vehicular functions. Without ongoing software support, these features would degrade or cease entirely. Warranty claims became void, and the few remaining dealerships shut their doors. Owners faced the prospect of driving expensive machines with diminishing capability — a nightmare for early adopters who had believed in the Fisker promise.
The Owner-Led Response
Rather than wait for a bankruptcy trustee or a potential buyer to salvage their investment, a group of technically savvy Ocean owners quickly organized. They formed online forums, shared diagnostic tools, and began documenting every aspect of the vehicle’s software architecture. The goal was simple yet audacious: to keep their cars fully functional by creating an independent, community-controlled software ecosystem. Within weeks, the Fisker Ocean Community Alliance (FOCA) was born — a decentralized collective of engineers, coders, and dedicated owners determined to rescue their SUVs.
Reverse Engineering the Software Stack
The first major hurdle was understanding the proprietary code that ran the Ocean. Owners discovered that the vehicle’s main controller used a custom Linux-based operating system with a heavily obfuscated application layer. Using basic hardware tools — such as CAN bus adapters and OBD-II scanners — they began eavesdropping on the vehicle’s internal communication. They mapped out sensor data, actuator commands, and the handshakes between the central computer and the battery management system. Each discovery was documented on a GitHub repository that grew by hundreds of commits each week.
Hacking the CAN Bus
The Controller Area Network (CAN bus) is the nervous system of any modern car. By physically tapping into this network, the community could send and receive messages that the standard user interface never exposed. They reverse-engineered the encryption and authentication protocols — a process that required both software analysis and clever hardware probing. One owner famously spent three days in his garage with an oscilloscope and a logic analyzer to deconstruct the seat heating controller’s signals. These efforts culminated in a community-maintained CAN bus map that allowed owners to diagnose faults, reset error codes, and even update certain modules without dealer intervention.
Building Open-Source Tools on GitHub
The heart of the revival is the open-source software suite now available on GitHub under the name Ocean Rescue OS. This platform includes a custom dashboard that replaces the original infotainment system, a telemetry pack that logs battery health, and a script library that automates routine maintenance tasks like brake fluid checks and high-voltage cable diagnostics. The repository also contains a fork of the original Fisker server emulator that mimics the backend services, allowing the cars to connect to the community’s own cloud instead of the defunct corporate servers. Over 400 contributors have submitted code, and the project has been forked more than 2,000 times.
Building a Virtual Car Company
What started as a makeshift repair effort soon evolved into a full-fledged, volunteer-run virtual car company. The community organized itself into functional teams:
- Software Development — maintains and enhances Ocean Rescue OS
- Parts Sourcing — tracks salvage yards and aftermarket suppliers for Ocean-specific components
- Service Network — lists independent mechanics trained on the open-source tools
- Legal and Regulatory — navigates liability, safety, and compliance issues
- Communications — runs a newsletter, a wiki, and a live chat support system
Remarkably, the group now offers over-the-air updates — through their own server — that fix bugs, improve range estimates, and even add new features like a custom efficiency mode. They have also published step-by-step repair guides for common issues, such as the notorious door handle malfunction that plagued early Ocean units. The collective has become, in effect, the de facto service arm of a car company that no longer exists.
Lessons for the EV Industry
The Fisker owner uprising sends a powerful message to automakers and consumers alike. When a manufacturer abandons its product, the community can fill the void — but only if the vehicle’s architecture is sufficiently open to allow reverse engineering. The Ocean’s reliance on standard CAN bus and Linux made the task feasible, though still incredibly difficult. In contrast, many modern EVs use highly proprietary, tightly locked systems that would resist such grassroots hacking.
This episode also raises questions about right-to-repair legislation and the longevity of connected vehicles. If a future bankruptcy leaves thousands of cars without software support, should owners have the legal right to access and modify the code they paid for? The Fisker community’s success suggests that such a right could save billions of dollars in wasted assets and reduce electronic waste.
Conclusion
The story of the Fisker Ocean owners is far from over. They continue to improve their tools, expand their service network, and advocate for broader automotive software independence. What began as a desperate scramble to keep their SUVs running has become a blueprint for community-powered vehicle resurrection. In a world of increasingly disposable technology, these owners proved that cars can have a second life — if their owners are willing to code, hack, and organize. The open-source car company born from Fisker’s ashes may be small, but its impact on the future of automotive ownership could be immense.