BlueStacks ships the world's most-installed Android emulator, plus cloud gaming, plus a brand-new AI worker product — across 17 locales and 2M+ titles, with publishers from Activision and Ubisoft to Blizzard, KRAFTON, and NEXON. The bluestacks.ai subdomain already runs on Cloudflare. The expansion footprint is the developer platform underneath every product surface: AI Gateway in front of BlueAI, R2 for the install corpus, Workers for Platforms for per-publisher tenancy, and the same edge already serving your AI launch.
bluestacks.ai is on Cloudflare DNS — alina / cody.ns.cloudflare.comwww.bluestacks.com + now.gg in stagesYou ship a binary that runs on millions of PCs and Macs, a cloud-game runtime, a 17-locale marketing surface, an AI worker that just launched, and a 2M+ title catalog. Each one has a different shape but all of them share an infrastructure problem: how do you serve, observe, and govern from the closest of 330+ POPs to whichever player just opened the app?
Each maps to something you ship today (BlueStacks 5/10, Air for Mac, BlueAI, Cloud Gaming, the Store, PlayPal, nowBux) or something on the public roadmap. Status tags show what's already live in your Cloudflare footprint.
The newest, most strategic product surface in the lineup — the AI worker — is already on Cloudflare DNS via alina & cody nameservers. This is the launchpad for everything else: it proves the procurement is in place, the SOC mapping exists, and the engineering relationship is established.
"Your AI Worker for Getting Things Done" implies high-volume inference across millions of users searching, comparing, replying, and looking up guides. AI Gateway gives you one logged, cached, rate-limited, budget-capped hop in front of whatever model layer BlueAI uses — with per-user and per-game attribution by default.
Every BlueStacks install pulls a ~700MB–1GB binary, then APKs and updates over the lifetime of the install. That's a heavy, globally-distributed bytecount problem — the textbook case for R2's zero-egress storage + Workers' Smart Placement to serve from the closest POP to each player.
2M+ titles is too big to browse linearly. Players land on RAID Shadow Legends and want adjacent RPGs. Players land on Lords Mobile and want adjacent strategy. Vectorize indexes every game's metadata + cover art embeddings, so "similar games" returns in single-digit milliseconds.
Activision, Blizzard, Ubisoft, KRAFTON, NEXON, Garena, NetEase, Plarium — each publisher has its own analytics, its own promo windows, its own anti-cheat constraints, its own data-handling expectations. Workers for Platforms gives each publisher its own Worker namespace with isolated keys, egress, and audit trails.
Free downloads + accounts with cashback economics (nowBux) are catnip for scrapers, account farmers, and grey-market resellers. Bot Management at the edge stops the abuse before it ever touches the Store backend — and Turnstile drops in cleanly on Store, signup, and redemption flows.
EN, ZH-TW, VI, TR, TH, RU, PT-BR, PL, MS, KO, JA, IT, ID, FR, ES, DE, AR — each one needs its own edge-cached rendering, its own redirect rules, and its own A/B routing. Workers make locale-specific edge logic a deployment configuration, not a microservice.
"Hybrid cloud or local PC. Play as you like." Cloud gaming sessions are stateful, per-user, region-bound, and latency-sensitive. Durable Objects give you a single-writer state holder at the edge for each session; Queues handle the input/output async without standing up Redis.
Engineering, support, and publisher-partner portals all need identity-aware access without VPN sprawl across global offices. Zero Trust Access closes the loop — one identity layer in front of Atlassian, GitHub, the publisher dashboards, and the BlueAI experiment consoles.
"You search for something, switch apps, check updates, compare options, look up a game guide, draft a reply, claim..." — every one of those is a small inference call. Across millions of users, those calls cluster heavily: same game guides, same compare flows, same reply templates. The cache hit rate is structural.
Two cost lines dominate launching an AI worker product: inference spend (every user query is a call) and CDN egress (chat UIs are surprisingly chatty about static assets + streamed tokens). Both are quietly some of the most edge-amenable workloads in software, and AI Gateway turns the first one into an observable, attributable dashboard instead of a monthly Anthropic surprise.
English, 繁體中文, Tiếng Việt, Türkçe, ไทย, Русский, Português, polski, Melayu, 한국어, 日本語, Italiano, Indonesia, Français, Español, Deutsch, العربية — each locale has its own promo cadence, its own gateway model preferences (Korean players want Korean LLMs), its own data-residency requirements, and increasingly different AI budgets.
Every row below is sourced from public DNS records and HTTP response headers on bluestacks.com, bluestacks.ai, and now.gg. The pink rows are already running on Cloudflare today. The orange column is the expansion footprint, additive to the AWS estate.
BlueAI launched today. The blog post is hours old. The architectural decisions being made this quarter — what governs inference, how attribution works across publishers, where the AI worker scales next — will define the BlueAI cost curve for 2027. AI Gateway is the cheapest hour you can spend in front of that curve.
The vendor relationship is in place. bluestacks.ai already runs on Cloudflare DNS. There's no procurement event to start from zero, no security review to begin, no MSA to negotiate. Expanding Cloudflare from the AI subdomain to the AI Gateway behind it is the most natural roadmap conversation in the lineup.
The publisher pipeline keeps accelerating. Every new game from Activision, Blizzard, Ubisoft, NEXON, KRAFTON, or NetEase is another tenant on the platform. Workers for Platforms turns "add a new publisher" from a backend integration project into a namespace creation. That math compounds.
The interesting conversation is which of these primitives is closest to your current sprint: AI Gateway behind BlueAI, R2 for the install CDN, Workers for Platforms behind the publisher catalog, or Bot Management across the Store + nowBux flows. I'd rather hear what's actually on your roadmap than guess.