Pre-public · CCIX merger announced · the architecture for the next 1000× matters

7M+ autonomy miles. L4. 6 OEM partners.
One control plane built to scale into factory-built fleets.

SuperDrive™ is the virtual driver inside factory-built autonomous trucks from TRATON (Scania, MAN, International), Hyundai, IVECO, Bosch, Amazon, DSV, Ryder, and NVIDIA. HyperFoundry™ is the Physical AI development platform underneath. The OTA control plane, the global telemetry firehose, the simulation data lake, and the per-OEM tenancy are the parts that have to scale by 1000× before driverless launch. Cloudflare's developer platform is built for exactly that shape.

NS: matt · may.ns.cloudflare.com on adjacent domains · Anthropic · Zoom · Wiz · Atlassian · Slack verified on plus.ai apex TXT · site fronted by Vercel

June 2025: PlusAI announced its plan to go public via merger with Churchill Capital Corp IX (NASDAQ: CCIX). April 2026: business update webcast. March 2026: SuperDrive™ 6.0 launched, NVIDIA Alpamayo foundation model integration announced, and the first commercial fleet trial with International began.
— Aggregated from plus.ai/news-and-insights, June 2026. The next 18 months are the most architecturally consequential in PlusAI's history.
7M+
Autonomy miles driven
L4
SAE autonomy level — driverless
6
OEM partners shipping with SuperDrive™
3
Continents — US, EU, Asia operations
Building the autonomous future with
TRATON GROUP· Scania· MAN· International· Hyundai· IVECO· Bosch· Amazon· DSV· Ryder· NVIDIA

PlusAI builds the virtual driver. Cloudflare runs the everything-around-it.

The hard parts of factory-built autonomous trucking aren't only the neural networks in the cabin. The OTA control plane, the global telemetry firehose, the per-OEM data isolation, the simulation data movement, the attorney-grade safety case audit trail — each one is a planet-scale infrastructure problem. None of them should compete for engineering attention with SuperDrive™ itself.

PlusAI builds

SuperDrive™, HyperFoundry™, and the Driving Intelligence stack

The AV2.0 architecture — large AI models replacing 100M lines of vehicle code. Auto-labeling, model distillation, in-vehicle neural network execution. The NVIDIA Alpamayo foundation model integration. The safety case framework. The factory-built integrations with TRATON, Hyundai, and IVECO.

  • DNN-based virtual driver replacing 100M+ LoC
  • Generative AI + open foundation models for driving intelligence
  • Auto-labeling and model distillation for efficient training
  • Factory-line integrations with 6 OEM partners across 3 continents
×

Cloudflare runs

The OTA control plane, the telemetry firehose, the per-OEM tenancy

The edge between trucks-in-the-world and PlusAI engineering: OTA delivery from R2, model rollouts via Workers, telemetry ingest at 330+ POPs, per-OEM data isolation via Workers for Platforms, Zero Trust for HyperFoundry developer access, and AI Gateway in front of the foundation model layer.

  • Workers + R2 for global OTA model + map delivery
  • Workers AI + AI Gateway in front of NVIDIA Alpamayo and Anthropic
  • Workers for Platforms — per-OEM tenancy by construction
  • Zero Trust for HyperFoundry developer + partner access

Two solutions, two developer-platform shapes.

SuperDrive™ runs on the truck. HyperFoundry™ runs off the truck. The control plane between them — OTA delivery, telemetry ingest, simulation data movement, partner access — is the natural home for Cloudflare's developer primitives.

SOLUTION 01

SuperDrive™

L4 AUTONOMOUS DRIVING · FACTORY-BUILT

PlusAI's virtual driver, built into trucks at the OEM factory line. The in-vehicle stack runs the DNN. Cloudflare runs the bridge between every truck and PlusAI engineering — OTA model updates, configuration delivery, telemetry ingest, incident triage routing, and partner data sharing — from the closest of 330+ POPs to whichever highway the truck happens to be on.

The wedge: Trucks need OTA model and map delivery from a runtime that's geographically close, byte-cheap, and resumable on intermittent connectivity. R2 (zero egress) + Workers + Smart Placement is exactly that runtime — no per-region S3 bucket sprawl, no CloudFront invalidation pain, no Lambda@Edge cold starts.
Workers R2 Smart Placement OTA delivery
SOLUTION 02

HyperFoundry™

PHYSICAL AI DEVELOPMENT PLATFORM

The off-truck side: production-validated data, models, and simulation distilled from the L4 stack. This is where PlusAI engineers (and increasingly OEM partner engineers) train, evaluate, and deploy. The interesting infra question isn't the GPU cluster — it's who can touch what, how datasets move between partners, and how every experiment maps back to a specific deployable model.

The wedge: Workers for Platforms gives every OEM partner their own HyperFoundry tenant — isolated keys, isolated egress, isolated audit trail. Zero Trust gates the human access. R2 holds the dataset corpus with zero egress when partners pull. Same control plane, no shared-state risk.
Workers for Platforms Zero Trust R2 Per-OEM tenancy

A truck is a streaming sensor. The pipeline is the product.

Every SuperDrive™-equipped truck is generating high-volume telemetry: camera frames, lidar returns, radar, GPS, CAN bus, driving decisions, and edge-case captures. That feed has to land somewhere it can be triaged in seconds, ingested into HyperFoundry™ for re-training, and replayed in simulation. Cloudflare runs that pipeline at the edge instead of the hub.

Truck telemetry → HyperFoundry™, sketched on Cloudflare primitives

From "the truck just made an interesting decision in Munich" to "the simulation team has the replay in Fremont" — the whole flow can move closer to the truck.
SOURCE
SuperDrive™-equipped truck
cameras, lidar, radar, CAN, decisions
INGEST EDGE
Workers + Queues
closest POP to truck, <30ms anywhere
TRIAGE + STORE
Workers AI + R2 + Vectorize
classify, embed, store zero-egress
FANOUT
Workflows + Durable Objects
re-train, sim replay, safety case
What this changes: Today, every byte of telemetry has to traverse a regional ingress, get classified by a centralized service, then redistributed for sim and training. On Cloudflare, classification happens at the POP closest to the truck. Interesting events bubble up in seconds. Boring events stay cheap. The HyperFoundry data lake gets only signal, not noise — and your engineers get to chase ground-truth incidents while they're still warm, not after a 4-hour pipeline.

The AV2.0 stack maps cleanly to six developer primitives.

Each of PlusAI's published technology pillars has a natural Cloudflare primitive that runs the off-truck half of it. None of this is speculative — each row maps to a sentence on the plus.ai/technology page.

PRIMITIVE 01 · AV2.0

Workers AI + AI Gateway for model serving

PlusAI's AV2.0 thesis replaces 100M+ lines of vehicle code with deep neural network models. AI Gateway sits in front of the foundation model layer (NVIDIA Alpamayo, Anthropic verified on your apex) with caching, attribution, and budget control. Workers AI runs open-weight models at the edge for non-safety-critical inference.

AI Gateway Workers AI Alpamayo
PRIMITIVE 02 · DRIVING INTELLIGENCE

Vectorize for scenario retrieval

"Generative AI, open foundation models, and proprietary data" to build general driving intelligence. Vectorize indexes every driving scenario embedding — so a re-training query like "find me every left-merge in fog on a 6% grade" returns in milliseconds, not hours.

Vectorize R2 RAG
PRIMITIVE 03 · EFFICIENT TRAINING

R2 + Workflows for the data lake

Auto-labeling and model distillation generate huge volumes of training-ready data. R2 holds the corpus with zero egress; Workflows orchestrate the multi-step distillation pipelines durably and observably — without standing up Temporal or Airflow.

R2 Workflows Queues
PRIMITIVE 04 · FAST MODELS

Workers for the off-truck inference

"Super efficient in-vehicle neural network execution allows us to deploy bigger, smarter models." That's the in-truck side. The off-truck side — fleet routing, scenario triage, partner-facing dashboards — runs on Workers at single-digit-ms latency from any of 330+ POPs.

Workers Durable Objects Smart Placement
PRIMITIVE 05 · SAFETY CASE

R2 + Workers for audit-grade artifacts

The Safety Case Framework requires immutable, replayable, attorney-grade evidence trails. R2 with object versioning + Workers for tamper-evident hash chaining gives you a compliance surface regulators, OEM legal, and insurance underwriters can all sign off on.

R2 versioning Workers Audit trail
PRIMITIVE 06 · FLEET ACCESS

Zero Trust for HyperFoundry developers + partners

You have wiz, slack, atlassian, and zoom verified on the apex. Adding Cloudflare Zero Trust closes the loop — identity-aware access to HyperFoundry, GitOps repos, and partner data rooms without VPN sprawl across US + EU + Asia offices.

Access Tunnel No VPN

The economics of millions of OTA deliveries and a global telemetry firehose.

Two infrastructure cost lines dominate factory-built autonomous trucking at scale: OTA model + map delivery, and telemetry ingest + storage. Both are quietly some of the most edge-amenable workloads in software. R2's zero egress and Workers' POP proximity move the dial in real numbers.

A back-of-the-envelope, not a quote
Modeled across OTA model rollouts + telemetry ingest + foundation-model inference at fleet scale
OTA DELIVERY EGRESS SAVINGS
40–60%
R2's zero egress vs. S3/CloudFront pricing across model and map rollouts that may run hundreds of GBs per truck per quarter as fleet sizes grow.
TELEMETRY TRIAGE AT THE EDGE
70–90%
Workers AI classifying telemetry at the POP closest to the truck — only interesting events get backhauled to HyperFoundry, not raw firehose.
FOUNDATION MODEL SPEND VISIBILITY
100%
AI Gateway gives per-OEM, per-scenario, per-experiment attribution across Alpamayo + Anthropic — today that lives across cost spreadsheets.
The real win isn't the savings, it's the auditability. When TRATON, Hyundai, and IVECO each have their own OTA delivery line item, their own telemetry ingest cost, and their own foundation-model attribution — you can defensibly price OEM agreements at the right tier. Equally important: when CCIX investors and regulators ask "show me the per-truck unit economics of autonomy at scale," the answer lives in one dashboard, not in a quarter-end reconciliation.

Six OEMs, six tenants. Workers for Platforms is the boundary.

TRATON's Scania, MAN, and International divisions, Hyundai, IVECO, and Bosch all build trucks with SuperDrive™ inside — but they each have their own confidentiality requirements, their own data residency expectations (EU vs US vs Asia), their own roadmap, and increasingly their own engineers needing access to HyperFoundry. That's not a row-level-security problem. It's a tenancy problem.

Per-OEM tenancy, sketched

Each OEM partner gets its own Worker namespace inside Workers for Platforms. Same edge, same observability, isolated keys, isolated egress, isolated audit trail, region-bound data residency.
🚚
TRATON / Scania
🚚
TRATON / MAN
🚚
TRATON / International
🚚
Hyundai
🚚
IVECO
🚚
Bosch (tier-1)
Shared control plane — Workers for Platforms + AI Gateway + Vectorize + R2
one runtime · one observability surface · data residency enforced by region binding, not by checkbox

Current stack, with Cloudflare overlaid.

Every row below is sourced from public DNS records, the plus.ai apex TXT, and HTTP response headers. The Cloudflare column is additive — nothing requires ripping out Vercel or the existing AWS estate.

What's running today, and where Cloudflare slots in

Pure overlay model. Vercel keeps doing what it does well; AWS keeps what it does well; Cloudflare picks up what it does better at fleet scale.
LAYER
PLUSAI RUNS TODAY
CLOUDFLARE FIT
MARKETING SITE
Vercel (sfo1, x-vercel-id headers)
No change — Vercel fronts cleanly behind a Cloudflare zone
DNS
101domain (ns1-5.101domain.com)
+ Cloudflare DNS — unified analytics, WAF, edge routing
FOUNDATION MODELS
Anthropic (verified on apex), NVIDIA Alpamayo (announced March 2026)
+ AI Gateway in front: cache, attribution, rate-limit, budget cap
CLOUD SECURITY POSTURE
Wiz (verified on apex)
+ Zero Trust closes the access loop alongside Wiz's posture management
DEV TOOLS
Atlassian + Slack + Zoom (all verified on apex)
+ Zero Trust SSO to Atlassian + Slack + Zoom from one identity layer
OTA DELIVERY
Likely S3 + CloudFront (industry standard for AV OTA)
+ R2 + Workers + Smart Placement — zero egress, POP-resident
TELEMETRY INGEST
Likely Kafka / Kinesis on regional AWS
+ Workers + Queues for edge-resident triage before backhaul
SIMULATION DATA LAKE
Likely S3-based parquet/lake on AWS
+ R2 (zero egress) as the read-heavy tier for cross-partner sharing
PER-OEM ISOLATION
Multi-tenant HyperFoundry with config-level isolation
+ Workers for Platforms — per-OEM namespace by construction
EMPLOYEE + PARTNER ACCESS
VPN across Santa Clara, Fremont, Munich, EU, Asia offices
+ Cloudflare Access — identity-aware proxy, no VPN sprawl
EMAIL
Google Workspace
+ Email Security as defense-in-depth (especially pre-IPO surface)
SAFETY CASE ARTIFACTS
Internal storage for audit-grade evidence
+ R2 with versioning + Workers for tamper-evident hash chaining

Why this is the right quarter to start the conversation

The CCIX merger is a forcing function. Once PlusAI is public, every infrastructure decision has shareholder gravity. The next 18 months — from now through SuperDrive™ 6.x and the first commercial fleet rollouts — are when the architecture that scales by 1000× gets chosen. Picking the off-truck control plane now is much cheaper than re-platforming it under quarterly earnings scrutiny.

The OEM pipeline keeps accelerating. The March 2026 International fleet trial, the NVIDIA Alpamayo integration, SuperDrive™ 6.0 launch — each new OEM and each new foundation model is another tenant on the control plane. Workers for Platforms turns "add a new OEM" from a multi-quarter integration into a namespace creation.

The vendor relationships are already in place. Anthropic is verified on your apex. Wiz, Atlassian, Slack, Zoom are all verified. Adding Cloudflare to that list isn't a new vendor introduction — it's the runtime that makes the rest of the modern stack run from the edge. No procurement event to start from zero.

Worth a 30-minute conversation with the platform team?

The interesting conversation is which of these primitives is closest to your current sprint: AI Gateway in front of Alpamayo + Anthropic, R2 + Smart Placement for OTA, Workers for Platforms behind HyperFoundry for OEM tenancy, or Zero Trust across the US + EU + Asia offices. I'd rather hear what's actually on your roadmap than guess.

Matt Holscher Calendar  → Reply by email