Skip to main content

 

The Real-World AI Lab: FSD and Optimus Generate Physical-World Training Data No Competitor Can Replicate

6.9 billion FSD miles. Unsupervised robotaxi live in Austin, Dallas, and Houston. Cybercab entering mid-2026 production. Optimus targeting 100,000 units. Tesla is building the AI dataset that text and image models cannot touch — and betting the company on what that data is worth.

By Francis Avorgbedor | Azure Engineer  ·  July 4, 2026  ·  14 min read  ·  Tesla · Physical AI · FSD · Robotics
70
SEVENAI Momentum Score
▲ +1 — Rank #6
6.9B
FSD miles accumulated — irreplaceable training data
▲ Growing daily
3
Cities with live unsupervised robotaxi operations in 2026
▲ Expanding
100K
Optimus robots targeted for 2026 production
▲ Ramp beginning

Tesla does not belong in a conversation about AI companies the same way Nvidia, Microsoft, or Google do. It does not build foundation models that power enterprise software. It does not run a cloud platform hosting AI workloads. It does not have a research organisation producing academic papers that move the AI benchmark leaderboards. What it has is something none of those companies can buy, build, or replicate at speed: 6.9 billion miles of real-world physical driving data, generated by a fleet of vehicles that serves as the world's largest distributed AI training system — operating continuously, at no additional cost to Tesla beyond the vehicles already sold.

In the SEVENAI Momentum Index, Tesla holds Rank #6 with a score of 70 — up one point this week, and the most difficult company in the index to score precisely. The challenge is not that Tesla's AI assets are unimpressive. They are extraordinary by any objective measure. The challenge is that the gap between what those assets could be worth if the robotaxi and Optimus bets succeed, and what they are worth today as revenue-generating businesses, is one of the widest in the Magnificent Seven. Tesla is playing a longer game than any other company we track. Whether that game is genius or hubris depends almost entirely on regulatory outcomes and execution timelines that are genuinely uncertain.

The data flywheel — why physical-world AI data is categorically different

Tesla's physical AI data flywheel
Step 01
Sell vehicles that generate data
Every Tesla on the road is a sensor array generating camera, radar, and ultrasonic data from real driving situations — edge cases, unusual weather, unpredictable pedestrians, complex intersections. Fleet of over 500,000 FSD-capable vehicles operating globally.
Step 02
Aggregate into training data no one else has
6.9 billion miles of accumulated FSD data. Processed through Dojo — Tesla's exascale training supercomputer running 50,000+ H100 GPUs — to extract the edge cases and unusual scenarios that matter most for improving autonomous capability.
Step 03
Train better models, deploy to the fleet
FSD V14 deploys with 4.5x more parameters than V13. Each iteration makes the entire fleet smarter overnight via over-the-air updates. Safety improves. Capability improves. More FSD subscribers choose to stay subscribed.
Step 04
Better FSD sells more vehicles and generates more data
Safer FSD attracts more subscribers at $199/month. Better FSD enables Cybercab and robotaxi commercial deployment. More vehicles on the road generate more training data. The loop compounds at a rate no competitor entering with a smaller fleet can match.

The flywheel logic is the foundation of Tesla's position in the AI race. No company building autonomous systems from scratch in 2026 can acquire 6.9 billion miles of real-world driving data at any price. Waymo — Google's autonomous vehicle subsidiary and Tesla's most capable direct competitor in consumer robotaxi — has accumulated tens of millions of miles. Tesla has accumulated hundreds of times more. That gap is not closeable through hiring, investment, or technical capability alone. It is closeable only through time — which is why Tesla's data moat is the most durable structural advantage in physical AI, even if it is the hardest to value commercially.

The robotaxi — from pilot to production in 2026

Tesla's robotaxi programme moved from concept to commercial operation in 2025 and is now expanding in 2026 at a pace that is finally converting years of FSD development into actual revenue-generating rides.

October 2024
Cybercab unveiled at "We, Robot" event
Purpose-built robotaxi — no steering wheel, no pedals, two seats, Hardware 5 (AI5) platform. $30,000 target production cost. Musk claimed it would be cheaper to ride than taking a bus.
June 2025 — Live
Robotaxi service launches with human safety monitors in Austin
Modified Tesla Model Y vehicles. $4.20 flat fare. Human safety drivers present. The first commercial Tesla robotaxi rides.
January 2026 — Live
Unsupervised vehicles integrated into Austin fleet
The first fully unsupervised Tesla robotaxi rides. No safety driver. Full Level 4 autonomy in designated operating areas. The moment Tesla's years of FSD data accumulation became a commercial product.
April 2026 — Live
Unsupervised expansion to Dallas and Houston
Per Tesla's Q1 2026 8-K: "We further expanded our unsupervised operation area in Austin and launched unsupervised rides in both Dallas and Houston in April." Three cities now running unsupervised autonomous rides.
Mid-2026 — In production
Cybercab volume production begins
Cybercab enters production mid-2026. "Once in production, we expect that Cybercab will begin to replace the existing Model Y fleet and will be the largest volume vehicle in the fleet over time." Purpose-built hardware replacing the Model Y improvisation.
H2 2026 onwards
Additional major US metros — testing and permitting underway
Tesla's Q1 2026 filing: "We continued laying the groundwork for expansion of our Robotaxi service to additional major U.S. metros, including testing and permitting, allowing us to quickly launch new markets once we are ready."
✓ The FSD safety data — the regulatory argument Tesla can now make

Tesla has 6.9 billion miles of data from Teslas driven with supervised FSD. That data consistently shows FSD achieving substantially better safety performance than human drivers — Tesla claims its FSD is already over ten times safer than human drivers on the metrics it publishes. Critics note that unsupervised deployment data is much smaller — it was not until recently that Tesla had any unsupervised robotaxis in service. But the supervised FSD safety record is the foundation of the regulatory argument for expanding unsupervised deployment to new markets. Every additional mile of unsupervised operation in Austin, Dallas, and Houston strengthens that argument.

Optimus — from demo to 100,000 units

Tesla's Optimus humanoid robot is the most audacious bet in the Magnificent Seven — not because humanoid robots are technically implausible, but because the timeline between demo and commercial scale has historically been the place where robotics companies fail. Tesla is betting that its manufacturing expertise, its AI training infrastructure, and the same data-flywheel logic that made FSD progressively more capable will combine to make Optimus the first humanoid robot to reach commercial scale.

The target for 2026 is 100,000 Optimus units — a production number that would make it one of the fastest hardware ramps in Tesla's history. FSD subscriptions fund and generate data for better AI models; those models are then reused in Optimus and potentially external AI services, which in turn create more data and value. The cross-pollination between FSD's vision and decision-making systems and Optimus's physical manipulation and navigation tasks is the AI synergy that no other humanoid robot programme can match — because no other humanoid robot programme is run by a company that also operates the world's largest real-world AI training fleet.

AI foundation
Same vision AI as FSD
Optimus uses the same camera-based vision system and neural network architecture as FSD. Real-world driving data trains the perception models that Optimus uses to navigate physical environments. Cross-pollination between the two programmes creates compounding capability gains.
2026 production target
100,000 units by year-end
From a standing start in 2025's limited production to 100,000 units targeting deployment in Tesla's own factories first — where each robot generates additional training data in controlled environments. By 2027, Optimus could assemble its own successors.
Commercial logic
Physical labour at $0.30/hour equivalent
Analysts estimate a cost per labour-equivalent hour that would be transformative for manufacturing economics. Tesla's manufacturing expertise gives it a structural production cost advantage over competitors building humanoid robots for the first time.
The big bet
Humanoid robots as the ultimate AI revenue model
If Optimus reaches commercial scale, it represents a recurring revenue model from physical AI that no software or cloud company can match — a physical product that gets smarter with every additional unit deployed, creating a self-reinforcing improvement loop in the real world.

Dojo — Tesla's own AI supercomputer

Tesla's Dojo exascale computing system is the infrastructure layer that makes FSD's continuous improvement possible. FSD V13 was enabled by Cortex — Tesla's training cluster running 50,000 H100 GPUs — which processes 4.2x more data than prior versions. Dojo extends that capability with Tesla's own custom AI training chips, designed specifically for the video processing workloads that FSD training requires. The decision to build Dojo rather than rely entirely on Nvidia's cloud infrastructure reflects the same logic that drives Google's TPU and Amazon's Trainium programmes: the company that controls its own chips controls its own training costs and roadmap.

Dojo is less commercially mature than Google's TPU or Amazon's Trainium at this stage — Tesla has not announced plans to sell Dojo compute capacity to third parties at scale. But it represents a genuine infrastructure independence from the Nvidia dependency that constrains every other AI company's training economics.

"Tesla's data loop, fueled by FSD and Optimus, could make it the Microsoft of autonomous tech. Tesla isn't just an EV company anymore — it's an AI company with wheels."

— AI investment analysis, 2025

The score constraint — why Tesla sits at 70

Tesla's score of 70 — the second lowest in the SEVENAI index — reflects a straightforward reality: the gap between Tesla's AI asset value and its current AI revenue is wider than any other company in the race. The FSD data moat is real. The robotaxi programme is live. Optimus is beginning to ramp. But the revenue from these programmes today is a fraction of what they would need to generate for Tesla to compete commercially with companies whose AI investments are already generating measurable cloud, model, and enterprise revenue.

FSD subscriptions at $199/month across an eligible fleet represent a meaningful revenue line — but not a dominant one. Robotaxi rides in Austin, Dallas, and Houston are generating early commercial revenue but not at a scale that moves Tesla's overall financial profile yet. Optimus at 100,000 units in 2026 is impressive if achieved, but even at commercial pricing the total revenue would be a small fraction of Tesla's automotive business, let alone comparable to Azure's $37 billion quarterly run rate.

The honest constraint on Tesla's score is time horizon. The thesis is correct: physical-world AI data is categorically different from text and image data, the FSD flywheel is real, and Optimus's commercial potential is extraordinary if it executes. But "if it executes" and "on what timeline" are the two questions that keep Tesla at 70 rather than significantly higher.

⚡ The regulatory risk — the thesis-breaker no timeline can predict

Every element of Tesla's AI commercial thesis depends on regulatory outcomes that Tesla does not control. Unsupervised FSD deployment in new US markets requires state-level regulatory approval that does not follow a predictable timeline. European FSD approval is targeted for 2026 but has repeatedly slipped. Cybercab volume production beginning in mid-2026 will be commercially irrelevant without regulatory approval for unsupervised operation in the markets where it would operate.

Analysts and investors describe this as the "thesis-breaker" for Tesla's AI bull case: if unsupervised FSD deployment is cancelled or delayed beyond 2027 in major US markets, it eliminates robotaxi revenue and reduces Tesla to an expensive automaker. Tesla has 6.9 billion miles of safety data to support its regulatory case. It does not control the pace at which regulators act on that data.

⚠ The Musk distraction factor

Elon Musk's involvement in US government — the DOGE programme and his public political positions — has created a customer sentiment challenge for Tesla in 2026 that is distinct from any AI competitive risk. European sales declines have been attributed in part to boycotts linked to Musk's political activity. The brand damage in key markets reduces the vehicle sales that generate the FSD data that powers the AI flywheel. This is not an AI story — it is a CEO reputation story that creates AI consequences. SEVENAI tracks it because it directly affects the fleet size and data generation rate that underpin Tesla's AI moat thesis.

CompanyStrategyScoreWk
Nvidia
NVDA · AI Infrastructure
The track every company races on. CUDA moat. $500B backlog.97▲+2
Microsoft
MSFT · Enterprise AI
OpenAI partner, Azure 40% growth, 450M M365 seats.89▲+3
Alphabet
GOOGL · AI Research
Full stack. DeepMind. TPU. Cloud 63% growth. $460B backlog.81—0
Meta
META · Open-Source AI
Llama 650M downloads. $125B capex. 3.9B users.78▲+4
Amazon
AMZN · Cloud AI
AWS Bedrock neutrality. $13B Anthropic. $225B Trainium commitments.74—0
Tesla
TSLA · Physical AI
6.9B FSD miles. Cybercab in production. Optimus ramping. Robotaxi live.70▲+1
Apple
AAPL · On-device AI
2.2B devices. Privacy-first. On-device constraint limits ceiling.61▼−2
What to watch
  • 01Cybercab volume production ramp. Mid-2026 Cybercab production beginning is the most important near-term milestone in Tesla's AI commercial story. The pace of the production ramp, the per-unit cost as volume scales, and any regulatory approvals for Cybercab-specific operations will determine whether 2026 becomes the year Tesla's robotaxi thesis transitions from proof-of-concept to commercial trajectory.
  • 02Unsupervised FSD expansion beyond Texas. Austin, Dallas, and Houston are operating. California, Nevada, and major East Coast metros are the next logical expansion targets. Each new state where Tesla receives unsupervised FSD regulatory approval expands the serviceable market and adds new driving environments to the training data. Watch for any state-level regulatory announcements regarding unsupervised FSD approval.
  • 03Optimus production numbers vs 100,000 target. The 100,000 unit target for 2026 is the most aggressive hardware ramp in Tesla's history outside of core vehicle production. Any quarterly production disclosure — or earnings call commentary on Optimus production pace — will reveal whether the target is tracking or slipping. A 50,000-unit delivery in 2026 would still be commercially significant; a significant shortfall would raise questions about the timeline for commercial-scale Optimus deployment.
  • 04FSD subscription revenue disclosure. FSD subscriptions at $199/month across the eligible fleet are moving to subscription-only per Tesla's Q1 2026 filing. Record net new subscriptions were announced in Q1. Any disclosure of total FSD subscription revenue — or implied subscriber count — would allow SEVENAI to assess whether FSD is becoming a meaningful software revenue line for Tesla or remaining a modest attachment to vehicle sales.
  • 05European FSD regulatory progress. Tesla targets supervised FSD approval in Europe in 2026. European sales have been challenged by the Musk brand dynamics, and regulatory approval for FSD would be both a practical and a narrative milestone — demonstrating that Tesla's safety data is compelling to regulators in the world's second-largest auto market. Any European regulatory decision on FSD supervised or unsupervised operation would move Tesla's score materially.

The bottom line

Tesla is the most unusual company in the Magnificent Seven AI race precisely because it is the only one competing in a category that does not yet commercially exist at scale. Physical-world AI — the intersection of computer vision, real-time decision-making, and embodied robotics operating in unstructured environments — is the hardest AI problem and the one with the most valuable eventual prize. The company that can train AI systems on billions of miles of real driving data, deploy those systems in purpose-built hardware at manufacturing scale, and extend the same AI stack to humanoid robots that work in every environment humans work in — that company owns the most valuable AI infrastructure of the 2030s.

Tesla's score of 70 reflects where it is today. The thesis, if it executes, points to a score that looks very different in two to three years. The race has no finish line. For Tesla, the race has barely started.

Popular posts from this blog

The Cloud Incumbent: AWS Bedrock Hosts Every Frontier Model and Amazon Is Betting on Neutrality AWS at $37.6 billion quarterly revenue, growing 28%. $13 billion invested in Anthropic. A $100 billion Anthropic-to-AWS commitment. Trainium with $225 billion in customer revenue commitments. The most quietly powerful AI strategy in the race. By Francis Avorgbedor | Azure Engineer  ·  July 4, 2026  ·  14 min read  ·  Amazon · AWS · Cloud AI 74 SEVENAI Momentum Score — Rank #5 $37.6B AWS Q1 2026 revenue — 28% YoY growth ▲ Fastest in 15 quarters $13B Total Amazon investment in Anthropic to date ▲ Strategic anchor 100K+ Customers running Claude on AWS Bedrock ▲ Distribution moat Amazon's AI strategy is built on a thesis that every other Magnificent Seven company is testing against — and that Amazon is uniquely positioned to win regardless of the outcome. The thesis is neutrality. In a race where Microsoft has bet on OpenAI, Google has bet on Gemini, and Meta has bet...
Performance Fix Foundry Local 1.2 Linux ARM64 Embeddings Offline ASR The Edge Latency Drop: Fixing Latency Spikes by Offloading Embeddings to Foundry Local 1.2 You are paying a full cloud round trip — network, TLS, queue, throttle risk — to turn a twelve-word search query into a vector. That is the most expensive way possible to do one of the cheapest computations in your stack. Foundry Local 1.2 now runs on Linux ARM64, which means embeddings and speech recognition can happen on a Raspberry Pi, a Jetson, or a Graviton instance — offline, unmetered, and in single-digit milliseconds. The failure signature this guide resolves # Application Insights — the embedding call, not the LLM, is your tail latency: name p50 p95 p99 calls/day POST /embeddings (cloud) 89 ms 412 ms 3,847 ms 1,240,000 POST /chat/completions (cloud) 940 ms 1,720 ms 2,910 ms 38,000 ^^^^^^^^ ...
  The 500GB System File That Eats Your Hard Drive Something on your Windows 10 drive is consuming hundreds of gigabytes and the normal tools cannot find it. This guide identifies every known culprit — from hibernation files and shadow copies to runaway backups and the Windows component store — and tells you exactly what is safe to delete, what to leave alone, and what the commands actually do.
How to Reset an Azure Virtual Machine to Factory Settings Using a Managed Disk Azure does not have a single "factory reset" button. What it does have is something better: the OS Disk Swap — a method that swaps out the corrupted or misconfigured OS disk for a clean Windows Server managed disk without deleting the VM, its NICs, its IP addresses, or any attached data disks. Here is how it works, when to use it, and the exact steps to execute it safely. FA Francis Avorgbedor Azure Engineer July 16, 2026 15 min read Azure VMs · Windows Server · Real-World Fix 3 Methods to achieve a clean Windows Server installation on an existing Azure VM ~15min Typical OS Disk Swap duration — VM retains its NICs, IPs, and data disks throughout 0 Data disks affected by an OS Disk Swap — data disks remain attached and untouched 1 Snapshot of the original OS disk you must take before starting — no exceptions Introduction Why Azure Does Not Have a Simple Factory Reset — and What to Do Instead On a ph...

AKS CrashLoopBackOff, Pending Pods, and NotReady Nodes — The Real Fixes Engineers Use

Incident Playbook AKS Kubernetes kubectl 2026 AKS CrashLoopBackOff, Pending Pods, and NotReady Nodes — The Real Fixes Engineers Use Every AKS engineer eventually faces the same nightmare: CrashLoopBackOff at 2am, pods stuck Pending for no clear reason, or nodes flipping to NotReady mid-deployment. The difference between panic and control is knowing the exact diagnostic sequence — and the real fixes that work in production. This guide gives you both. 3 commands get pods, describe pod, and logs diagnose roughly 90% of AKS incidents before you touch anything else Exit 137 The code that means OOMKilled — the container hit its memory limit and was killed by the kernel (128 + SIGKILL 9) Events The bottom of kubectl describe is where the real cause lives — Pending, FailedScheduling, and image errors all surface there CoreDNS The single component behind most "intermittent" production failures — service discovery breaks quietly and looks like an app bug Table of Contents 01 The 3 Comm...
Can I Update My Old Computer to Windows 11 — and How Much Will It Cost? Your i7, 16GB RAM, 512GB SSD machine is powerful enough to run Windows 11 comfortably. The TPM 2.0 and Secure Boot wall is a security checkbox, not a performance ceiling. Here are two proven ways to get past it, what each one costs, and what you are trading away by doing so. $0 Cost of the Windows 11 licence if your existing Windows 10 is genuine — the upgrade remains free in 2026 2 Proven methods to bypass TPM 2.0 and Secure Boot — Rufus (easy) and Registry edit (manual) 25H2 Current Windows 11 version — all known bypass methods tested and confirmed working as of July 2026 Oct 2025 Windows 10 end of life — no more security updates. Staying on Windows 10 now carries real risk. First — Check Your BIOS Before Anything Else You Might Not Actually Need a Bypass Before running any bypass, open your BIOS and look at two settings. Many computers that fail the Windows 11 compatibility check have TPM 2.0 present in the hard...
2026 Edition 100 Tools Software Engineering DevOps AIOps Top 100 Best AI Tools for Azure  Engineers and DevOps Professionals in 2026 85% of developers now regularly use AI tools. Fully AI-generated code accounts for nearly 28% of all pull requests. The question is no longer whether to use AI tools — it is which ones, in which combination, for which part of the lifecycle. This guide cuts through the noise: 100 tools, 10 categories, honest pricing, real use cases, and a selection framework for building your stack without redundancy. 85% Percentage of developers who now regularly use AI tools, per JetBrains' 2025 State of Developer Ecosystem report — up from near zero three years ago 28% Share of all pull requests containing primarily AI-generated code in 2026 — the metric that signals AI coding assistants have moved from experiment to workflow $50B Cursor's reported valuation in April 2026 Series D talks — the number that signals investor confidence in the AI developer tools mark...

Azure Files vs Azure NetApp Files: Which One Should You Choose?

Azure Files vs Azure NetApp Files: Which One Should You Choose? Performance tiers, protocol support, dual-protocol capability, pricing models, SAP/Oracle/HPC suitability, data management features, and the decision framework that maps each workload type to the right service — with step-by-step setup procedures for both. FA Francis Avorgbedor Azure Engineer July 15, 2026 20 min read Azure Storage · Architecture 4 Azure Files tiers: Premium SSD, Standard Hot, Cool, Tx Optimized 3 ANF performance tiers: Standard, Premium, Ultra — all SSD-backed 4TiB ANF minimum provisioning — significant cost floor for small workloads Dual ANF serves the same data via SMB and NFS simultaneously — AF cannot Introduction Two Services, One Surface Area — Completely Different Purposes Microsoft offers two fully managed, enterprise-grade file storage services in Azure. They share a surface area — both serve file shares over standard protocols, both run on managed infrastructure, and both integrate with Microsof...
Troubleshooting Guide AKS Kubernetes Real Solutions kubectl Azure Kubernetes Service (AKS) Troubleshooting Guide: Real Solutions to Common Problems CrashLoopBackOff at 2am. Pods stuck Pending with no obvious cause. Nodes going NotReady mid-deployment. DNS resolution silently failing in production. Every AKS engineer encounters these — the difference between engineers who panic and engineers who stay calm is knowing the exact sequence of diagnostic commands to run. This guide gives you that sequence, the root cause analysis for each failure mode, and the fix. 3 commands 90% of AKS problems are diagnosed with the same three kubectl commands: describe pod, logs --previous, and get events — in that order, every time Exit 137 The exit code that tells you everything: container killed by SIGKILL — either the Linux OOM killer (memory limit exceeded) or kubelet after grace period expired 5 min The CrashLoopBackOff ceiling: Kubernetes applies exponential backoff (10s → 20s → 40s → 80s → 160s → 3...

How to Deploy an AI Chatbot on Azure Using Azure OpenAI and App Service

Step-by-Step Guide Azure OpenAI App Service Production Python How to Deploy an AI Chatbot on Azure Using Azure OpenAI and App Service From zero to a production-grade AI chatbot: provision Azure OpenAI, write a streaming Flask API backend, deploy it on Azure App Service with Managed Identity, wire in conversation history and content safety, and instrument it with Application Insights — all with complete code and Terraform IaC. No API keys in environment variables. No hardcoded secrets. No half-finished PoC patterns. 7 phases This guide covers the full deployment lifecycle: architecture design → resource provisioning → backend code → App Service deployment → streaming → security → monitoring Zero keys The chatbot authenticates to Azure OpenAI using Managed Identity and DefaultAzureCredential — no API keys stored in environment variables, Key Vault, or code SSE Server-Sent Events stream GPT tokens to the browser as they generate — the same token-by-token typing effect users expect from pr...