The AWS blog from Oct 29, 2025 lays out exactly how Sibros + Panasonic + AWS reduce connected-vehicle integration friction. AWS hosts the vSkipGen GPU emulator on EC2 G5G and ships Deep Connected Platform via AWS Marketplace — both of which Cloudflare doesn't try to replace. What Cloudflare adds is the layer in front: OTA binary delivery at zero egress, vehicle telemetry triage at 330+ POPs, AI Gateway in front of Deep Insights, and Workers for Platforms for per-OEM tenancy — on the same edge that already serves sibros.tech today.
sibros.tech on Cloudflare via carrera + merlin.ns.cloudflare.comwww.sibros.tech served via Cloudflare anycast (104.26.x / 172.67.x) with server: cloudflareThe AWS blog post is admirably clear about who does what. Sibros writes the connected-vehicle software. Panasonic ships the digital cockpit. AWS provides the GPU instance and the Marketplace. The thing missing from the diagram — not yet a problem at demo scale, very much a problem at fleet scale — is the global edge layer that handles OTA delivery and telemetry triage. That's where Cloudflare slots in.
Deep Logger for CAN-bus capture + analytics, Deep Updater for OTA, Deep Commander for remote diagnostics, Deep Insights for AI-powered root-cause analysis. Embedded firmware that integrates with any automotive stack.
EC2 G5G with NVIDIA GPUs for vSkipGen virtual cockpit, AWS Marketplace as the OEM distribution channel, the Automotive Innovation Lab in Santa Clara, and generic cloud compute for the Sibros DCP SaaS backend.
R2 for OTA binary distribution at zero egress. Workers + Queues for telemetry triage at the POP closest to the vehicle. AI Gateway in front of Deep Insights' LLM calls. Workers for Platforms for per-OEM tenancy. All on the same edge already serving sibros.tech.
Each maps to a specific component in the AWS architecture diagram from the blog. Status tags show what's already on Cloudflare, what's an obvious next addition, and what should stay on AWS as the GPU-bound parts of the system.
Authoritative DNS via carrera + merlin.ns.cloudflare.com. The web edge serves with server: cloudflare. Procurement is in place, SOC mapping exists — expansion is a configuration change, not a vendor selection.
Every connected vehicle pulls firmware updates — sometimes hundreds of MB per ECU per update, multiplied across millions of vehicles. R2's zero egress fees vs. S3 + CloudFront is the single biggest cost line in the entire Deep Updater workflow at fleet scale.
Deep Logger captures CAN signals from millions of vehicles. Workers at 330+ POPs catch the inbound telemetry at the POP closest to the vehicle — not centralized us-west-2 backhaul. Queues handle fan-out into ML pipelines without standing up SQS regionally.
Deep Insights is described as "AI-Powered analytics, including root cause diagnosis." Anthropic + OpenAI are both verified on your apex TXT records. AI Gateway sits in front: semantic cache for repeated root-cause queries, per-OEM attribution, budget caps, BYO keys for enterprise OEM customers.
Sibros sells to many automakers via Panasonic, AWS Marketplace, and direct. Each OEM customer has its own SLA, its own data-residency requirements, its own audit cadence, its own brand surface. Workers for Platforms gives each OEM its own isolated Worker namespace inside one control plane.
During an OTA push, each vehicle is a stateful session: which ECUs are updating, where the update is paused, whether cellular dropped mid-flight. Durable Objects give you a single-writer state holder per VIN at the edge with native WebSocket support — no per-region Redis cluster.
Deep Insights does "root cause diagnosis." That's a scenario-similarity problem: "find every CAN-bus event in the last 30 days that looks like this thermal anomaly." Vectorize indexes telemetry embeddings; the answer returns in single-digit milliseconds, not minutes.
Engineers, OEM partners, and validators all need access to per-OEM dashboards and telemetry pipelines. Cloudflare Access + Tunnel give identity-aware, audit-logged access without VPN sprawl — critical for the kind of SOC 2 / ISO 27001 / TISAX posture automotive customers expect.
The vSkipGen Android Automotive emulator legitimately needs an NVIDIA GPU instance (EC2 G5G), which Cloudflare doesn't provide. The AWS Marketplace AMI distribution is also AWS-native and stays there. This isn't a replacement pitch — the GPU-bound parts of the stack belong on AWS.
The diagram in the AWS blog shows vSkipGen running on AWS, the Sibros DCP SaaS running on AWS, and the in-vehicle Deep Logger talking to the cloud. The blog doesn't show a global edge in front — not because it isn't needed, but because at single-vehicle demo scale you can ignore it. At fleet scale, you can't.
The AWS-only architecture is the right starting point for demos and pilot OEMs. The architecture for 10M+ vehicles needs an edge layer that doesn't charge per-byte for OTA delivery, doesn't centralize telemetry through one region, and gives per-OEM cost attribution as a default not a future-roadmap feature.
Sibros sells to automakers directly, to tier-1 suppliers like Panasonic, and to OEM joint ventures. Each customer has its own SLA, its own audit cadence, its own data residency requirements (EU GDPR, China, etc.), its own brand surface. That's not a feature flag — it's an isolation boundary.
Every row is sourced from public DNS records, the sibros.tech apex TXT, HTTP response headers, and the AWS blog post architecture diagram. Lime rows are already on Cloudflare. Orange-tinted rows belong on AWS and should stay there. The orange overlay column is the additive Cloudflare layer.
sibros.tech ships Vite in production. We can see it on the wire today: five /assets/[name]-[8-char-hash].js chunks (react-vendor, i18n-vendor, supabase-vendor, vimeo-vendor, plus the main bundle), modulepreload hints for each, and the __vite__mapDeps runtime symbol baked into the main chunk. That is the canonical Vite output signature.
On June 4, 2026, Cloudflare acquired VoidZero. The full team behind Vite, Vitest, Rolldown, Oxc, and Vite+ — Evan You and the maintainers — are now Cloudflare engineers. Vite stays open source and vendor-agnostic. The change is that the people building the toolchain Sibros engineers use every day now sit on the same team that operates the front door of sibros.tech.
What this opens up for Sibros. Direct line into the Vite roadmap on questions that matter to the Deep Connected Platform team: Rolldown-powered production builds (no Rollup/esbuild split), Oxc for type-checking and linting at native speed, and tighter integration between Vite's dev-server semantics and the same Workers runtime that already fronts sibros.tech. The combination of VoidZero engineers + Workers + R2 + AI Gateway on one platform is not available anywhere else.
The conversation-starter framing. “The bundler running sibros.tech right now is built by people on Cloudflare's team” is the opener. The substance underneath it is what is interesting: a single platform spanning the build tool, the edge runtime, the OTA delivery layer, and the AI inference path. That is the version of the developer-platform story that did not exist 60 days ago.
The AWS blog made the architecture public. Sibros + Panasonic + AWS just published a joint go-to-market piece on Oct 29, 2025 — with named co-authors from all three companies. The diagram is now public, the marketplace listings are live, and the demo runs at the AWS Automotive Innovation Lab in Santa Clara. The architecture conversation is open, which is the right moment to talk about what else fits in the picture.
You're already on Cloudflare. sibros.tech DNS is on us. The web edge serves through us. Anthropic, OpenAI, Cursor, and Lovable are all verified on the apex — you're an AI-tooling-heavy team. Expanding from DNS + web edge to R2 + Workers for Platforms + AI Gateway is the most natural roadmap conversation in the lineup.
VoidZero is now Cloudflare. The Vite/Vitest/Rolldown/Oxc team joined on June 4. Your production build is shipped by their toolchain today. Direct roadmap access — on the same platform that already fronts your front door — is a delta that did not exist last quarter.
The economics flip at fleet scale. At 100 demo vehicles, the AWS-only architecture is the cheapest, simplest path. At 1M+ vehicles, OTA egress is the single biggest cost line in the bill. R2's zero-egress profile is the most valuable thing Cloudflare can offer the Deep Updater roadmap — and the cheapest hour you can spend in front of that curve, before the math starts to matter at OEM-contract-pricing time.
The interesting conversation is which of these primitives is closest to your current sprint: R2 for OTA at zero egress, AI Gateway in front of Deep Insights, Workers for Platforms for per-OEM tenancy, or Workers + Queues for global telemetry triage. I'd rather hear what's actually on your roadmap than guess.