FastRoutervs.Requesty
Requesty has built the best European LLM gateway in the market and made GDPR-grade data residency its core promise. FastRouter is built for global scale with deeper routing, evals, and governance. Where each one wins is genuinely clear.
By Siv Souvam~13 min readShort version
The quick decision
| If you are... | Use... | Why? |
|---|---|---|
| EU data residency is non-negotiable | Requesty | EU-only by design (AWS Frankfurt). GDPR-grade. Auto PII scrubbing. |
| Need evals, MCP vault, or deeper routing | FastRouter | Smart + Auto + GEPA evals, MCP credential vaulting, 7 routing strategies. |
| European startup that wants a local vendor | Requesty | EU-HQ, local procurement, aligned regulatory fit. |
| Global scale, no hard residency mandate | FastRouter | 0% markup, multi-region available, AI Auto Router driven by your evals. |
At a glance: Key metrics
| Metric | FastRouter | Requesty |
|---|---|---|
| Markup (BYOK) | 0% with BYOK | 5% markup on model costs |
| Routing strategies | 7 (incl. AI Auto) | Smart routing + cascading fallback |
| Built-in evaluations | Smart + Auto + GEPA + Video | Not in scope today |
| EU data residency | Available on enterprise plans | EU-only by design |
Feature matrix
| Capability | FastRouter | Requesty |
|---|---|---|
| Model catalog | Major frontier + open | ~400+ models, 160+ providers |
| AI Auto Model Router | Per request, eval-driven | Smart routing (complexity-tier) |
| Smart / Automatic Evaluations | Live production evals | Not in scope today |
| GEPA prompt optimization | Supported | Not supported |
| MCP credential vaulting | Agents never see raw keys | Not in current docs |
| EU data residency | Enterprise plans | EU-only by design (core differentiator) |
| Auto PII redaction | Supported | Built-in, real-time scrubbing |
The EU residency question
Requesty is hosted only in AWS Frankfurt (eu-central-1). All processing within EU borders, full GDPR compliance, zero cross-border transfers — structurally, not as a configuration. For European teams whose compliance officer needs to sign off on "no US data transfers, ever," Requesty's posture is the cleanest in the category.
FastRouter offers EU regional deployment as a configuration on enterprise plans with the same zero-data-retention defaults. For teams without a hard EU-only mandate, functionally equivalent. For strict mandates ("control plane must be EU-only"), Requesty's "no other region exists" architecture is structurally cleaner.
Final decision tree
EU residency is a hard, non-negotiable requirement? → Requesty. Cleanest positioning in the category.
Want EU residency plus evals, MCP, deeper routing? → FastRouter with enterprise EU deployment.
No residency mandate, scale matters? → FastRouter. 0% markup, evals, deeper routing.
European startup buying European? → Requesty. Local-vendor argument is real.
Side-by-side
The full feature breakdown
✓ supported, ✗ not supported, ◑ partial.
| Capability | FastRouter Full-stack gateway | RequestyEU-first gateway |
|---|---|---|
| Markup on inference | 0% with BYOK | 5% markup on model costs (BYOK supported separately) |
| Model catalog | Major frontier + open providers | ~400+ models, 160+ providers |
| Routing strategies | 7: category, priority, lowest latency, lowest price, highest throughput, weighted, AI Auto | Smart routing (complexity-aware), cascading fallback, latency-based, cost-optimization, load balancing |
| AI Auto Model Router | Per-request, eval-driven | ◑Smart routing handles complexity tiers; not full per-request quality scoring |
| Smart / Automatic Evaluations | Live production evals | Not in scope today |
| GEPA prompt optimization | Supported | Not supported |
| Video evaluations | Supported | Not supported |
| MCP credential vaulting | Supported | Not confirmed in current docs |
| Live observability dashboard | Supported | Live Logs — tokens, latency, cost real-time |
| Auto PII redaction | Supported | Built-in, real-time scrubbing |
| Workspaces / RBAC | Workspace-level kill-switches | Owner / Admin / Developer / Viewer; cascading caps |
| Per-team / per-project budget caps | Supported | Org → team → project → key cascading |
| Model allowlists per team | Supported | Approved Models feature |
| EU data residency (Frankfurt) | ◑Available on enterprise plans, not the default region | EU-only by design — core differentiator |
| Zero data retention | ◑Configurable per workspace on enterprise plans | Real-time proxy by default; nothing stored after delivery |
| SOC 2 Type II | Supported | Supported |
| HIPAA | Supported | ◑Not explicitly confirmed in public materials |
| OpenAI-compatible endpoint | Supported | router.requesty.ai/v1 |
| 7-day passive audit | Supported | Not supported |
Read the matrix by constraint. If GDPR + EU-only is non-negotiable, Requesty's positioning is genuinely better — it's the only thing they do, and they do it well. If you don't have that constraint, the gateway depth gap is the more decisive factor.
EU residency
Where Requesty's positioning is most defensible
Requesty is hosted in AWS Frankfurt (eu-central-1). All processing happens within EU borders, there are no cross-border transfers, GDPR compliance is full, and a Data Processing Agreement is available on request. The zero-data-retention guarantee is structural — the gateway is a real-time proxy, not a logging platform that also proxies — so prompts and completions are never stored after delivery. Encryption is TLS 1.3 in transit and AES-256 at rest for the metadata that does get persisted.
For European teams whose compliance officer needs to sign off on "no US data transfers, ever," that single fact often closes the procurement conversation faster than any feature set on the FastRouter side could compete with. Requesty's positioning as the EU-resident gateway is earned, not just claimed.
FastRouter offers EU regional deployment as a configuration option on enterprise plans, with the same zero-data-retention defaults and equivalent encryption. For teams without a hard EU-only mandate, this is functionally equivalent. For teams with a strict mandate that the entire control plane must be EU-only, Requesty's "we don't even have a US region" architecture is a stronger story.
If your compliance officer's answer to "where does the data live" must be "Frankfurt, only Frankfurt, by design," Requesty wins that conversation.
Routing
Both routers work. The depth gap is real but specific.
Requesty's routing is a clean implementation: smart routing inspects request complexity and matches it to a model tier (cheap models for simple queries, premium for hard ones), cascading fallbacks chain primary → secondary → tertiary providers with sub-20ms failover, latency-based routing tracks live P50/P90/P99 and switches to fastest, and load balancing distributes across multiple providers simultaneously for reliability. The 99.9% uptime SLA is part of the pitch.
FastRouter's seven strategies cover the same ground and add three primitives Requesty doesn't expose today: category-based routing as a first-class strategy (map prompt classes to model groups without building complexity heuristics), weighted shuffle for explicit canary releases, and the AI Auto Model Router that selects per request from cost, latency, and quality signals fed by the eval layer.
For straightforward production routing, the gap is narrow. For teams that want to A/B route between models or have the gateway make per-request quality-aware decisions, FastRouter has more knobs.
Evals & optimization
The widest gap is here
Requesty's product surface is intentionally focused. Observability is real-time and useful, governance is well-designed, and routing is solid — but evaluations and prompt optimization aren't part of the current product. The team has signaled a focus on production gateway and observability rather than offline experimentation tooling.
FastRouter ships:
Smart Evaluations — AI quality scoring on live production traffic.
Automatic Evaluations — background sampler that benchmarks competing models on your real traffic.
GEPA — Generative Evolutionary Prompt Architecture for Pareto-optimal cost/quality.
Video evaluations — compare model output on video inputs, exclusive in this category.
If your roadmap includes "we should know which model is actually best for each workload, continuously" — that's where FastRouter pulls clearly ahead.
Governance
Both have real governance. Different shapes.
Requesty's governance model is well-thought-through: Owner / Admin / Developer / Viewer roles with cascading permissions; budget enforcement at org → team → project → key levels with cascading caps; Approved Models lets org admins curate which models teams can call; virtual API keys per project with provider credential isolation; complete RBAC. PII redaction is automatic for emails, phone numbers, SSNs, and credit card numbers before requests reach the model.
FastRouter offers the same primitives plus MCP credential vaulting (agents and tool callers never see raw provider keys — the gateway injects credentials server-side) and workspace-level kill-switches that hard-stop spend. For agentic workloads where MCP servers are calling tools on behalf of the user, the credential vault closes a real exfiltration surface that Requesty doesn't address today.
Pricing
5% vs 0% — context matters
Requesty charges 5% markup on model costs, $6 in starting credits, BYOK supported separately for teams that want their own provider keys, and volume discounts available at the Enterprise tier. The 5% covers the entire feature surface — routing, governance, observability, PII redaction, EU hosting.
FastRouter charges 0% markup on inference when you BYOK. Platform pricing is a flat managed-service fee instead of percentage-of-spend, which means the gateway tax doesn't compound as your usage grows.
At small scale (sub-$2K/mo), 5% is rounding error and Requesty's all-in pricing is genuinely simple. At larger scale ($10K+/mo), the 5% delta becomes meaningful: $500/mo at $10K, $5,000/mo at $100K. If EU residency is the deciding factor, the 5% is often a fair price for the constraint. If it's not, the 0%-markup math compounds in FastRouter's favor.
Honest take
When each one wins
When Requesty is the better pick
EU data residency is non-negotiable
- Frankfurt-only by design — full GDPR compliance
- Zero cross-border transfers, structurally
- The cleanest answer for European compliance
You want a simple, all-in-one EU gateway
- 5% covers everything — no plan tiers to navigate
- Real-time observability included
- Auto PII scrubbing built in
Your needs map closely to the EU-first product surface
- Cascading governance is well-designed
- Smart routing covers most production needs
- Live Logs dashboard is genuinely useful
You're a European startup buying European
- EU-headquartered vendor
- Local procurement and support
- Aligned regulatory and language fit
When FastRouter is the better pick
You don't have a hard EU-only mandate
- 0% markup vs 5% — compounds at scale
- EU regional deployment available if needed later
- The EU constraint isn't paying for capability
You need evals and prompt optimization
- Smart + Automatic Evaluations on live traffic
- GEPA prompt optimization runs continuously
- Video evals — exclusive in the category
You're running agentic workloads with MCP
- MCP credential vaulting
- Per-tool budget caps and rate limits
- Audit trail across multi-step agent runs
You want deeper routing knobs
- 7 strategies including AI Auto Model Router
- Category-based routing as a first-class primitive
- Weighted shuffle for explicit canary releases
How to choose
The decision tree
EU data residency is a hard, non-negotiable requirement
Use Requesty. Their EU-only positioning is the cleanest in the category and the rest of the product surface is solid.
You want EU residency but also need evals, MCP, and deeper routing
Talk to FastRouter about enterprise EU deployment. Not the default tier, but available alongside the broader feature set.
You don't have a residency mandate and your scale is meaningful
Use FastRouter. 0% markup, evals, and routing depth compound favorably as you grow.
You're a European startup that wants to buy European
Use Requesty. The local-vendor argument is real for procurement.
You're already on Requesty and bumping into the eval / MCP gap
Talk to FastRouter. Both are OpenAI-compatible; migration is a base URL swap and a key change.
Common questions
Yes. AWS Frankfurt (eu-central-1) is the only hosting region — that's the architectural commitment. For teams whose compliance officer needs structural assurance that data never leaves the EU, that's the strongest answer in the category.
Yes, but with caveats. EU regional deployment is available on enterprise plans rather than as a default tier, and ZDR is configured per workspace as part of that setup. The architectural difference is that FastRouter is a global product where EU residency is an option you can turn on, while Requesty is EU-only by design. For most teams the functional outcome is the same. For teams with strict "control plane must be EU" mandates, Requesty's posture is structurally cleaner because there's no other region to misconfigure.
FastRouter is HIPAA-compliant with a BAA on enterprise plans. Requesty's HIPAA status isn't explicitly confirmed in public materials we've seen — if HIPAA is on your requirements list, ask both vendors directly.
Requesty's smart routing is a complexity heuristic — it inspects the request and routes to an appropriate model tier (small/fast for simple queries, large for hard queries). FastRouter's AI Auto Model Router goes further: it picks per request from real-time cost, latency, and quality signals fed by the eval layer. Both are valuable; AI Auto adds a quality dimension that complexity-only routing can't.
Both are OpenAI-compatible. The bulk of migration is endpoint and key changes. Workspace and team mappings translate cleanly; budget cap structures are similar. We help with cutover for production workloads.
MCP support isn't documented in Requesty's current public materials. If MCP and credential vaulting are on your roadmap, that's a real gap to weigh. FastRouter ships MCP credential vaulting as a first-class primitive.
5% is fine at small scale and a meaningful line item at large scale. At $10K/mo inference that's $500/mo; at $100K/mo it's $5K/mo. If EU residency is the deciding factor, that's often a fair price for the constraint. If it's not, the math favors a 0%-markup model like FastRouter's.