Willow ships voice dictation to 50,000+ users across Mac, Windows, and iPhone — with SOC 2, HIPAA, zero data retention, and Scribe just shipping as the AI writing assistant. willowvoice.com is already on Cloudflare DNS. api.willowvoice.com is already running on Cloudflare anycast. The expansion footprint is the developer platform underneath: AI Gateway in front of the inference layer, R2 for the model + binary distribution, Workers for the desktop sync layer, and Workers for Platforms for the Teams plan that's coming.
willowvoice.com on Cloudflare DNS via christian / dorthy.ns.cloudflare.comapi.willowvoice.com on Cloudflare anycast (104.26.x / 172.67.x) — already a CF Worker or proxyYou've shipped the hard part: a dictation engine fast enough and accurate enough that 50K+ users prefer it to the keyboard. The next infrastructure surface is the part players don't see — the inference plane behind Scribe, the binary + model distribution to every Mac and Windows desktop, the Teams tenancy boundary, the SOC 2 audit surface for the next enterprise security review. Cloudflare's developer platform is built for exactly that shape, and you're already on it for DNS + the API plane.
Each maps to something you ship today (the API plane, the desktop clients, Scribe, the audio pipeline, the HIPAA-grade compliance surface) or something on the roadmap (Teams plan, organization-level controls, enterprise security reviews). Status tags show what's already live in your Cloudflare footprint.
Authoritative DNS via christian / dorthy.ns.cloudflare.com. The foundation everything else snaps onto. Procurement is in place, SOC 2 mapping exists, support relationship is established — expansion is a configuration change, not a vendor selection.
api.willowvoice.com resolves to Cloudflare anycast (104.26.x / 172.67.x) — meaning it's either a Worker, a CF proxy, or running through a CF Tunnel. Either way, the desktop and iOS clients talk to Cloudflare on every request already.
Scribe = "polished message from a few quick words" = LLM call per invocation, multiplied across 50K+ users. AI Gateway sits in front: semantic cache for repeated patterns ("draft a Slack follow-up to X"), per-user attribution, budget caps before runaway spend, BYO keys for enterprise customers when the Teams plan ships.
Every desktop install pulls a binary. Every release updates it. With 50K+ users across three platforms and growing fast, that's a meaningful CDN bill at any reasonable scale. R2's zero egress + Workers' Smart Placement serves from the closest POP to each user without per-region S3 sprawl.
The Teams page exists today (in the footer nav). When the Teams plan ships, every enterprise customer wants their own custom dictionary, their own SSO, their own data residency, their own audit log, their own Scribe budget. Workers for Platforms makes those boundaries infrastructure, not config flags.
"Willow spells unique terms and names correctly using contextual cues." That's a retrieval problem. Vectorize indexes per-user (and per-org, when Teams ships) custom dictionaries + recent context so the right spelling comes back in single-digit milliseconds.
Live dictation sessions have state: the audio buffer, the running transcript, the user's style profile, the in-flight edit operations. Durable Objects give you a single-writer state holder per active session, at the edge, with native WebSocket support — no Redis cluster needed.
SOC 2 + HIPAA require audit-grade access controls to production. As Willow grows from YC X25 stage into enterprise sales, the security reviews get harder. Cloudflare Access closes the loop — identity-aware, audit-logged access to admin consoles and model environments without standing up a separate IdP stack.
50K+ users with a free tier and a $15/mo paid tier = a magnet for automated abuse: fake signups, free-tier exploitation, scraped binaries. Bot Management at the edge stops the abuse before it touches the auth backend; Turnstile drops in cleanly on signup and download flows.
"Just say a few quick words. Willow turns it into a fully polished message." Every Scribe invocation is an LLM call. Across 50K+ users typing emails and Slack messages and Cursor prompts, those requests cluster brutally — same draft-an-apology, same write-a-follow-up, same rewrite-this-more-professional patterns. The cache hit rate is structural, and AI Gateway captures it from request one.
Voice dictation is one of the most edge-amenable workloads in software: small audio packets in, structured text out, latency-sensitive at every step. Add Scribe's LLM layer on top, and you're now also paying for inference per invocation. AI Gateway turns both into one observable, attributable cost line — before the Series A inference bill becomes a board-meeting agenda item.
Mac, Windows, and iPhone have different update cadences, different binary sizes, different telemetry shapes, different App Store / Notarization / Microsoft Store distribution flows. Each platform's binary delivery, telemetry ingest, and crash reporting can live in its own Worker namespace inside Workers for Platforms — same edge, isolated state.
Every row is sourced from public DNS records and HTTP response headers on willowvoice.com, app.willowvoice.com, and api.willowvoice.com. The purple rows are already running on Cloudflare today. The orange column is the expansion footprint.
Scribe just shipped. The banner is live on willowvoice.com today. Every architectural decision being made this quarter — what governs Scribe's inference, how attribution works as Teams ramps, what the unit economics look like at 500K users — will define the inference cost curve for the rest of 2026 and 2027. AI Gateway is the cheapest hour you can spend in front of that curve.
You're already on Cloudflare. DNS via christian + dorthy. The API plane via anycast. No procurement event to start, no security review to begin, no MSA to negotiate. Expanding the footprint from DNS + API to AI Gateway + R2 + Workers for Platforms is the most natural roadmap conversation in the lineup.
YC X25 timing. The Series A architecture decisions get locked in over the next 12–18 months. Picking the runtime now — while the team is small enough to move fast and the user base is small enough that re-platforming is cheap — is materially cheaper than doing it after Teams customers depend on it.
The interesting conversation is which of these primitives is closest to your current sprint: AI Gateway behind Scribe, R2 for the binary CDN, Vectorize for context-aware spelling, or Workers for Platforms behind the Teams plan. I'd rather hear what's actually on your roadmap than guess.