Electric car parked in the garage: the real risk of proprietary software after insolvency

Bankruptcy of automakers exposes risks of vehicles dependent on proprietary software that may become inoperable without ongoing support.

Fisker Ocean and Renault Fluence Z.E. illustrate real cases where server interruptions left cars without basic functions or completely stopped. Especialistas warn that the growing dependence on remote updates and connectivity makes mechanical durability a secondary issue compared to the survival of the company responsible for the code.

Owners face difficulties accessing over-the-air updates, remote diagnostics or even starting the vehicle in extreme scenarios. Iniciativas like Catena-X seek to standardize components to facilitate replacements, but the industry still lacks mandatory rules to ensure minimum support.

Growing risks in connected vehicles

Modern vehicles integrate software into essential subsystems such as battery management, door locking and engine starting. Quando the company responsible closes operations, servers are turned off and remote access disappears.

Updates stop arriving, leaving glitches unfixed. Proprietários turn to informal communities for unofficial solutions, but this involves safety risks such as airbag or brake failures.

Recent cases show that even basic functions can require cloud authentication, rendering the car inoperable without an active connection.

Concrete examples of failures after insolvency

Fisker, which delivered the Ocean in markets such as Reino Unido and Estados Unidos, declared bankruptcy in 2024. An owner in

The car remained an immovable object in the garage, with no access to updates or official support. Tentativas of partnerships to maintain services have failed in some cases, cutting off premium connectivity and remote diagnostics.

Historical cases reinforce concern

Better Place, which operated battery swapping infrastructure for electric vehicles, went bankrupt in 2013 after investing US$850 million. Servidores were turned off, preventing battery authentication and fleet management on the Renault Fluence Z.E. sold in Israel and Dinamarca.

Renault halted production of the model on Turquia due to the impact. Proprietários were left with vehicles unable to charge or change batteries, highlighting vulnerabilities in centralized proprietary systems.

Initiatives to mitigate software dependency

Catena-X, a collaborative data network in the automotive industry, promotes software bills of materials and component standardization. Isso facilitates replacement by alternative suppliers via marketplace and open-source implementations.

Associations advocate shared commitments to data retention, such as battery passports valid for ten years. Especialistas emphasize that interoperability reduces risks, but does not replace specific regulations for long-term support.

Server dependency affects security and residual value

Unsupported cars face similar cyber vulnerabilities as outdated internet-connected devices. Falhas not corrected can compromise critical systems, raising concerns at high speeds or emergency situations.

Resale value drops sharply when upgrades stop, as potential buyers avoid models from unstable brands. Established Fabricantes offer longer guarantees, but startups face greater scrutiny for insolvency history.

Owners seek limited alternatives

Communities of owners attempt reverse engineering to maintain functionality, but experts warn against unverified solutions. Erros may affect active safety, such as stability control or braking systems.

Consolidated brands maintain support for decades in some cases, but the increase in connected features puts pressure on better planning. The transition to software-defined vehicles requires a balance between innovation and affordable durability.