ELSA Speak is the #1 AI English speaking app — 92M+ downloads, 90M+ learners, 4.9 stars, in 193+ countries, with a Bilingual AI Tutor, 5 named role-play coaches, and an ELSA API for developers. elsaspeak.com is already on Cloudflare DNS. The expansion footprint is the developer platform underneath: AI Gateway for the bilingual tutor + role-play inference, R2 for the lesson + audio corpus, Workers for Platforms for ELSA Business / Schools / API tenancy, and Workers AI for the speech-analyzer pipeline.
elsaspeak.com on Cloudflare via graham + nola.ns.cloudflare.comcf-cache-status: HIT on every homepage response — you're already serving Astro static through CFYou're already on Cloudflare for DNS + edge caching of a JAMstack marketing surface — that's the front door for 92M+ downloads. The next infrastructure layer is the part that scales with the actual product: the bilingual AI tutor's inference, the role-play scenario fan-out, the speech-analyzer pipeline, the per-organization tenancy boundary for ELSA Business + Schools + API, and the audio + lesson corpus that has to serve a learner in Vietnam at the same latency as a learner in Brazil.
Each maps to something you ship today (the bilingual tutor, the role-play library, the speech analyzer, the ELSA API, the multi-tier B2B offering) or something the published roadmap implies. Status tags show what's already live in your Cloudflare footprint.
graham + nola.ns.cloudflare.com serve DNS. The Astro static surface is already cached at the edge with cf-cache-status: HIT on every response. Procurement is in place, the SOC mapping exists — this isn't a vendor selection conversation.
Every role-play conversation with Kevin or Camila is an LLM call. Every bilingual tutor session that bridges a learner's native language to English is an LLM call. Multiplied across 90M+ learners, that's serious inference volume. AI Gateway gives one logged, cached, attributed hop — with semantic cache catching enormous repetition across learners.
The Speech Analyzer, How to Pronounce, and Quick Evaluation features are real-time audio analysis. Workers AI runs ASR + scoring models at the edge POP closest to the learner — not from a centralized GPU cluster. Latency from speech to feedback collapses by hundreds of milliseconds.
Individual + ELSA Business + ELSA Schools + ELSA API customers all need different feature gates, different curricula, different reporting dashboards, different data-residency rules. Workers for Platforms gives each tier — and each enterprise customer inside — its own isolated Worker namespace on the same edge.
Lessons from HarperCollins, Pearson, Oxford. Audio prompts in dozens of native languages. Industry-specific content for ELSA Business. Curriculum-aligned lessons for ELSA Schools. R2 holds it all zero-egress; Vectorize indexes lessons for "find me a lesson like this one for a Vietnamese learner targeting Hamburger University."
The ELSA API is already a public product. Workers is the natural runtime for a developer-facing API at the scale you operate — sub-millisecond cold start, 330+ POPs for partner apps in any region, native rate-limiting per API key, and native auth at the edge.
92M+ downloads across iOS + Android. Every update, every new lesson pack, every per-region audio variant has to reach learners worldwide. R2's zero-egress storage + Workers + Smart Placement serves from the closest POP to each learner — without per-region S3 sprawl or CloudFront egress bills.
A role-play with Kevin or Lily has state: the conversation buffer, the in-flight grading, the learner's accent profile, the per-turn feedback. Durable Objects give you a single-writer state holder per active session at the edge with native WebSocket support — no separate Redis cluster.
A free-tier product with 92M+ downloads is a magnet for credential-stuffing, free-trial abuse, scraped lessons, and API-key farming. Bot Management at the edge stops the abuse before it touches the Auth backend or the ELSA API. Turnstile drops in on signup, login, and API key issuance.
Each ELSA avatar runs a distinct AI workload — same model family, different prompts, different success metrics. AI Gateway gives you per-avatar attribution by default: which scenarios drive the most engagement, which cost the most per turn, which need the next round of investment.
"Learner opens the app, says one sentence" → ASR pass → pronunciation scoring → role-play turn through Claude → instant feedback → progress tracker update. Each step is a small inference call. Across 90M+ learners doing 20+ minutes a day, those calls cluster brutally — same lessons, same common phrases, same accent patterns.
ELSA's scale is a freemium funnel where the inference bill scales with engagement, not with revenue. AI Gateway turns Anthropic + open-model spend into a per-tier, per-coach, per-org cost line — the data needed to defensibly price Business and Schools tiers at the right margin and to scope the next year's API monetization.
Individuals want a personal coach. ELSA Business wants role-specific coaching + ROI dashboards for Fortune 1000s. ELSA Schools wants curriculum-aligned content + parent reports. ELSA API wants per-app key issuance + per-app billing. Each tier — and each enterprise customer inside — needs isolation enforced by infrastructure, not config.
Every row is sourced from public DNS records, the elsaspeak.com apex TXT, HTTP response headers, and the visible CMS asset CDN. The mint row is already running on Cloudflare today. The orange column is the expansion footprint.
ELSA API is a developer-platform product. The moment you expose an API to outside developers, the platform questions stop being internal. Rate limiting, per-key attribution, regional latency, abuse defense, BYO-key support for enterprise customers — all become product surface. Workers is the most natural runtime in the market for that shape, and AI Gateway is the cheapest hour you can spend on cost observability before API usage scales.
You're already on Cloudflare. DNS via graham + nola.ns. Edge caching of the Astro static surface on every response. There's no procurement event to start, no security review to begin from zero, no MSA to negotiate. Expanding from DNS + edge cache to AI Gateway + R2 + Workers for Platforms is the most natural roadmap conversation in the lineup.
The B2B pipeline keeps accelerating. Nestlé, McDonald's Hamburger University, TELUS Digital, NTT Data, Pertamina, PLN, Permata Bank, YKK AP, NashTech — 1,300+ organizations served globally. Every new enterprise contract is another tenant on the platform. Workers for Platforms turns "add a new enterprise" from a custom integration into a namespace creation. That math compounds.
The interesting conversation is which of these primitives is closest to your current sprint: AI Gateway in front of the bilingual tutor + role-play layer, Workers as the ELSA API runtime, Workers for Platforms behind Business + Schools, or Workers AI for the speech analyzer at edge POPs. I'd rather hear what's actually on your roadmap than guess.