Autonomy Insiders

Europe's first fully driverless commercial robobus runs in France. beti is a French operator of automated mobility networks, and a spin-off from Bertolami, a family coach business that has moved people around rural France for 75 years. CEO Benjamin Baudet explains the layer of the autonomous driving industry nobody photographs: the people and software that keep a driverless bus service running once the driver is gone.Before beti existed, the family studied its own routes and asked a simple question — if the driver is no longer on board, who does everything else? They counted 421 daily tasks that had nothing to do with driving. Autonomous driving technology replaces the driving task. It does not replace the operator. That finding became the company.What beti sells is people and software: field teams trained to deploy someone else's autonomy, plus two in-house platforms — OperaVision for the ground crew and HyperVision for remote monitoring. The conversation gets into the fleet operations numbers this layer rarely publishes: four vehicles per hypervisor on two-hour rotations, roughly 20% of operating effort spent on cleaning, charging, depot work and roadside recovery, and around 30% lower operating cost than a service with a driver — but only above eight hours a day and seven days a week.In October 2024 beti flew to Guangzhou to argue it was the right size of European partner. Four months later the Valence TGV robobus line launched with WeRide and Renault. Adapting a robobus designed for the Chinese market took a year of closing gaps on language, interfaces and data protocols. Plus: how French driverless permits came through in three months, why Keolis, Transdev and RATP are customers rather than competitors, how beti is preparing for robotaxi and goods transport alongside public transport, and the 2030 target Benjamin uses to measure success.This show is the interview half. The analysis lands every Monday in the newsletter. Free: https://avmarketstrategist.substack.com/?utm_source=youtube&utm_medium=description&utm_campaign=ep27TIMESTAMPS0:00 - open: the gap in the leading pack is narrowing0:59 - The service layer nobody photographs1:53 - What beti actually sells2:24 - Why a family coach operator started an autonomy company3:32 - The 421 tasks that are not driving5:01 - What transfers from a 75-year-old bus business6:00 - The turnkey offer: people plus two software platforms7:37 - Hypervision vs. teleoperation, and who owns the driving8:52 - Why the control room sits in the same country9:16 - Training customers to not need you10:16 - What operators underestimate11:12 - Four layers, and the two beti refuses to enter12:13 - How many vehicles one hypervisor can handle13:38 - What caps the ratio: human attention14:18 - The ground crew: 20% of operating effort14:54 - What stops WeRide or Renault building this themselves15:55 - Valence 2025: how the WeRide deal came together17:00 - Why that route, and the riders who became ambassadors18:59 - Driverless permits in three months19:59 - Rebuilding a Chinese robobus for Europe22:02 - Navya, EasyMile, WeRide: a 20-criteria operator framework23:31 - Roland-Garros 2026: a 100% beti operation25:00 - Who the customer is, and who writes the cheque26:11 - 30% below a driven service, with conditions27:18 - When your supplier goes under28:58 - Keolis, Transdev, RATP: customers, not competitors30:13 - The 2030 target: 2,000 hypervision licences

Everyone measures robotaxi progress in miles driven. Almost nobody measures the hours the vehicle spends not driving. George Kalligeros, co-founder and CEO of Aseon Labs, is building a robot that compresses a depot into a single parking space.When a robotaxi drops below its charge threshold, it leaves the zone it is earning in, drives three to five miles to a depot, queues, gets serviced, and drives back. In San Francisco, a compact city with unusually good infrastructure, that is roughly two hours out of service, and it happens several times a day. The driving stack is fully autonomous. Everything around it is still humans, real estate and deadhead miles.Aseon's answer is a six-metre box that occupies one charging bay, holds two six-axis robotic arms, and completes a reset in twenty to thirty minutes: inspection, charge, interior clean, item retrieval, data sync and reboot. George is unusually direct about what version one does not do. No exterior wash. No sensor detailing. Anything genuinely unpleasant goes back to the depot.Daniel Abreu Marques presses on the parts that decide whether this is a business or a demo: why Aseon operates a network instead of selling boxes, how the project-company and asset-backed financing model is designed to pull AV operators into owning part of their own infrastructure, and why a pod needs only about five resets a day — roughly 10% utilisation — to break even.The wider argument is the one this show keeps returning to. If more than half the cost of a robotaxi service sits in infrastructure and operations rather than in the driver, then autonomy economics are settled off the road, not on it. And once cities start tendering licences with a cap on vehicle numbers, "drive somewhere cheaper to charge" stops being a strategy. As George puts it: the infrastructure has to meet the vehicle, not the vehicle be taken to the infrastructure just because it drives itself.Plus: what four years at Tier taught him about who you can actually incentivise, why Europe's density makes it the natural market for this product, and why he is building the company in California anyway.TIMESTAMPS 0:49 - Introduction 1:26 - What Aseon is, and what an operator actually buys 1:52 - Inside the box: one bay, two robotic arms 2:41 - A 20-30 minute reset, bounded by charge rate 3:29 - What it replaces: two hours out of service, several times a day 4:50 - What they found inside real AV depots 5:31 - A third of the fleet offline at any given time 6:44 - Four years at Tier, and who you can actually incentivise 7:50 - Which jobs version one does, and which it refuses 9:47 - Interior resets: the 90% a robot can close out 10:55 - Getting power into a dense-city parking bay 12:00 - One pod, many platforms: ID Buzz down to Cybercab 13:55 - Orchestration: no queuing, just-in-time only 14:51 - When the pod fails with a vehicle inside 15:52 - Why Aseon runs a network instead of selling boxes 18:07 - How operators pay, and what makes it bankable 19:08 - Five resets a day: the utilisation math 21:02 - Where the $10M goes, and what 2027 has to prove 21:38 - $50M a metro: from venture equity to asset-backed debt 22:48 - Movable, permittable, live in eight weeks 23:55 - Lyft, Avis, Move: why route into a third-party network 25:20 - What stays in-house 26:14 - Are AV depots the new data centres? 27:39 - Is the cost really decided off the road? 28:55 - Curb space, cities and the traffic externality 30:53 - Europe: why build in the US, and when Aseon arrives here 32:52 - The one metric for the next twelve months

France already has a working legal framework for approving driverless public transport. Most of the industry has never heard of it. Aryldo Russo of GESTE Engineering takes it apart piece by piece.Getting a vehicle type approved in Europe is one problem. Getting a driverless service running on a specific street, with a control room behind it and a city that has to agree, is a completely different one. France solved the second problem by writing its rules into the transport code rather than vehicle law, and handing the job to the national technical service that already oversaw metros and tramways.That inheritance shapes everything. The system is assessed as a whole, not as a vehicle: six domains covering onboard safety, connectivity and positioning, cybersecurity, road infrastructure, vehicle behaviour and operations, plus a seventh that consolidates them into a single verdict. Three sequential dossiers carry a project from generic capability to a specific route. And the safety bar is inherited from rail: globally at least as safe as the service being replaced, measured against national statistics rather than one bus route.Aryldo explains what happens when an operator calls, what counts as evidence, and why a million kilometres of driving proves less than teams expect. We also cover why the law refuses to name a vehicle-to-operator ratio for remote supervision, whether French cybersecurity rules duplicate UN R155, how you assess an end-to-end driving system you cannot decompose, where the seam sits between EU type approval and national authorisation, whether Brussels should use the French model as its template, and whether Europe's assurance layer is a safety asset or a competitive handicap against Waymo and Chinese operators.Plus the number nobody publishes: roughly what the whole safety demonstration costs as a share of the project.TIMESTAMPS 0:00 - Type approval is one problem. Running a service is another 1:09 - The French technical service, and its metro and tram origins 2:46 - What rail engineers see that automotive teams miss 3:45 - What actually happens when a project calls you 5:19 - The seven domains of the assessment 6:56 - Independence: assessor and engineering support at once 8:29 - What counts as an automated road transport system 9:35 - Built through the transport code, not vehicle law 10:46 - The remote intervener and the service organiser 12:02 - Predefined routes, zones, and whether Paris fits 13:36 - GAME: at least as safe as what it replaces 14:54 - National statistics, or one specific route 15:26 - Who signs: the operator, the mayor, the assessor 16:23 - Three dossiers: DCST, DPS, final safety case 19:17 - When to call an assessor, and the cost of calling late 20:45 - Remote supervision: why the law names no number 22:10 - Do remote operators have to sit in France 22:47 - French cybersecurity rules vs. UN R155 24:17 - Why a million kilometres proves very little 26:49 - Traceability when behaviour comes from data 28:26 - The seam between EU type approval and French rules 29:51 - Should Brussels use the French model 31:07 - What changes when it is a truck, not a shuttle 32:14 - How long it takes and what it costs 33:26 - Waymo, China, and whether assurance is a handicap 34:36 - The one thing he would changeLINKSThe AV Market Strategist (my weekly AV analysis) - https://avmarketstrategist.substack.comAryldo on LinkedIn: https://www.linkedin.com/in/aryldogrussojr/#AutonomousDriving #Robotaxi #DriverlessVehicles #MobilityPolicy #AutonomyInsiders

WeRide CEO Tony Han on where robotaxis actually break even, how the Uber partnership works in Abu Dhabi, and why Europe could be profitable from day one.Most robotaxi conversations cover one city, maybe one country. Tony Han runs a company that has tested or operated in more than 60 cities across 13 countries and holds autonomous driving permits in eight of them. Daniel Abreu Marques sits down with the co-founder and CEO of WeRide — the Nasdaq and Hong Kong dual-listed operator behind robotaxis, robobuses, robovans, robosweepers and a fast-growing ADAS business — to get specific about the numbers.This is a conversation about business models, not demos. Where each product line makes money, how deployment decisions actually get made, what regional break-even means in practice, and why Tony believes almost none of his L2 competitors qualify as robotaxi companies at all.You'll discover:Where WeRide is at or near break-even today, and why Europe's higher taxi fares change the math from day oneHow the three-way Abu Dhabi structure works, and who actually decides how many vehicles run on a given dayWhat happened to rider behavior after Uber launched a dedicated autonomous category — and why the surprise wasn't what you'd expectWhy more than 80% of last quarter's new vehicles went to robotaxis rather than the other four product linesThe "qualification process" Tony proposed a year ago, and why he argues no L2 competitor has passed the reverse version of itWhy WeRide refuses to build robotrucks or mining trucks despite the obvious adjacencyHow WeRide selects European launch cities — population, taxi density, regulator openness, and one factor most operators ignore entirelyWhy he calls the L4-to-L2 move a "projection" and the L2-to-L4 climb a "lifting" problemTony also gets into the parts of the story that rarely make the earnings call: the sabbatical that turned into a Baidu AI Lab role, why he left a tenured professorship for a company with no business plan, what Taoism and Bertrand Russell have to do with building autonomous systems, and why a live connection hiccup during the recording turned out to be the best possible illustration of the physical AI reliability problem.For anyone tracking where autonomy goes next — from the Middle East build-out to Spain, Slovakia, Denmark and the open question of Germany — this is the operating picture behind the headlines.Timestamps0:56 - Introduction 1:58 - Leaving a tenured professorship 2:15 - Baidu AI Lab, Andrew Ng, and an unexpected desk mate 6:36 - What philosophy has to do with autonomous driving 9:05 - Five product lines, five business models 15:15 - Why WeRide won't build robotrucks 17:52 - Inside the 3,400-vehicle fleet 18:46 - How WeRide decides what gets deployed where 21:19 - Who owns the vehicles: asset-light vs. own fleet 22:32 - The Middle East doubled in one quarter 23:13 - Abu Dhabi: how the Uber partnership actually works 24:50 - What changed when riders could choose a robotaxi 26:48 - Business class at taxi prices 28:44 - Europe: Spain, Slovakia, Denmark and what comes next 30:26 - How WeRide picks a European city 32:44 - Germany, Wittgenstein and a robotaxi in Stuttgart 34:01 - Unit economics: where WeRide breaks even 36:22 - Physical AI vs. digital AI 39:03 - L4 to L2: projection, lifting and the qualification test 42:45 - What separates the long-term winners 44:31 - Closing: a live lesson in reliability

This video is sponsored by TaskUS.Autonomous fleets do not scale on software alone. The hidden advantage is the human layer and Nick Allen reveals how TaskUs powers the remote assistance, safety, validation, and emergency response that keeps robotaxis moving when the real world gets messy.If you think autonomy is just about removing people, this conversation flips that script. Daniel Abreu Marques sits down with Nick Allen, Head of Autonomous Vehicle Mobility and Logistics Solution at TaskUs, to unpack why the most successful AV operators are building human support into the stack from day one, not bolting it on after launch.You'll discover:Why the best AV fleets treat humans as the "central nervous system" of the operationHow remote assistance differs from remote driving, and why that distinction matters for safety and scaleThe cost math behind human-in-the-loop operations, including how teams can shrink cost per mile by 30% to 50%What a healthy vehicle-to-operator ratio looks like in commercial AV today, and why it changes by city, weather, and ODDHow edge cases, emergency response, and rider support actually work in the first 60 seconds of a real incidentWhy Europe's regulatory patchwork is creating both friction and opportunity for AV expansionNick also breaks down the less visible but essential parts of the job: high-fidelity sensor labeling, scenario reconstruction, fleet management, training and recertification, resiliency support for operators, and the hybrid model TaskUs uses across customer sites and its own facilities.We also get a look at the next wave. From Manchester to the broader UK and Europe, Nick explains why localization, GDPR, and country-by-country compliance are reshaping deployment strategy, and why AV is becoming a direct on-ramp to robotics and humanoid systems.Find Nick here: https://www.linkedin.com/in/nicholasjallen/TaskUs here: https://www.taskus.com/services/autonomous-vehicle-operations/Timestamps:01:39 TaskUs in the AV Ecosystem: From Data Annotation to Operations Coordination03:30 Why Autonomous Vehicles Still Need Human Support04:18 Cost per Mile and the Right Operator-to-Vehicle Ratio05:30 When AV Companies Should Bring in Operational Support06:36 Data Annotation and Training for Complex Edge Cases07:47 Remote Assistance Explained: How the Command Center Works09:01 Remote Driving vs. Remote Assistance10:41 Latency, Safety, and Commercial Operator Ratios13:09 Training and Qualification for Remote Assistance Teams14:15 Own Sites or Customer-Side Operations?15:21 Edge Cases and Emergency Response on the Road17:47 Training, Compliance, and “Learning as a Service”19:21 Business Models, Customers, and the Path to Commercialization21:26 The Biggest Challenges in Scaling Autonomous Mobility23:10 Global Teams, Quality, and Resilience in AV Operations28:29 TaskUs’ Europe Strategy and Market Entry31:40 Localization, Regulation, and Data Privacy in Europe35:09 The Future of Human-in-the-Loop and Robotics38:32 Closing#AutonomousDriving #Robotaxi #AutonomousVehicles #RemoteAssistance #FleetOperations #AutonomyInsiders