An Open Call to Volkswagen, Volkswagen Digital Solutions & CARIAD

Over the past months, we’ve spent countless hours analyzing endpoints, testing OAuth flows, and reverse-engineering client IDs to keep third-party integrations and community projects alive for VW ID and connected vehicle services. Every time access methods change or public clients get locked down, it kicks off another round of a classic cat-and-mouse game. We spend our technical energy finding workarounds, while your teams spend time erecting new barriers. In the end, nobody wins - least of all the passionate VW owners who just want to integrate their vehicles into their smart homes, custom dashboards, and personal workflows. We also have to acknowledge that the current official implementation of the EU Data Act, unfortunately, does not cover the real-world needs of the developer and enthusiast community. The actual usage patterns - real-time updates, local automation, and lightweight API access - require a level of practical flexibility that formal regulatory frameworks haven't yet delivered. **We want to change this dynamic.** Instead of working against each other, **let’s work together**. The developer and open-source community isn’t trying to break your systems; we want to make the VW ecosystem richer, more flexible, and more valuable for drivers. Formalizing developer access, establishing practical community APIs, or simply creating a direct line of communication would benefit everyone. If anyone on the VW Digital, CARIAD, or Connected Mobility teams is listening: reach out to us (reach out to me or Robin). Let’s sit down, talk through security, regulatory constraints, and technical realities, and build a collaborative bridge instead of playing another round of cat-and-mouse. FYI @robinostlund, @andig, @balloob, @frenck

GitHubToolDevSource
0Sign in to voteCopy link

FL score

42

out of 100

Verdict

SKIP

medium confidence

Competition

No competitor data yet

Trend

No signal yet

A request for Volkswagen to formalize developer API access, not a standalone business idea.

The pain

Developers and enthusiasts reverse-engineer VW vehicle APIs to build integrations, dashboards, and smart home automation. Each time Volkswagen locks down access, the community has to find new workarounds. This wastes engineering time on both sides and frustrates users who want legitimate third-party tools.

The gap

Volkswagen has not published official, stable APIs for community developers. The EU Data Act does not mandate the real-time, lightweight access patterns that hobbyists and small builders need. There is no formal channel between the open-source community and VW's product teams.

Build angle

Instead of asking Volkswagen for permission, build a standalone product that works within existing constraints. Options: (1) A proxy layer that caches and serves vehicle data locally, reducing API calls and working around rate limits. (2) A community-maintained SDK that abstracts away reverse-engineered endpoints and updates automatically when they break. (3) A marketplace or registry where developers share working integration patterns and alert each other to API changes. (4) A consulting service that helps enterprises negotiate data access agreements with OEMs. Any of these creates value independent of Volkswagen's cooperation.

Strengths

  • The pain is real and affects a growing number of people as vehicle connectivity expands.
  • The founder has deep technical credibility and has already done the hard reverse-engineering work.
  • The community is passionate and willing to contribute time and code.
  • The problem touches a regulatory gap that will likely widen as more OEMs lock down APIs.

Risks

  • Volkswagen could shut down any workaround at any time, making the entire business fragile.
  • The addressable market is small: only developers and enthusiasts willing to tinker, not mainstream consumers.
  • No clear revenue model. Developers rarely pay for tools; they expect open-source or free access.
  • The idea depends entirely on Volkswagen's willingness to negotiate, which is outside the founder's control.
  • Legal risk: reverse-engineering and distributing access methods could violate terms of service or CFAA-like laws.
  • This is a feature request, not a business. It solves a problem for Volkswagen's benefit, not the founder's.

Questions about this idea?

FlyBot reads the scoring and gives you a second opinion on “An Open Call to Volkswagen, Volkswagen Digital Solutions & CARIAD”.

Open FlyBot