← Back to Blogs
HN Story

From Bricks to Blueprints: How Fisker Ocean Owners Built an Open-Source Car Company

May 17, 2026

From Bricks to Blueprints: How Fisker Ocean Owners Built an Open-Source Car Company

When Fisker Inc. filed for Chapter 11 bankruptcy in June 2024, it didn't just leave behind a trail of debt; it left approximately 11,000 Fisker Ocean SUV owners in a precarious position. These owners, who had invested between $40,000 and $70,000 in their vehicles, suddenly found themselves owning "orphaned" hardware. With the manufacturer gone, over-the-air updates ceased, connected services vanished, and warranties became meaningless.

However, the story did not end with the collapse of the company. In a remarkable display of collective action, the owners refused to let their vehicles become e-waste, instead organizing to build a volunteer-run, open-source support ecosystem from the ashes of the corporation.

The Architecture of Obsolescence

The crisis facing Ocean owners was not merely a lack of customer support; it was a fundamental architectural flaw. The Fisker Ocean was designed as a "software-based car," where critical subsystems—including brakes, airbags, shifting, battery management, and door locks—were designed to periodically communicate with Fisker’s cloud servers for diagnostics and basic operations.

When those servers went dark, the cars didn't just lose their Spotify integration; they lost critical functionality. As Ethereum co-founder Vitalik Buterin noted on X, the situation highlighted a dangerous new default in the industry: "if the manufacturer disappears, the car is useless now."

The Rise of the Fisker Owners Association (FOA)

Within months of the bankruptcy, thousands of owners formed the Fisker Owners Association (FOA), a nonprofit that evolved into a hybrid of a car club and a tech startup. With roughly 4,000 members, the FOA took on the responsibilities that the manufacturer had abandoned:

  • Technical Recovery: The FOA hired independent experts to reverse-engineer proprietary software patches and taught members how to flash their own firmware.
  • Supply Chain Management: To bypass the loss of official channels, the group organized bulk purchases of replacement parts, successfully negotiating the price of key fobs down from $1,000 to a fraction of that cost.
  • The "Flying Doctors": In Europe, a mobile repair network of technically skilled members was established to travel and help other owners maintain their vehicles.
  • Legal and Insurance Advocacy: The FOA worked to ensure safety recalls were included in bankruptcy proceedings and convinced insurers to continue covering vehicles without an active manufacturer.

Engineering the Open-Source Arsenal

Beyond basic maintenance, a sophisticated technical ecosystem has emerged on GitHub and community forums. This effort represents a shift from desperate troubleshooting to intentional open-source development.

API and Integration

A developer known as MichaelOE reverse-engineered the API of the "My Fisker" mobile app, creating a Home Assistant integration. This project allows owners to expose cloud API values as sensors and control vehicle functions via Home Assistant, providing a glimpse of what a truly open vehicle interface looks like.

CAN Bus Mapping

Community members have systematically mapped the Ocean's multiple CAN buses (CCAN, PTCAN, Inverter CAN, and BCAN), publishing DBC files on GitHub to allow for filtering and processing. This work, supplemented by detailed guides from contributors like Majd Srour on sniffing CAN traffic and decoding Diagnostic Trouble Codes (DTCs), aims to put professional-grade diagnostic capabilities directly into the hands of the owners.

The Fragility of Handshake Deals

The community's progress was nearly derailed by a failed corporate partnership. In October 2024, American Lease acquired Fisker's remaining inventory and spent $2.5 million to secure the proprietary source code and cloud services. A "handshake deal" was struck with the FOA to extend these services to private owners.

However, the agreement collapsed when American Lease demanded the FOA cover 58% of operational costs (including LTE and Microsoft Cloud services) without providing itemized invoices. This led to the revocation of remote connectivity and the blocking of a pending software recall, proving that even when source code is "saved," the infrastructure required to run it remains a point of failure.

Broader Implications for the Auto Industry

The Fisker saga is a cautionary tale for the broader EV market, where startups like Nikola, Canoo, and Arrival have faced similar fates. The community's struggle has sparked a wider debate about the "software-ification" of hardware.

The Case for Less Software

While the FOA's efforts are inspiring, some critics argue that the root problem is the over-reliance on software in the first place. One commenter on Hacker News highlighted the absurdity of modern car design, noting that simple mechanical adjustments—like seat positioning—have been replaced by complex CAN bus-integrated motors and software preferences, introducing "problem spaces so baroque they border on the occult."

Structural Solutions

To prevent future vehicles from becoming bricks, consumer advocates and technical experts are proposing several systemic changes:

  1. Software Escrow: Mandatory requirements for manufacturers to place source code in escrow, to be released to the public or a third party if the company goes bankrupt.
  2. Open-Source Mandates: Legal requirements in bankruptcy proceedings to open-source critical vehicle software to ensure longevity.
  3. Right to Repair: Expansion of laws (like Oregon's Right to Repair bill) to ban "parts pairing," which prevents independent repair of software-locked components.
  4. Industry Collaboration: A 2025 memorandum between European giants like Volkswagen, BMW, and Mercedes-Benz to develop a shared open-source automotive software platform suggests that even legacy automakers recognize the risk of proprietary silos.

The Fisker Ocean owners have proven that a dedicated community can keep orphaned EVs on the road through sheer technical will. However, the consensus among advocates is clear: owners should not have to become hackers and parts brokers just to maintain the utility of a product they legally purchased.

References

HN Stories