When the Server Goes Dark: How Fisker Ocean Owners Built an Open-Source Car Company From the Ashes of Bankruptcy

A $70,000 Car That Needed the Cloud to Survive

The Fisker Ocean was built as a "software-defined car" in the most literal and unforgiving sense. Virtually every subsystem — brakes, airbags, battery management, door locks, gear shifting — was tied to periodic cloud server connections for diagnostics and operations. When those servers began going dark after Fisker's collapse, it wasn't just the navigation app that stopped working. Owners found themselves losing access to critical vehicle functions one by one.

Fisker had secured 31,000 reservations worth a reported $1.7 billion before bankruptcy, but managed to produce only around 11,000 vehicles. When the company filed for Chapter 11 in June 2024 with over $1 billion in debts, those 11,000 owners were left holding expensive paperweights that the rest of the auto industry had no particular reason to support.

4,000 Members and a Volunteer Army

Within months of the bankruptcy filing, Ocean owners began finding each other online and the Fisker Owners Association (FOA) was born. It grew rapidly to over 4,000 members — and it operates unlike anything else in the automotive world. Part car club, part tech startup, part independent automaker, the FOA took on tasks that would normally require teams of paid engineers and millions in infrastructure budget.

Technically skilled members dove into the vehicle's architecture. They mapped the Ocean's CAN bus networks — including CCAN, PTCAN, Inverter CAN, and BCAN, all running at 500 kbps — and published DBC files on GitHub that allow any owner to read and process their vehicle's internal communications. A developer known as MichaelOE reverse-engineered the API behind Fisker's official "My Fisker" mobile app and built a Home Assistant integration that exposes every cloud API value as a sensor, with all the app's controls available locally. The project now has 135 commits, 20 releases, and is released under the Apache 2.0 open-source license.

Community members also built diagnostic tools capable of scanning Diagnostic Trouble Codes — something that previously required dealer access and proprietary software.

Flying Doctors of Europe

For European owners, the community created one of its most creative solutions: the "Flying Doctors" program. Technically skilled FOA members volunteer to travel to other owners and perform hands-on repairs that would otherwise require a dealership network that no longer exists. It's a mobile repair service built entirely on community goodwill and technical expertise.

The FOA also coordinated group purchasing programs that brought down the cost of replacement parts dramatically. Key fobs, for instance, had been selling for close to $1,000 each on the secondary market after Fisker's collapse — the community's bulk purchasing efforts cut that to a fraction of the original price. Supply chains were secured through companies like Tsunami/Tidal Wave, and the association even worked to maintain insurance coverage for what insurers were starting to classify as "orphaned" vehicles.

The American Lease Disaster

The most promising — and ultimately most painful — chapter in the FOA's story involved a company called American Lease. In October 2024, American Lease purchased a portion of Fisker's inventory for $2.5 million, which included access to the vehicle's source code and connected services infrastructure. They initially agreed to extend those connected services to private Ocean owners, which would have been a lifeline for the community.

The deal collapsed when American Lease demanded that the FOA cover 58% of operational costs — an arrangement the association could not sustain. The result was swift and brutal: remote connectivity was revoked, cloud-based features were cut, and a critical software recall was blocked from being delivered. The community was back to fighting with one hand tied behind its back.

Vitalik Buterin and a Bigger Conversation

The Fisker story attracted attention well beyond the EV community. Ethereum co-founder Vitalik Buterin weighed in, observing that "we really need much more open source in the auto industry" — and pointing to the sad reality that when a manufacturer disappears, software-dependent cars effectively become useless. It was a rare moment of alignment between the cryptocurrency world and the practical concerns of everyday car owners.

The Fisker situation is not unique in kind, only in scale. Nikola also filed for bankruptcy. Canoo and Arrival are facing liquidation. As the EV startup wave crests and retreats, more owners of more vehicles will find themselves in exactly this position — holding hardware that depends on software that no one is maintaining.

What Needs to Change — and What Already Is

The FOA's experience has energized advocates pushing for structural change across the industry. The policy demands are concrete: mandatory software escrow funds that ensure source code is held in trust for owners, open-source mandates in bankruptcy proceedings, and shared repair data requirements that prevent manufacturers from monopolizing diagnostic access.

In the United States, Oregon's Right to Repair bill has already taken a meaningful step forward, banning the practice of "parts pairing" — where manufacturers lock replacement parts to specific vehicles, making independent repair impossible. In Europe, the landscape is shifting too: Volkswagen, BMW, Mercedes-Benz, and eight suppliers signed a 2025 memorandum committing to a shared open-source automotive software platform, a sign that at least some established players see the writing on the wall.

The EU's existing right-to-repair legislation, which came into force in 2021 and expanded in subsequent years, gives European consumers stronger protections than their American counterparts — but it was designed for appliances, not software-defined vehicles that communicate with remote servers to unlock basic functions.

A Blueprint — and a Warning

The Fisker Owners Association has done something genuinely extraordinary. A community of everyday people, most of them not professional engineers, kept a vehicle that the industry had written off alive through technical ingenuity and collective determination. They built the infrastructure of a small automaker from scratch, on a volunteer budget, because they had no other choice.

But the fact that they had to do this at all is a damning indictment of how the auto industry builds and sells software-defined vehicles. When you spend $60,000 on a car, you should own it — not rent its functionality from a server farm whose business model might not exist in three years. The FOA's story is a blueprint for what community resilience looks like. It's also a warning about what happens when digital dependency meets corporate failure, and no one has planned for the outcome.

As more legacy automakers race to turn their vehicles into rolling software platforms — subscription features, over-the-air updates, cloud-dependent safety systems — the question the Fisker Ocean community has been living with deserves a much wider audience: what happens to your car when the company disappears?

Source: https://electrek.co/2026/05/16/fisker-ocean-open-source-ev-story-after-bankruptcy/