In June 2024, Fisker Inc. declared Chapter 11 bankruptcy, leaving roughly 11,000 Ocean SUV owners stranded with vehicles that cost between $40,000 and $70,000. These modern electric cars depended heavily on the company’s cloud servers for critical operations. When the manufacturer vanished, so did the over-the-air updates, connected services, and warranty support. The cars were becoming expensive paperweights. Instead of accepting defeat, the owners banded together. They reverse-engineered the proprietary software, hacked into the CAN bus networks, and built entirely new toolkits on GitHub. What emerged from the ashes were five distinct open source cars — different community-driven projects that aim to keep the Ocean alive and independent.
The collapse of Fisker created a unique crisis in the automotive world. The Ocean SUV was a software-defined vehicle, meaning virtually every subsystem required periodic connection to the company’s servers for diagnostics and regular functionality. Digital rights advocates had long warned about the dangers of locking essential car functions to a corporate cloud. Ethereum co-founder Vitalik Buterin captured the moment perfectly on social media, stating the industry needed much more open source development in vehicles. The Fisker community took that sentiment to heart. Within months, they launched five major initiatives that function as independent open source cars, ensuring their vehicles remain drivable, repairable, and relevant.
Car #1: The Fisker Owners Association — The Volunteer Automaker
The Fisker Owners Association (FOA) quickly grew to 4,000 members and began operating as a hybrid between a car club and an independent automaker. This nonprofit organization hired independent technical experts to reverse-engineer Fisker’s proprietary software patches. They secured court representation during the bankruptcy proceedings to ensure safety recalls were addressed properly. The FOA also negotiated with insurers to maintain coverage for a vehicle whose manufacturer no longer existed. By creating a formal legal and logistical structure, they built the chassis of an open source car company, providing the organizational backbone that allows these vehicles to survive without their original maker.
Car #2: The Open-Source Software Stack — Reclaiming the Digital Engine
The technical heart of the movement emerged on GitHub, where developers began publishing critical code. Developer MichaelOE reverse-engineered the API behind Fisker’s My Fisker app, creating tools that gave owners local control over their vehicles. Separately, Majd Srour published a detailed multi-part series on Medium documenting how to sniff CAN traffic and decode Diagnostic Trouble Codes. Complete CAN bus DBC files for the Ocean were uploaded to public repositories, allowing anyone to understand the vehicle’s internal communications. This collective effort effectively liberated the car’s software from the dead company’s servers, creating a genuine open source car ecosystem built on transparency and shared knowledge.
Car #3: The Flying Doctors — The Decentralized Repair Network
In Europe, Ocean owners created a remarkable program called the Flying Doctors. This network consists of technically skilled members who travel to assist other owners facing mechanical or software problems. The Flying Doctors teach each other how to flash firmware, diagnose complex errors, and perform repairs that the original dealer network would have handled. This decentralized service model ensures that a single technical problem does not become a death sentence for the vehicle. It adds a human touch to the open source car movement, proving that community collaboration can replace an entire corporate service infrastructure.
Car #4: The Parts Cooperative — Solving the Supply Chain Problem
Access to replacement parts is a major challenge for orphaned vehicles. The FOA organized bulk purchasing of essential components, negotiating prices down significantly. A clear example is the key fob, which originally cost roughly $1,000 each through Fisker. The cooperative negotiated prices down to a fraction of that through coordinated group buys. They also hosted free global key fob pairing events, saving each participant up to $250. By securing parts supply channels through companies like Tsunami and Tidal Wave, they built a working supply chain from scratch. This open source car model of community purchasing keeps thousands of vehicles on the road.
You may also enjoy reading: Automating Tech Procurement: A Practical Guide to Streamlined Operations.
Car #5: The Home Assistant Integration — Smart Home, Smart Car
One of the most practical tools to emerge is a fully functional Home Assistant integration built by MichaelOE. This system allows Ocean owners to monitor battery levels, lock and unlock doors, and control climate settings directly from their smart home dashboard. Because it connects locally rather than relying on Fisker’s defunct cloud servers, it provides a stable and permanent interface for managing the vehicle. It demonstrates how open source cars can integrate seamlessly into modern smart lifestyles, offering convenience and control that the original manufacturer could not sustain.
Why Open Source Cars Are the Future
The Fisker community has set a powerful precedent that extends far beyond a single model. They proved that a committed user base can outlive the original manufacturer and maintain a vehicle through collective effort. This story has profound implications for the right to repair movement and the future of software-defined vehicles. When a car’s core functions depend entirely on a company’s cloud servers, the owner is always vulnerable to the company’s solvency. The Fisker owners demonstrated that open source cars are not just an abstract concept — they are a practical survival strategy for the modern automotive landscape.
The tools, community structures, and technical frameworks built by these 11,000 owners provide a blueprint for the entire industry. Future automotive buyers may begin to demand that their vehicles include open source components or local control options. Manufacturers building software-defined cars will need to consider what happens to their products if the company fails. The Fisker story is a powerful reminder that the most durable technology is the kind that belongs to its users. These open source cars born from bankruptcy may be the most important experiment in automotive history, proving that when a company abandons its product, the people who love it can build something even more resilient. The wheels keep turning, and the code keeps running — all thanks to a community that refused to let their cars die.
