Two years after Fisker Inc. collapsed into bankruptcy and left roughly 11,200 Ocean owners without warranty coverage, software updates, or the hands-free driver assistance the company had actively used to sell them their vehicles, an open-source hardware platform has done what the car's own maker never could. On July 12, Comma AI posted a demonstration video showing a Fisker Ocean SUV steering itself through city streets using the company's $999 Comma Four device — hands-free, with no input from the driver. The clip was shot by Majd Srour, a security researcher and prominent figure in the Fisker owner community, and it represents the first publicly demonstrated proof that openpilot's lane-centering can run on the Ocean using an external CAN integration rather than anything Fisker installed.

The wires are still visibly hanging in the demo footage. The software branch enabling the port has not been merged into openpilot's public repository, and there is no automatic acceleration or braking yet. But the steering works — and after two years of broken promises, that is no small thing for owners holding premium electric SUVs priced from roughly $40,000 to over $70,000 that were physically capable of hands-free driving from the day they left the factory.

Hardware Was Always There — Software Never Came

Every Fisker Ocean rolled off Magna Steyr's production line in Graz, Austria with the sensors and electronics necessary to support hands-free driving. Fisker had sold buyers on a suite of advanced driver assistance features — adaptive cruise control with lane awareness, an autonomous parking system the company called Park My Car, and a bidirectional home-charging system called PowerHouse — all of which depended on software that was still under development when the company filed for Chapter 11 bankruptcy protection on June 17, 2024. Some owners reported seeing the steering wheel buttons for these features but finding them grayed out in software, awaiting an over-the-air update that never came.

By the time bankruptcy proceedings advanced to liquidation approval, Fisker's engineering team had been decimated by layoffs. The update — and every feature that depended on it — was never delivered.

That left owners in a difficult position: holding vehicles that were technically capable of hands-free driving but left in a lesser state by software the maker no longer had the resources or the incentive to ship. The promised features were not missing from the hardware — they were absent only from the software flag that would have switched them on.

From Security Vulnerability to CAN Integration

Srour is not a random tinkerer. In May 2025, he published Srour's Fisker Ocean security research documenting severe security vulnerabilities in the Fisker Ocean's cloud infrastructure — demonstrating that he could remotely unlock and start an Ocean belonging to a friend in Canada from his laptop in San Jose, California, using nothing more than a vehicle identification number and an exposed API key. His work revealed that Fisker's connected-vehicle architecture had been built without basic authentication safeguards: no multi-factor verification, no encryption, no security certificates — and that the same exposed API included commands for sending raw CAN messages directly to the vehicle.

His latest project turns that same CAN bus expertise in a more constructive direction. Rather than exploiting the Ocean's Controller Area Network — the internal protocol through which a vehicle's electronic control units exchange commands — Srour is now using it to introduce commands from an external device. Specifically, Comma AI's Comma Four plugs into the car via a model-specific wiring harness, intercepts the CAN messages that would normally carry steering commands, and replaces them with torque instructions computed by openpilot's on-board neural network.

The critical detail is how that torque command gets accepted. When openpilot issues a steering command on a supported vehicle, it does so by sending raw CAN messages with the correct message identifier, torque scaling, checksum, and counter format that the car's electric power steering module expects to see from its own ADAS system. Getting those parameters right — reverse-engineering the Ocean's specific message IDs and formats — is the core porting work Srour has done. When the EPS module receives a message in the format it expects, it accepts the command without triggering a fault, regardless of whether the command came from the car's own ADAS ECU or from Comma AI's device mounted on the windshield.

What the Comma Four Actually Does

The Comma Four, announced at COMMA_CON 2025 on November 8 and made available for purchase on November 25, 2025, is a compact windshield-mounted computer roughly the footprint of a standard rearview mirror. It houses a triple-camera 360° vision system, a Qualcomm Snapdragon 845 MAX processor with a custom-engineered cooling system designed to prevent thermal throttling on hot windshields, built-in LTE and Wi-Fi for over-the-air software updates, and a 1.9-inch OLED display. The device retails for $999, and the openpilot software it runs is entirely open-source, free of charge, and continuously developed by both Comma AI's team and a community of over 1,000 external contributors.

On Comma Four's official product page, openpilot is described as delivering automated lane centering and adaptive cruise control — roughly comparable to Tesla Autopilot or GM Super Cruise in function, though Comma AI frames it explicitly as a Level 2 system requiring driver supervision at all times. The platform's neural network, redesigned for the openpilot 0.11 release in early 2026, is now trained using a 2-billion-parameter world model built on 2.5 million minutes of fleet driving video — a shift Comma AI describes as transforming openpilot from a conventional driver assistance system into a "robotics agent" capable of full end-to-end longitudinal control in Experimental Mode. As of openpilot 0.11.2, released June 15, the officially supported vehicle list includes more than 325 models across Toyota, Hyundai, Honda, Ford, GM, and others, accumulated over a decade of community-contributed vehicle ports.

Crucially for the Fisker case, openpilot does not depend on the host vehicle's own ADAS sensors. It sees the road through its own cameras and computes its own trajectory before issuing control commands over the CAN harness. This independence from the host car's sensor stack is precisely what makes a port possible on a vehicle like the Ocean, whose native ADAS sensors were present but never software-activated by the manufacturer.

What Owners Can Expect — and When

For now, Ocean owners interested in the Comma Four port will need to wait for Srour's branch to stabilize and be submitted to openpilot's public repository. The current implementation covers lateral control only. Adding longitudinal control — automatic acceleration and braking — requires further reverse engineering of the Ocean's CAN interface to identify and safely map the throttle and brake message IDs and parameters. Until that work is complete and validated, the driver must remain actively engaged with the throttle and be ready to take over at any moment.

When a full port is available, Ocean owners would need to purchase the Comma Four device at $999 and a compatible wiring harness — putting the all-in cost at roughly $1,200 to $1,500 depending on harness pricing. In exchange, they would receive ongoing software updates from Comma AI's continuously developed platform, free of subscription cost, independent of any manufacturer's cloud infrastructure.

That independence is the point. The openpilot ecosystem does not depend on Fisker's servers, American Lease's maintenance budget, or any third-party software contractor like the Indigo Tech firm whose OTA update bricked an estimated 10 percent of Ocean vehicles in late 2024 — forcing owners to pay $200 to $350 out of pocket for manual remediation. Ocean owners who have been dealing with cut-off connected services, unauthorized firmware rollbacks, and the collapse of the American Lease/Fisker Owners Association cloud agreement are being offered something the original manufacturer never provided: a software stack that belongs to no single company's balance sheet.

Open-Source Development Is the Only Verified Escape Route from EV Startup Bankruptcy

The Fisker Ocean is the most visible test case yet of what the industry has begun calling the orphaned EV problem — a vehicle whose manufacturer has ceased to exist but whose feature set depends on cloud servers, over-the-air update pipelines, and software flags that only the original engineers could set.

The consequences for Ocean owners have been cascading and well-documented. After the bankruptcy liquidation was approved in late 2024, approximately 3,200 unsold Oceans were acquired by New York fleet operator American Lease for roughly $14,000 apiece — a fraction of their original sticker prices — and deployed as Uber and Lyft rideshare vehicles in New York City. Private owners received a short-lived reprieve when American Lease agreed to maintain connected services in exchange for cost-sharing from the Fisker Owners Association, a 4,000-member nonprofit that formed specifically to keep the vehicles functional. That agreement subsequently collapsed over payment disputes. As Fisker owners lose connected services, remote access, streaming, traffic data, and OTA update delivery have all been severed for private owners.

The structural lesson is not specific to Fisker. When any connected vehicle is sold with software-gated features, the buyer implicitly accepts a form of counterparty risk that neither lemon laws nor existing warranty frameworks address: if the manufacturer fails to deliver those features and subsequently ceases to exist, there is no legal mechanism for the buyer to recover them. What the Comma AI port demonstrates — and what the broader openpilot ecosystem's community-port model has now shown repeatedly, from pre-Autopilot Teslas to Gen 1 Rivian owners who received openpilot's Rivian Gen 1 support after Rivian halted further ADAS updates for that generation — is that open-source development is currently the only documented path by which EV owners can recover promised software capabilities after their manufacturer's exit.

That is a market failure. Open-source hacking is a workaround, not a solution. But for 11,200 owners who bought a car on the strength of features that will never arrive from the people who sold it to them, a $999 workaround that works is worth considerably more than any amount of policy discussion about what should have been done differently.

Does Fisker Ocean openpilot Support Apply to the Rideshare Fleet?

Whether the Comma Four port ever reaches the Ocean rideshare fleet operated by American Lease is a separate question. Commercial fleet operators face insurer requirements and commercial licensing conditions that may complicate the deployment of aftermarket ADAS hardware. A fleet operator running vehicles under commercial coverage would need explicit insurer sign-off before installing a third-party system that modifies the vehicle's steering control loop.

For private Ocean owners — the roughly 8,000 individuals who bought their cars expecting Fisker to deliver on its promises — no such barrier exists. The Comma Four is legal to purchase and install. The only current obstacle is that the Fisker-specific openpilot branch is not yet publicly available.

Two years after the bankruptcy filing that ended Fisker's obligations to its owners, the community is still finishing what the company started.

Frequently Asked Questions

Can I install openpilot on my Fisker Ocean today?

Not yet, as of July 13, 2026. The branch enabling Fisker Ocean support was demonstrated by security researcher Majd Srour on July 12 but has not been merged into the public openpilot repository. When it is released, Ocean owners will need a Comma Four device ($999) and a compatible wiring harness, putting the all-in cost at approximately $1,200 to $1,500. Watch the openpilot GitHub repository and the Fisker Owners Association community channels for updates on when the port becomes publicly available.

What does "CAN bus integration" mean for a car like the Fisker Ocean, and why does it matter?

CAN (Controller Area Network) is the internal communication protocol that all of the Ocean's electronic control units use to send commands to each other — including commands to the electric power steering motor. When Comma AI's hardware connects via a wiring harness, it intercepts those messages and substitutes its own steering torque commands, computed from the device's own cameras. Critically, openpilot does not use the Ocean's own ADAS sensors — it uses its own vision system — which means the port works even though Fisker never activated the Ocean's factory driver assistance. The porting challenge Srour solved was identifying the correct message identifiers, torque scaling values, and checksums the Ocean's steering module expects, so it accepts the external commands as if they came from the car's own systems.

What happened to the features Fisker Ocean buyers were promised?

Fisker sold the Ocean with promises of adaptive cruise control, hands-free lane centering, autonomous parking (Park My Car), and a bidirectional home-charging system (PowerHouse). All of these features required software updates that were still in development when Fisker filed for Chapter 11 bankruptcy in June 2024. The update was never shipped. After the bankruptcy, American Lease acquired the fleet inventory and contracted Indigo Tech to manage OTA updates — an effort that bricked approximately 10 percent of vehicles, with owners paying $200 to $350 out of pocket for fixes. Connected services were subsequently cut off after a payment dispute. None of the originally promised ADAS features have been delivered by any party since Fisker's collapse.

What does the Fisker case mean for anyone buying an EV from a startup today?

It reveals a structural gap in consumer protection law: when a connected vehicle is sold with software-gated features — features that exist in the hardware but are activated by an over-the-air update — the buyer has no legal remedy if the manufacturer fails before delivering them. Lemon laws and warranty claims require the manufacturer to exist. The Comma AI port is a workaround, not a solution. Prospective EV buyers should factor a manufacturer's financial health, software delivery track record, and whether promised features are already activated (not just promised) into their purchase decision. Policy advocates and consumer groups have begun pushing for software escrow requirements and open-source transition clauses in EV bankruptcy proceedings, but no such protections are law in the United States as of this writing.