Tesla Teases Cybercab With Built-In Starlink V5 Dish and Redundant 5G Connectivity

Tesla has published a cutaway image of its Cybercab robotaxi showing an integrated SpaceX Starlink V5 satellite dish alongside a 5G LTE cellular antenna and GPS module, the first concrete look at the vehicle's connectivity architecture. Engadget
The image, posted on X by Tesla's official account, reveals the Starlink V5 dish embedded into the vehicle's roof structure, paired with a built-in 5G antenna for redundant terrestrial connectivity. A concurrent Starlink post on the platform described the integration as "High-speed internet from space for the future of autonomous vehicles." Engadget
The Starlink V5 dish itself was announced the week prior to the Cybercab reveal. It is smaller and more energy-efficient than previous Starlink hardware generations, including the V4 model. On raw throughput, the V5 delivers 375+ Mbps, slightly below the V4's 400+ Mbps rating. Starlink currently positions the V5 as a home internet terminal only, distinguishing it from the Starlink Mini, which is designed for mobile, on-the-go use. The Cybercab integration would, if it ships, put the V5 into a mobile application that Starlink has not formally marketed it for. Engadget
The dual-connectivity approach pairs low-latency satellite backhaul with 5G cellular for dense urban coverage. For a vehicle designed to operate without a human driver, maintaining continuous connectivity for telemetry, over-the-air updates, remote assistance, and real-time mapping data is a functional requirement rather than a convenience feature. The redundancy between satellite and cellular paths addresses a straightforward failure-mode concern: cellular dead zones in rural or fringe-urban areas, and satellite signal degradation under dense canopy, tunnels, or urban canyon conditions.
Tesla has not announced a release date for the Cybercab. The vehicle remains in development. In a January 2025 SEC filing, Tesla listed the Cybercab as "In development" in Nevada. SEC Filing At that time, Elon Musk told investors that Tesla would roll out autonomous ride-hailing for money by June 2025 in Austin, Texas. Reuters That timeline has passed without a commercial Cybercab launch. According to Robotaxi Tracker data cited by Engadget, Tesla's current fleet comprises 39 unsupervised rider vehicles and 770 total vehicles including supervised ones. Engadget
The V5's slightly lower peak throughput compared to the V4 (375+ Mbps versus 400+ Mbps) is unlikely to be a meaningful constraint for a vehicle application. Autonomous driving telemetry, even with high-resolution sensor streaming, consumes a fraction of that bandwidth. The relevant engineering tradeoff is power draw and form factor, both of which favor the V5 for roof integration on a compact vehicle where aerodynamic profile and battery budget matter.
Starlink's own marketing of the V5 as a home-only terminal raises a practical question about the terminal's mobile-use certification and whether Tesla has access to a variant or firmware profile not available to standard consumers. The V5 dish may require modifications for mobile Doppler-shift compensation and handoff between orbital planes that the home-internet firmware does not currently handle. Starlink's Mini, by contrast, is explicitly designed for in-motion use.
The broader context here is that Tesla is building out the connectivity layer for a vehicle platform that does not yet have a committed production date. The Cybercab concept has moved from render to physical prototype with Starlink integration, but the gap between Musk's June 2025 Austin target and the current fleet size of 39 unsupervised vehicles underscores the distance remaining between the reveal stage and commercial deployment. The connectivity architecture itself is technically sound; the question is when, and whether, the vehicle around it arrives at scale.
For Tesla, the Starlink integration also tightens the operational link between two Elon Musk-led companies. The Cybercab's connectivity stack depends on SpaceX infrastructure for its satellite backhaul path, creating an intra-ecosystem dependency that competing robotaxi operators do not have. Whether that is an advantage or a single point of organizational risk depends on execution that has not yet been demonstrated.
The cutaway image confirms the physical integration is real enough to show publicly. What remains undisclosed is the production timeline, the mobile-use certification status of the V5 terminal, and the operational parameters under which satellite and cellular paths will fail over between each other in production vehicles.


