Vida Health delivers enterprise obesity and metabolic care — GLP-1 prescribing, behavioral health, continuous glucose monitoring integration, multicultural support — with HITRUST r2 certification and the 2026 MedTech Breakthrough Award for Best Virtual Care Platform. vida.com is already on Cloudflare DNS with a custom proxy. The expansion footprint is the developer platform underneath: AI Gateway for the GLP-1 + behavioral AI surface, R2 for the FHIR clinical corpus, Workers for Platforms for per-employer / per-health-plan tenancy, and Zero Trust for clinical staff access at HIPAA scale.
vida.com on Cloudflare DNS via fred / serena.ns.cloudflare.comvida.com#upstream-id: vida-proxy-2-corporate-site-443 — you've already built a custom CF proxy in front of WP EngineYou've already chosen Cloudflare for the edge — complete with a named custom proxy, which is unusual signal that someone on the platform team trusts the developer surface here. The next infrastructure layer is the part that needs to scale with the AI-care surface: the inference plane behind the AI coaching, the FHIR-grade content corpus, the per-employer / per-payor tenancy, and the clinical staff access plane that has to satisfy HITRUST auditors.
Each maps to something you ship today (the AI app, the clinical content library, the payor integrations, the device/RPM telemetry, the HITRUST-grade access controls) or something on the published roadmap. Status tags show what's already live in your Cloudflare footprint.
Authoritative DNS via fred / serena.ns.cloudflare.com, and the response headers reveal a named custom proxy: vida-proxy-2-corporate-site-443. The platform team already builds on the Cloudflare developer platform — this isn't a cold conversation.
Anthropic is verified on your apex TXT. Every coaching-conversation summary, every visit-note draft, every GLP-1 candidate screening that runs through Claude is a call that should be cached, attributed, audit-logged, and budget-capped. AI Gateway gives you all of that in one header change.
Each enterprise customer (employer, health plan, partner) has different formularies, different program inclusion rules, different cost-of-care targets, different audit requirements. Workers for Platforms gives each one their own Worker namespace with isolated keys, egress, logs, and AI budget — on the same edge.
Clinical content, care plan templates, multicultural language variants, FHIR resources, outcomes data. R2 holds it zero-egress; Vectorize indexes it for "find the closest care-plan template to this member's profile" in milliseconds. The retrieval layer for every Anthropic call.
HITRUST r2 requires audit-grade access controls to PHI-touching systems. Cloudflare Access gives identity-aware, audit-logged access to Canvas Medical, the Vida admin console, the AI experiment dashboards, and the Genesys PureCloud agent surface — without standing up a separate IdP stack.
Continuous glucose monitors (featured in your hero photo), wearables, scales — high-volume telemetry from member devices into the Vida care plane. Workers ingest at the closest of 330+ POPs to the device. Queues handle the async fan-out into clinical alerts, member dashboards, and outcomes pipelines.
iOS + Android app updates, app-side ML models, member-facing rich-media content (videos, multicultural assets), care-plan PDFs. R2 zero-egress + Workers + Smart Placement serves from the closest POP to each member — especially important for the multicultural / international member base.
HITRUST r2 + HIPAA require detailed, tamper-evident access logs for every PHI touch. Workers can stamp + hash every request at the edge before it ever touches an internal system. R2 with object versioning gives you immutable storage. Auditor-friendly by construction.
Eligibility-check forms, account creation, support portal — all high-value surfaces for synthetic-identity abuse, eligibility scraping by competitors, and credential stuffing on returning members. Bot Management at the edge stops the abuse before it touches Canvas Medical or any PHI-handling system.
"Member asks the Vida app about their GLP-1 dose" → an Anthropic call → FHIR + care plan retrieval → a behavioral-health-aware response → an audit trail every HITRUST auditor will want. Cloudflare runs each step on the same edge, on the same audit log, behind the same BAA.
Vida sells outcomes — weight loss, diabetes control, cost savings — not AI minutes. But the AI bill scales with member-engagement, not with outcomes. AI Gateway turns Anthropic spend from a monthly surprise into a per-payor, per-program, per-cohort cost line you can defensibly price into your enterprise contracts.
Employers want benefits-integrated obesity care. Health plans want medical-management partnership and outcome guarantees. Partners want embedded care delivery. Each one has its own contract terms, its own data residency, its own audit cadence, its own clinical formulary. That's not a feature flag — that's an isolation boundary.
Every row is sourced from public DNS records, the vida.com apex TXT, HTTP response headers, and the visible CSP allowlist. The magenta row is already running on Cloudflare today. The orange column is the expansion footprint.
The 2026 MedTech Breakthrough Award is a procurement moment. The award puts Vida in front of every Fortune 500 benefits team's "build the short list" exercise for 2026 RFPs. Every one of those RFPs will include a security architecture review. Cloudflare in front of the AI surface gives you a defensible answer the first time the question is asked.
You're already on Cloudflare with a custom proxy. vida-proxy-2-corporate-site-443 in the response headers tells me the platform team already trusts the developer-platform side. There's no procurement event to start, no security review to begin from zero, no MSA to negotiate. Expanding the footprint from DNS + custom proxy to AI Gateway + R2 + Workers for Platforms is the most natural roadmap conversation in the lineup.
The GLP-1 + AI coaching surface is exploding. Anthropic is already on your apex. Every new payor contract that wants outcomes guarantees means more AI calls per member. AI Gateway is the cheapest hour you can spend in front of that cost curve — before the per-payor margin math starts to matter at scale.
The interesting conversation is which of these primitives is closest to your current sprint: AI Gateway behind Anthropic, R2 + Vectorize for the FHIR + care-plan corpus, Workers for Platforms for per-payor tenancy, or Zero Trust for the clinician access surface. I'd rather hear what's actually on your roadmap than guess.