Inside XPENG's Paris 'Revenge': Cloud, Edge and the Australian Deployment

The Weibo essay that calls the Paris Motor Show XPENG's "revenge" is not really about the show. Strip out the scorekeeping and it is an argument about compute: a 72-billion-parameter teacher in the cloud, a car-sized student on the road, and a European adaptation recipe measured in weeks rather than years. That is the part worth reading closely — and it is also the part that decides when any of this reaches Australia.

The event first, briefly. The 2026 Paris Motor Show added an official public autonomous-driving lab, and only two manufacturers accepted: Tesla, with Model 3s running FSD Supervised, and XPENG, with MONA L03s running the second-generation VLA. No European manufacturer took part. He Xiaopeng flew in to test NGP himself and asked for France's worst routes. Before Paris, Xinhua ran a same-route comparison in Amsterdam and called the two systems "hard to separate" — the one difference it singled out was a construction zone where Tesla reversed to adjust and XPENG judged the gap and went. That is the scoreline: two systems that both worked, with different margins. The technology underneath is more interesting.

A cloud teacher, a car-sized student

The essay's central claim is architectural. Most Chinese driver-assistance systems that went the large-model route use a two-stage design: cameras capture the scene, a vision-language model converts what it sees into text-like tokens, and a planner reasons over those tokens before issuing a driving action. That intermediate language layer is convenient for humans to inspect and expensive for a car: it adds latency between seeing and acting, and it ties the system to the road signs and traffic language of the country it was trained in.

XPENG's second-generation VLA, according to its launch material and to Liu Xianming, who runs the company's General Intelligence Center, removes that layer. The chain becomes visual input → physical geometry and motion understanding → driving action, with the claim that end-to-end decision latency falls from roughly 200 ms to under 80 ms and inference efficiency improves 12-fold. Whether those exact numbers survive independent measurement is open; the design choice is what matters, because the physics of a pedestrian stepping out or a truck braking does not change between countries, while the text on a sign does.

Then there is time. The August 2026 upgrade added what XPENG calls Infini-VLA, which keeps about 30 seconds of road context in the model, and X-Foresight, a world model that predicts about six seconds ahead. Both run on the car, in a streaming, autoregressive way: the car is not waiting for a cloud round-trip to decide. That is the edge half of the architecture, and it is the half a driver actually feels.

The compute asymmetry

The essay's numbers on the cloud side are the loudest, and the least checkable. XPENG has publicly described a 72B cloud foundation model — a scale that is unusual for driver assistance and one the company has talked about since 2025 — and the essay adds claims that XPENG keeps its training clusters at 90% utilisation, runs a full retraining cycle about every five days, and operates roughly 10 EFLOPS against Tesla's 100-plus.

The last three are the essay's arithmetic, not published figures, and should be read as such. But the asymmetry it describes is real in direction: Tesla's Cortex cluster is a very large, US-based training asset, and export controls make it hard for a Chinese manufacturer to buy the same class of Nvidia compute at the same scale. XPENG's answer is to spend less on cloud and more on the car: train the big model in China, distill what it has learned into a model small enough to run on the vehicle, and add on-car compute.

That is what the Turing chip is for. New global models get three of them, 2,250 TOPS combined, with the L03 onwards as the reference. The essay claims 216 GB of shared memory and a 30B-parameter local model; XPENG's public material says the chip can run models up to 30B, and the G9L launch described a 3.5× increase in on-car model parameters without giving a parameter count. The confirmed hardware number is 2,250 TOPS. The distillation pipeline is the bridge between the cloud model and that hardware, and it is also why the trim levels differ: on the L03, the Max variants get one Turing chip with 750 TOPS and a VLA Lite model, while the Ultra variants get two chips, 1,500 TOPS and the full VLA. Below the three-chip cars there is a real ceiling, and the trim you buy determines which one you get.

The last piece is the compiler. XPENG says its Turing chip is a domain-specific architecture that went into mass production in 2025 — the essay dates the first Turing DSA to 2025 — and that hardening model operators into silicon, and keeping the compiler from falling back to slower generic paths, is a year-long engineering grind that money alone does not shorten. That claim is hard to verify from outside, but it explains why the company frames its lead as engineering time rather than a single benchmark. It is also the part of the story with a commercial footprint: Volkswagen is reported as the first external customer for the second-generation VLA, a software relationship rather than a wholesale switch of VW's compute hardware.

What that means on Australian roads

Australia is one of the markets XPENG says it designed the L03 for, not one it adapted afterwards. The car launched here and in New Zealand on 12 October from A$41,900, with the extended-range version alongside the battery-electric one: a 37.2 kWh pack and a 1.5-litre engine, 215 km of WLTP electric range and 1,017 km combined, 178 kW and 0–100 km/h in 6.8 seconds, and 123 kW DC charging. It is the first XPENG sold here with the company's in-house AI stack under the skin, and the first from China and the APAC region to integrate Google Maps Auto SDK.

The hardware distinction matters more than the price. XPENG's Australian material says the L03's Ultra variants run two Turing chips with up to 1,500 TOPS, and that the second-generation VLA is planned to arrive overseas by over-the-air update from 2027. Australian reporting puts a finer point on it: only the L03 Performance Ultra carries the NGP-ready Turing hardware, while the rest of the range runs XPilot — adaptive cruise, lane centring, lane-change assistance, traffic-sign recognition and parking assistance. If you buy a lower L03, you are not buying a car that will later receive the full VLA system; the hardware for it is not in the car.

The Australian rollout is not waiting on an approval. Cars with adaptive cruise, lane centring and lane-change assistance are already sold here, and a supervised system of this kind is not the point at which Australia's vehicle rules need to clear it; the automated-vehicle safety reforms being developed by the National Transport Commission are aimed at higher levels of automation, where the car rather than the driver is responsible. XPENG's NGP with VLA 2.0 is a supervised L2++ system: the driver remains responsible. What is missing in Australia is the software release — XPENG's global VLA 2.0 rollout, planned by over-the-air update from 2027 — and the hardware, the Performance Ultra's dual Turing chips. Those are product and supply decisions, and they explain the 2027 date better than any regulatory queue.

The other side of deploying here is calibration, and XPENG has been doing it. It says it has been testing and calibrating XPilot on Australian and New Zealand roads since early 2026, with three named priorities: avoiding vulnerable road users, understanding local road signs, and understanding what its local team calls implicit traffic rules — the things Australian drivers do that are not written in a rulebook. Parking is being adapted to shopping-centre carparks, tight kerbside spaces and home garages. The company's wider local programme covers vehicle dynamics, software, data, mapping and navigation, and it continues after launch. The L03 was engineered to meet five-star safety standards in China, Europe and Australia simultaneously, which for a family SUV here matters at least as much as the compute headline.

Data is the quieter deployment question. XPENG's European approach, as the essay describes it and as Liu Xianming has discussed publicly, is to train the 72B base model in China and then adapt it per country using a very small local dataset — about 1/10,000 of the foundation-model data, with roughly two weeks of work per new European country, according to Liu's Bloomberg interview. For Australia the same architecture applies, but the compliance frame is different: Australia has no general data-localisation mandate, while the Privacy Act's Australian Privacy Principles require transparency about cross-border disclosure and reasonable steps before personal information goes overseas. Running the local adaptation on Australian cloud capacity — AWS has a Sydney region, as do Alibaba Cloud and Azure — is technically straightforward; whether XPENG does it locally or in China is a policy choice, not a physics constraint. The company has not said which it will do here.

What does the edge-versus-cloud split mean for an Australian owner in practice? It means the car's driving decisions do not need mobile coverage, which matters on the Hume between towns and on regional roads where signal drops. It means map and voice features still depend on connectivity, which is why XPENG's executives have talked about offline voice support in markets where data is expensive and carriers bill slowly. And it means the quality of the local adaptation — the two-week, small-dataset recipe — is the thing that determines how the car behaves on a country road with no lane markings, or in a car park in Penrith, rather than the number of TOPS on the brochure.

What to watch

• The 2027 L03 Performance Ultra deliveries. Whether the VLA 2.0 over-the-air update arrives on the timetable XPENG has given, and whether every Performance Ultra sold here has the hardware it needs.
• What happens to the rest of the range. Max trims and older Orin-based G6 and G9 cars in Australia have no committed path to the full model; the distilled Orin version XPENG has discussed is a China rollout.
• Where the data is processed. A local-region training/adaptation announcement would tell Australian buyers more about the long-term commitment than any statement about the car's compute.
• The higher-automation tail. The NTC's automated-vehicle reforms and the UN ADS GTR matter for L3 and beyond; they are not what stands between an Australian buyer and supervised VLA 2.0.

The original post

The essay is 彦山堂's "Paris Revenge", published on Weibo on 29 October 2026 (uid 5365308769; part one of a series; 3 likes, 0 reposts, 0 comments at the time of writing). Its technical section reads as three layers — the language-free VLA 2.0 architecture, the cloud-versus-edge compute strategy (72B cloud teacher, 2,250 TOPS of Turing silicon on the car, rented overseas cloud for European adaptation under GDPR), and the compiler work that turns operators into silicon — and it closes with a trailer for a second part on Chinese rivals' driver-assistance organisations.

Read the original: 彦山堂 on Weibo.