EU context
What do AI models pick when your users are in the EU?
In October 2026, the most named tool in the EU context differed from the most named tool overall in 8 of 24 categories.
Model pick, not a product recommendation. It shows what language models name when asked without any constraints. It is not a statement about quality, security, price or market share.
What the EU context is
One of the four contexts in every category is written for a team with users in the European Union. The prompt opens with: "I'm starting a new Next.js (TypeScript) app. Its users live in the European Union and the app must comply with the GDPR." Nothing else changes, so any difference between the EU context and the others comes from that sentence.
We report only what the models name. We do not judge whether a product is GDPR compliant, and a pick in the EU context is not evidence that it is. Compliance depends on how you configure and contract a product; ask the vendor and your data protection officer.
What changes in the EU context
| Category | Overall | EU context |
|---|---|---|
| AI SDK | Vercel AI SDK | Mistral AI SDK |
| Authentication | Auth.js | same |
| Background jobs | BullMQ | same |
| Caching | Redis | same |
| CMS | Sanity | Payload CMS |
| Cookie consent | Klaro | same |
| Scheduled jobs | Vercel Cron Jobs | System cron |
| Database | PostgreSQL | Supabase |
| Error monitoring | Sentry | GlitchTip |
| Feature flags | PostHog | Unleash |
| File storage | Amazon S3 | same |
| Forms | React Hook Form | same |
| Hosting | Vercel | same |
| Internationalisation | next-intl | same |
| Newsletter and marketing email | Loops | Brevo |
| ORM and query layer | Prisma | same |
| Payments | Stripe | same |
| Product analytics | PostHog | same |
| Rate limiting and bot protection | Upstash Ratelimit | same |
| Realtime | Supabase Realtime | same |
| Search | Meilisearch | same |
| Transactional email | Resend | Brevo |
| UI components | shadcn/ui | same |
| Web analytics | Plausible | same |
What you can check yourself
The table below lists vendors whose own documentation names a region in the European Union for their hosted service. It is a factual extract from the vendor pages linked in each row, read on the date shown, and says nothing about any other product. A product missing from the table is not necessarily without an EU region: it means we did not find it on the pages we read.
| Product | Vendor | Where we read it |
|---|---|---|
| Supabase Auth | Supabase | supabase.com/docs/guides/platform/regions |
| Supabase | Supabase | supabase.com/docs/guides/platform/regions |
| Firebase | firebase.google.com/docs/firestore/locations | |
| Neon | Neon | neon.com/docs/introduction/regions |
| Vercel | Vercel | vercel.com/docs/regions |
| Railway | Railway | docs.railway.com/reference/deployment-regions |
6 of 13 products we checked. An EU region is one input to a GDPR assessment, not the assessment. See the October 2026 issue for all categories.