Fisker Inc. filed for Chapter 11 bankruptcy in June 2024, leaving roughly 4,700 Ocean SUV owners stranded with vehicles that had no manufacturer warranty, dwindling software support, and a very uncertain future. The kind of ending that usually means everyone walks away, parts the cars out, and moves on. Except that's not what happened. Instead, a loose coalition of former Fisker employees, Ocean owners, and independent developers started doing something genuinely unusual: they began treating the Ocean like an open-source project.
That effort has now coalesced into something more formal. A group operating under the banner of what observers are calling the "Fisker Open-Source Initiative" has begun publishing vehicle software, schematics, and diagnostic data that Fisker once kept proprietary. More ambitiously, they're exploring whether new vehicles can be designed and built using the same open, community-driven model that powers Linux, Firefox, and thousands of other software projects. That comparison sounds like a stretch until you look at how far EV technology has actually come in terms of standardization and accessibility.
How a Bankruptcy Became a Starting Gun
Fisker's downfall was spectacular even by startup standards. The company burned through cash trying to compete with Tesla and legacy automakers simultaneously, struggled with supplier relationships, and never resolved serious quality concerns surrounding the Ocean. When bankruptcy proceedings began, the company had approximately $1 billion in debt and an estimated 4,200 unsold vehicles sitting in lots across the United States and Europe.
What bankruptcy court proceedings made clear is that Fisker owned significant intellectual property, including software systems, telematics infrastructure, and vehicle design documentation. As creditors picked through the carcass, some of that IP ended up acquired at steep discounts. Former Fisker software engineers, who had already been laid off in waves throughout 2023 and 2024, started quietly sharing code and documentation in private channels. GitHub repositories began appearing. Discord servers filled up with Ocean owners comparing notes on unofficial diagnostics and workarounds.
This wasn't purely altruistic. Many Ocean owners paid between $37,499 and $68,999 for their vehicles. Watching that investment depreciate toward zero because the software would eventually go dark had a focusing effect on people's motivations.
What "Open-Source Car" Actually Means in Practice
Software people throw the word "open-source" around freely, but applying it to a physical vehicle is genuinely complicated. A car isn't just software. It has crash structures, battery chemistry, thermal management systems, high-voltage wiring, and hundreds of other components that require regulatory approval, manufacturing partnerships, and supply chain management that no GitHub repository can conjure.
What the Fisker open-source community is actually doing, at least right now, breaks into a few distinct tracks.
- Software liberation: Publishing the Ocean's firmware, OTA update mechanisms, and diagnostic protocols so owners can keep their vehicles functional without Fisker's cloud infrastructure. This is the most immediately practical work and the most legally murky.
- Reverse engineering: Mapping out the Ocean's hardware interfaces, battery management system parameters, and CAN bus data so third-party developers can build compatible tools and apps.
- Design documentation: Sharing whatever vehicle design assets were legally acquired or independently recreated, with the long-term goal of enabling derivative vehicle projects.
- Community manufacturing exploration: Investigating whether contract manufacturers in lower-cost regions could produce new vehicles based on open specifications, similar to how open-source hardware companies like Arduino operate at small scale.
That last track is where things get genuinely ambitious, and genuinely difficult.
The Precedents Are Thin but Real
Open-source hardware has produced some real results, just not at automotive scale. The Arduino platform demonstrated that shared hardware designs could spawn massive ecosystems of compatible products. The RISC-V processor architecture, developed openly at UC Berkeley, is now in billions of chips. OSVehicle launched the Tabby EVO, an open-source EV chassis, back in 2014, and while it never achieved mass production, it did get used for small fleet vehicles and prototypes in several countries.
Local Motors tried a crowd-sourced design approach with the Strati, a partly 3D-printed car, before the company shut down in 2022. Wikispeed built an open-source modular car for years as a nonprofit experiment. None of these became mainstream consumer products. The honest assessment is that the gap between a working prototype and a regulatory-compliant, crash-tested, insurable vehicle that people can actually buy and drive legally is enormous. The Fisker community knows this.
But 2024 is different from 2014 in a few important ways. Battery cells are far cheaper, with pack costs hovering around $100 per kWh at volume compared to over $600 a decade ago. Off-the-shelf EV drivetrain components from suppliers in China are now accessible to smaller buyers. Companies like BYD and CATL will work with much smaller order quantities than they would have five years ago. The barrier isn't zero, but it has dropped considerably.
The Software Question Is More Urgent Than the Hardware
For current Ocean owners, the open-source software work matters right now, not in some speculative future. Fisker's cloud services are winding down. The mobile app already struggles with authentication errors. Features like remote climate control, over-the-air updates, and navigation services depend on Fisker's servers staying online, and those servers have no long-term maintenance guarantee.
This is a problem the entire EV industry needs to take seriously. When you buy a car from a legacy automaker that goes bankrupt, you can still drive it. The mechanical systems work. The software dependencies are minimal. A 2005 Ford that survives its manufacturer's bankruptcy still starts in 2024. An Ocean with a dead cloud backend loses significant functionality, potentially including features that were part of the purchase decision.
The open-source community is essentially building a lifeboat. Developers have already created unofficial diagnostic apps that read Ocean battery data, motor temperatures, and error codes without Fisker's servers. An open-source replacement for the OTA update system is reportedly in development. If successful, it would let owners install community-maintained firmware indefinitely, similar to how Android device enthusiasts run custom ROMs on phones their manufacturers abandoned years ago.
What This Means for How We Think About EV Ownership
The Fisker situation is forcing a conversation that the industry has successfully avoided. When you buy an EV from a software-forward company, what exactly do you own? The physical object, certainly. But the software that makes it function? The ability to update it? The diagnostic access needed to repair it? These questions have mostly been answered by manufacturers in ways that favor manufacturers.
Right-to-repair advocates have been making versions of this argument for years. The Fisker bankruptcy gives the argument a specific, sympathetic face. Thousands of people who spent real money on real vehicles are now running down a clock they didn't know existed when they signed the purchase agreement.
Open-source EV advocates argue that publicly documented software and hardware interfaces should be a baseline requirement for any vehicle sold to consumers. Not all the code, necessarily, but enough of the interface specifications that third parties can build compatible tools and maintain functionality after the original manufacturer disappears. The EU is already moving in this direction with vehicle data access rules. The US is moving more slowly.
The New Company Taking Shape
Beyond preserving the Ocean, some former Fisker employees have started working toward an actual company. Details are sparse and the project is early-stage, but the stated goal is to design a simple, affordable EV, targeting a sub-$25,000 price point, using openly documented specifications and contract manufacturing. Think of it as a software startup's approach to car-making: keep the core team small, outsource manufacturing, and let the community contribute to the design and software.
The model has appeal on paper. A small team without billion-dollar factory ambitions might avoid the capital trap that killed Fisker, Rivian's early burn rate problems, and the long list of EV startups that confused fundraising with manufacturing competence. A vehicle designed around standard, documented interfaces could theoretically be maintained, modified, and repaired by a community of independent mechanics and developers rather than a closed dealer network.
The challenges are real. Automotive safety certification in the US runs into the tens of millions of dollars per vehicle model. Liability exposure for a community-designed vehicle is a legal puzzle nobody has fully solved. Supply chain relationships require capital and credibility. And consumers, however frustrated with software lock-in, tend to make purchase decisions based on brand trust and dealer networks, not open-source ethics.
Worth Watching Closely
What's happening with the Fisker open-source community isn't going to displace Ford or GM next year. But it's a real experiment with real stakes, run by people who have technical credibility and personal motivation to make it work. If the Ocean's software gets successfully liberated and maintained by the community, that's a proof of concept with implications well beyond one bankrupt startup's customer base.
Every major automaker is now a software company whether they like it or not. Tesla proved the model works. What Fisker's aftermath might prove is that a community can keep a car alive when the company can't, and maybe, eventually, build one from scratch. The path from here to a viable open-source EV at real volume is long and genuinely uncertain. But the people working on it are further along than most people realize, and the problem they're solving matters far more than just the 4,700 Oceans currently sitting in driveways waiting to find out what happens next.