From Bankruptcy to Community Innovation: How to Build an Open-Source EV Car Company from a Failed Manufacturer

Introduction

When Fisker Inc. filed for Chapter 11 bankruptcy in June 2024, roughly 11,000 Ocean SUV owners faced a grim reality: their $40,000–$70,000 vehicles were losing the software brains that made them run. No more over-the-air updates, no connected services, no warranty. The manufacturer was dead. But rather than watch their cars become rolling paperweights, these owners did something remarkable. They organized, reverse-engineered proprietary software, hacked into CAN bus networks, built open-source tools on GitHub, and effectively stood up a volunteer-run, open-source car company from the ashes. This guide shows you how they did it—and how you can apply the same principles if you ever find yourself stranded with a discontinued EV.

What You Need

• Ownership of a stranded EV from a bankrupt or defunct manufacturer
• Basic technical skills (or willingness to learn): understanding of CAN bus systems, embedded software, and Linux
• Access to tools: OBD-II scanner, oscilloscope, logic analyzer, and a laptop with open-source software (Wireshark, CANutils)
• A community platform: Discord, Slack, or a forum to coordinate volunteers
• GitHub account for hosting open-source code and documentation
• Legal advice (optional but recommended) to navigate intellectual property and right-to-repair laws
• Patience and persistence — this is a marathon, not a sprint

Step-by-Step Guide

Step 1: Organize the Community

The first thing Fisker owners did was find each other. Within days of the bankruptcy announcement, they set up dedicated forums, subreddits, and Discord servers. Create a central hub where owners can share knowledge, ask questions, and divide tasks. Use social media and online car communities to spread the word. Elect moderators and assign roles: hardware hackers, software developers, documenters, and testers. A thriving community is the foundation of every open-source project.

Step 2: Gather Technical Documentation

Before you can reverse-engineer anything, collect every scrap of information available. Search for service manuals, wiring diagrams, and any leaked technical documents. Fisker owners found that some parts of the software were still accessible via the vehicle’s diagnostics port. Scrape official websites (some may still have mirrors), contact former employees, and share findings in a private wiki. Create a central repository with PDFs, schematics, and notes. This step is critical because you’re working blind without the manufacturer’s support.

Step 3: Reverse-Engineer the CAN Bus and Software

The CAN bus is the nervous system of any modern car. Using an OBD-II adapter and software like Wireshark, capture CAN bus traffic while performing actions (locking doors, starting the car, adjusting climate). Map the message IDs to functions. Fisker owners discovered that many critical features, like battery management and infotainment, were controlled by proprietary ECUs. They used logic analyzers to probe pins, dumped firmware via JTAG/SWD interfaces, and decompiled the code using tools like Ghidra. Document every finding in the repository. Expect this step to take weeks or months—it’s the hardest part.

Step 4: Build Open-Source Tools on GitHub

Once you understand the vehicle’s communication protocols, start coding. Create a GitHub organization and repositories for different components: a CAN bus library, a replacement infotainment system (using something like Android Automotive or a custom Linux distro), a server for over-the-air updates, and a companion mobile app. The Fisker community released tools like “FiskerOS-Open” and “OceanCAN.py” that let owners read diagnostic codes, adjust battery parameters, and even enable disabled features. Use an open-source license (GPL, MIT, Apache) to encourage contributions.

Step 5: Replicate Connected Services

When the manufacturer’s cloud servers go dark, features like remote lock/unlock, climate pre-conditioning, and charging status vanish. Build your own back end using open-source MQTT brokers (like Mosquitto), Node-RED, or AWS alternatives. Reverse-engineer the API calls that the car’s infotainment system makes—often they’re standard HTTP requests to an endpoint. The Fisker community set up a community-run cloud service hosted on donated servers. You’ll need to implement authentication, encryption, and reliable connectivity. Security is paramount—a compromised car can be dangerous.

Step 6: Establish a Volunteer-Run Organization

An open-source car company needs structure. Form a non-profit or a cooperative (legal entity) to manage donations, domain names, and liability. Create a transparent roadmap, use GitHub Projects for task tracking, and hold regular virtual meetings. The Fisker owners registered the “Fisker-Owners Alliance” as an entity and launched a Patreon to fund server costs and hardware. Appoint a lead maintainer for each subsystem. Document everything—onboarding new volunteers becomes much easier when you have clear README files and contributor guidelines.

Step 7: Share Updates and Maintain the Project

Your community-built car company will live or die by its updates. Regularly publish “release notes” on your forum or blog, explaining new features, bug fixes, and how to apply updates. Set up an over-the-air update mechanism using a custom server (Step 5) or a simple USB-based flash process. The Fisker project now releases monthly updates that include improvements to battery range, infotainment stability, and new driving modes. Engage with the wider EV community—cross-pollinate ideas and code—to keep the project alive.

Tips for Success

• Start small: Don’t try to replicate the entire car software at once. Focus on one critical function (e.g., battery monitoring) first.
• Respect IP laws: Reverse-engineering may be legal under right-to-repair laws, but distributing proprietary code is not. Keep your work clean-room if necessary.
• Test extensively: A bug in a car’s software can be dangerous. Use simulators, spare ECUs, or a test vehicle before rolling updates to the whole fleet.
• Build a diverse team: You need not only coders but also testers, writers, legal experts, and community managers. Every skill is valuable.
• Document decisions: Write down why you chose a particular protocol or library—future maintainers will thank you.
• Celebrate milestones: Setting up a functioning dashboard or successfully updating a car over-the-air is a huge win. Acknowledge contributors publicly to keep morale high.
• Prepare for attrition: Volunteer projects often slow down after the initial excitement. Have a core team committed to the long haul.

The Fisker Ocean community proved that a dead car company doesn’t have to mean dead cars. With organization, technical grit, and open-source principles, you can take control of your vehicle’s future. The road ahead is long, but the destination is worth it: a car that truly belongs to its owners.