1. How to read this page
This list is meant to make the vendor layer visible rather than forcing customers to infer it from the product or infrastructure stack.
Status values such as Live, Launch-planned / partial, and Planned are included so we do not overstate what is already active in the current production path.
2. Active and launch-planned subprocessors
| Vendor | Role | Data / workflow area | Status |
|---|---|---|---|
| Vercel | Frontend hosting and edge delivery | Public website and app shell | Live |
| Fly.io | Backend application hosting | API runtime and deployment target | Live |
| Supabase | Primary database hosting | Account, org, transcript, and product data | Live |
| Upstash | Redis cache and queue infrastructure | Rate limiting, cache, and queue support | Live |
| Cloudflare R2 | Object storage | Uploaded media and related storage flows | Live |
| Cloudflare | DNS, TLS, and edge network | Domain routing and edge protection | Live |
| Resend | Transactional email delivery | Verification and product email | Live |
| Stripe | Payment processing | Subscription and billing events | Launch-planned / partial |
| OpenAI | LLM-backed product features | Arbitration, summary, and translation flows | Live in enabled code paths |
| RunPod | GPU inference hosting | ASR workloads when production endpoints are enabled | Planned |
| Groq | Fallback ASR provider | Whisper fallback workloads when enabled | Planned |
| Google OAuth | Authentication provider | Optional Google sign-in once configured | Planned |
3. Questions and updates
If you need more detail about the current vendor set, email hello@yanascript.com with the subject line Subprocessor question.
This page should be read together with the Privacy Notice, which explains the broader handling of account data and customer content.