[AlotOfReading]

I would consider a reasonable definition of 'open' to include publication of all relevant safety metrics through the appropriate channels. As the other reply mentions, one channel would be the DMV report in CA which Tesla famously eschews. They also don't publish FSD data, and their AP numbers are essentially useless for determining actual safety. They also don't have professional testers like cruise, waymo, etc do validating releases. Those other companies can do better here with publication, but they track safety data very closely internally, even down to specific scenarios and streets/areas. I haven't seen evidence that those sorts of numbers exist at Tesla or are consulted before releasing updates to the public, but feel free to correct me.

If your metric is simply public access and videos, waymo and cruise both have public demos available. jjricks has quite a few videos on the former. The latter is too new and small a program to have much content yet.

[onethought]

I'm sorry I don't consider a "curated CSV for California only" to be at all equivalent to 60,000 members across the US of the public who are free to post videos and setup failure cases, and report whatever they like.

> They also don't have professional testers like cruise, waymo, etc do validating releases.

Source? From my understanding they rollout releases to employees first (I assume a subset of those are professional testers). Then to beta testers. There have been a couple of releases that have been halted that lend credence to that.

> They also don't publish FSD data, and their AP numbers are essentially useless for determining actual safety

So is this because you can't see detailed data of their in-progress beta software? Could you show me the beta stats of Waymo/Cruise? Where are they published? Tesla aren't operating any robotaxis - so it's clearly not a finished piece of software is it?

On the AP front, why is the AP data useless? Which data do you need that is missing?