RAP1 and LiDAR: what the next R2 hardware rollout actually means

By Conor Early · 2026-10-24 · News & analysis

The reported plan separates employee vehicles in late 2026 from customer vehicles in 2027.

February 2024 archive vehicle photograph; not a LiDAR-equipped R2 or evidence of RAP1 hardware. Photo: Eric Anderson / Rivian Newsroom. Used for editorial coverage; © Rivian.

For anyone deciding whether to buy an R2 now or wait, “new hardware is coming” is an incomplete answer. The useful distinction is between the hardware announcement, the first vehicles built with it, and the date a customer can actually receive an equipped vehicle.

The hardware Rivian announced

Rivian’s Autonomy & AI Day material identifies RAP1 as its own processor at the heart of the Gen 3 Autonomy Computer. It also describes adding LiDAR to future R2 models, supplementing its sensing approach with three-dimensional spatial information. These are hardware plans, not merely a new name for an over-the-air update. Rivian’s announcement.

The more recent timeline

InsideEVs reported September 30 that Rivian investor-relations executive Chip Newcom described employee deployment later in 2026 and customer rollout in 2027. The report also recounts Rivian saying the Launch Package would not include RAP1 and LiDAR. That is an attributed rollout plan; it does not establish a precise order date, trim allocation, price or delivery commitment for an individual customer. Read the timeline reporting.

What a buyer should ask

Keep calendar year and model year separate when discussing that timeline. Ask which computer and sensors belong to the exact configuration on your order, and what the vehicle can do at delivery. A roadmap is not a promise that every proposed feature will reach every vehicle.

This article does not establish a retrofit path for existing R2s. Nor does more computing capacity itself establish permission to stop supervising a vehicle. Follow the operating requirements for the features actually enabled on yours.

The practical decision is personal: how well does today’s vehicle meet your needs, and how much uncertainty are you willing to accept while waiting? Our buy-now-or-wait discussion separates current needs from future expectations so that conversation stays useful.

Sources and further reading

Corrections and firsthand experiences are welcome. Identify your R2 configuration and software version when relevant.