pony.ai is already on Cloudflare today. Every static asset on the site — hero videos, carousel images, the "新15秒视频" homepage MP4, the careers reel, every favicon, the investor PDF — currently loads from Alibaba Cloud OSS via xiaomazhixing.com. One platform serves the page, a second serves everything on the page.
The expand conversation isn't about replacing what's already working. It's about closing the inconsistency in the network waterfall — the one where every visitor to pony.ai/?lang=en hits Cloudflare for the page and then re-establishes a second TLS connection to Alibaba Cloud's US edge POPs for the assets. Two CDNs, two cache layers, two operational surfaces, two bills. R2 + Stream consolidate that onto the edge already serving the page.
Origin headers confirm Server: Tengine + x-oss-* + Via: ens-cache* = Alibaba Cloud OSS + ENS CDN.
xiaomazhixing.com for each asset is overhead the architecture doesn't need. The R2 + Stream consolidation collapses two cache layers into one, removes the second corporate-name DNS lookup in the US-EN network waterfall, and turns a multi-vendor asset estate into a single managed surface — without touching the HTML/CSS/JS stack that's already working.
Three Cloudflare products that map directly to the consolidation:
Cloudflare Stream — replaces the Alibaba-hosted MP4 layer. The homepage "官网新15秒视频" hero, the 57.5 MB careers MP4, and any future autonomous-vehicle test footage, demo reels, or investor relations video. Adaptive bitrate, signed URLs, analytics, single Stream embed per video. The 4-year-old static MP4 on the careers page becomes a properly streamed asset with mobile/desktop bandwidth optimization.
R2 + Cloudflare CDN — replaces the Alibaba Cloud OSS layer for everything that isn't video. The carousel images, banner JPEGs, icons, favicons, downloadable PDFs (the investor relations Pony.ai-*.pdf in particular). Zero egress, S3-compatible, same edge as the HTML.
Cloudflare Images (optional) — for the 轮播大图*.jpg carousel and banner assets that currently ship at one size for all devices. Per-device variant generation, format negotiation (WebP/AVIF), no separate image pipeline to maintain.
What's driving the static-asset estate staying on xiaomazhixing.com — is it the China-engineering-team workflow that originally set it up, a partner-storage agreement with Alibaba Cloud, a data-residency constraint, or simply that nobody has gotten around to migrating it? Different answer = different consolidation path. 20 minutes to map it out and see if there's a clean R2 + Stream pilot worth running on one page first.
A detailed audit is in progress — including the per-page asset inventory across pony.ai, ir.pony.ai, tech.pony.ai, press.pony.ai, story.pony.ai, and business.pony.ai; the Stream + R2 migration cost model vs. current Alibaba OSS + ENS spend; the careers-page pilot path; and the IR/post-IPO recruiting-page optics angle for the NASDAQ:PONY public-facing surfaces. Tell me which slice would be most useful first.
Existing-customer note: this isn't a swap-Cloudflare-for-something conversation. pony.ai HTML is already on Cloudflare today. This is a consolidation of what's already partially on Cloudflare with what isn't yet — closing the inconsistency between the page layer and the asset layer.