Requesty

Name: Requesty
Brand: Requesty
Rating: 5 (3 reviews)

AI Native

Requesty is an OpenAI-compatible API gateway and router that proxies requests to 600+ LLM models/providers, providing intelligent routing and failover, prompt caching for token-cost reduction, governance controls, and observability metrics.

Est 2023|Valuation $11.4M|Raised $3.6M|21 Ref Customers

LinkedIn 3K|Website|FTEs 5|HQ London, United Kingdom

Published Oct 16, 2026

01Competitive Landscape

| Aspect | Requesty | OpenRouter | LiteLLM | |---|---|---|---| | Starting Price | - Pay-as-you-go - Vendor states a published percentage markup on model costs - Vendor-stated promotional free credits available | - Pay-as-you-go - Fees depend on usage mode; BYOK uses a tiered fee model with no fee up to published thresholds and a percentage fee beyond those thresholds (vendor documentation) | - OSS: free to self-host - Enterprise: priced for support/enterprise features (vendor-stated) | | Suitable For | - Teams seeking a single OpenAI-compatible gateway across multiple providers - Teams wanting routing/failover, governance, and dashboards in one product | - Developers needing a broad model catalog, unified billing, and ecosystem integrations - BYOK users within published free usage thresholds | - Teams that require self-hosting to keep data/keys in proprietary infrastructure - Platform teams comfortable operating a proxy/gateway | | Key Strength | - Integration via OpenAI-compatible endpoint swap - Combined routing, caching, failover, governance, and observability features - EU endpoint/data residency claims | - Large ecosystem and developer tooling integrations - Public documentation on BYOK fee thresholds and developer-focused tooling | - Infrastructure control and extensibility - Avoids SaaS gateway dependency | | Key Weakness | - Adds an external dependency and potential latency overhead - Published percentage markup can be material at scale - Community reports of client integration issues in some cases | - Fee structures and thresholds can be confusing for some users - Also introduces a dependency in the request path | - Operational burden to run and maintain - Enterprise features/support are typically paid | - Direct competitors and their key differentiators - OpenRouter - Strong presence in model aggregation and developer tooling with public documentation on fee thresholds for BYOK use cases. - LiteLLM - Self-hosted option that keeps data and keys within customer infrastructure; enterprise features may be monetized separately. - Portkey - Positioned as an "AI Gateway" with observability and cost management features, oriented toward enterprise buyers. - Helicone - Combines gateway and observability features with options for pass-through billing or BYOK observability. - Feature comparison: where Requesty appears relatively strong vs weak - Relative strengths (based on vendor claims and community positioning): - Bundled feature set combining routing, caching, failover, governance, and observability - Integration model that uses OpenAI-compatible endpoint configuration to reduce migration effort - Relative limitations (based on market patterns and limited independent validation): - Organizations requiring fully private, self-host-only gateways may prefer open-source/self-host competitors - Limited third-party reviews and analyst coverage relative to larger competitors - Pricing comparison: value proposition vs alternatives - Requesty’s stated published percentage markup is similar in structure to percentage-fee BYOK models from other providers under certain thresholds. - For high-volume workloads, a percentage-based gateway fee can be significant; self-hosted options reduce gateway fees but increase engineering and operations costs. - Customer testimonials comparing this product to competitors - Informal community comparisons to OpenRouter exist in developer/proxy contexts, but they are not structured enterprise evaluations. - Market share and adoption trends - There is insufficient independent data in the accessible sources to estimate market share. Vendor-reported usage metrics are unverified.

02Market Map

—

Published Oct 16, 2026

01Competitive Landscape

Aspect	Requesty	OpenRouter	LiteLLM
Starting Price	- Pay-as-you-go

Vendor states a published percentage markup on model costs
Vendor-stated promotional free credits available | - Pay-as-you-go
Fees depend on usage mode; BYOK uses a tiered fee model with no fee up to published thresholds and a percentage fee beyond those thresholds (vendor documentation) | - OSS: free to self-host
Enterprise: priced for support/enterprise features (vendor-stated) | | Suitable For | - Teams seeking a single OpenAI-compatible gateway across multiple providers
Teams wanting routing/failover, governance, and dashboards in one product | - Developers needing a broad model catalog, unified billing, and ecosystem integrations
BYOK users within published free usage thresholds | - Teams that require self-hosting to keep data/keys in proprietary infrastructure
Platform teams comfortable operating a proxy/gateway | | Key Strength | - Integration via OpenAI-compatible endpoint swap
Combined routing, caching, failover, governance, and observability features
EU endpoint/data residency claims | - Large ecosystem and developer tooling integrations
Public documentation on BYOK fee thresholds and developer-focused tooling | - Infrastructure control and extensibility
Avoids SaaS gateway dependency | | Key Weakness | - Adds an external dependency and potential latency overhead
Published percentage markup can be material at scale
Community reports of client integration issues in some cases | - Fee structures and thresholds can be confusing for some users
Also introduces a dependency in the request path | - Operational burden to run and maintain
Enterprise features/support are typically paid |
Direct competitors and their key differentiators
- OpenRouter
  - Strong presence in model aggregation and developer tooling with public documentation on fee thresholds for BYOK use cases.
- LiteLLM
  - Self-hosted option that keeps data and keys within customer infrastructure; enterprise features may be monetized separately.
- Portkey
  - Positioned as an "AI Gateway" with observability and cost management features, oriented toward enterprise buyers.
- Helicone
  - Combines gateway and observability features with options for pass-through billing or BYOK observability.
Feature comparison: where Requesty appears relatively strong vs weak
- Relative strengths (based on vendor claims and community positioning):
  - Bundled feature set combining routing, caching, failover, governance, and observability
  - Integration model that uses OpenAI-compatible endpoint configuration to reduce migration effort
- Relative limitations (based on market patterns and limited independent validation):
  - Organizations requiring fully private, self-host-only gateways may prefer open-source/self-host competitors
  - Limited third-party reviews and analyst coverage relative to larger competitors
Pricing comparison: value proposition vs alternatives
- Requesty’s stated published percentage markup is similar in structure to percentage-fee BYOK models from other providers under certain thresholds.
- For high-volume workloads, a percentage-based gateway fee can be significant; self-hosted options reduce gateway fees but increase engineering and operations costs.
Customer testimonials comparing this product to competitors
- Informal community comparisons to OpenRouter exist in developer/proxy contexts, but they are not structured enterprise evaluations.
Market share and adoption trends
- There is insufficient independent data in the accessible sources to estimate market share. Vendor-reported usage metrics are unverified.

02Market Map

—

Aspect	Requesty	OpenRouter	LiteLLM
Starting Price	- Pay-as-you-go

Vendor states a published percentage markup on model costs
Vendor-stated promotional free credits available | - Pay-as-you-go
Fees depend on usage mode; BYOK uses a tiered fee model with no fee up to published thresholds and a percentage fee beyond those thresholds (vendor documentation) | - OSS: free to self-host
Enterprise: priced for support/enterprise features (vendor-stated) | | Suitable For | - Teams seeking a single OpenAI-compatible gateway across multiple providers
Teams wanting routing/failover, governance, and dashboards in one product | - Developers needing a broad model catalog, unified billing, and ecosystem integrations
BYOK users within published free usage thresholds | - Teams that require self-hosting to keep data/keys in proprietary infrastructure
Platform teams comfortable operating a proxy/gateway | | Key Strength | - Integration via OpenAI-compatible endpoint swap
Combined routing, caching, failover, governance, and observability features
EU endpoint/data residency claims | - Large ecosystem and developer tooling integrations
Public documentation on BYOK fee thresholds and developer-focused tooling | - Infrastructure control and extensibility
Avoids SaaS gateway dependency | | Key Weakness | - Adds an external dependency and potential latency overhead
Published percentage markup can be material at scale
Community reports of client integration issues in some cases | - Fee structures and thresholds can be confusing for some users
Also introduces a dependency in the request path | - Operational burden to run and maintain
Enterprise features/support are typically paid |
Direct competitors and their key differentiators
- OpenRouter
  - Strong presence in model aggregation and developer tooling with public documentation on fee thresholds for BYOK use cases.
- LiteLLM
  - Self-hosted option that keeps data and keys within customer infrastructure; enterprise features may be monetized separately.
- Portkey
  - Positioned as an "AI Gateway" with observability and cost management features, oriented toward enterprise buyers.
- Helicone
  - Combines gateway and observability features with options for pass-through billing or BYOK observability.
Feature comparison: where Requesty appears relatively strong vs weak
- Relative strengths (based on vendor claims and community positioning):
  - Bundled feature set combining routing, caching, failover, governance, and observability
  - Integration model that uses OpenAI-compatible endpoint configuration to reduce migration effort
- Relative limitations (based on market patterns and limited independent validation):
  - Organizations requiring fully private, self-host-only gateways may prefer open-source/self-host competitors
  - Limited third-party reviews and analyst coverage relative to larger competitors
Pricing comparison: value proposition vs alternatives
- Requesty’s stated published percentage markup is similar in structure to percentage-fee BYOK models from other providers under certain thresholds.
- For high-volume workloads, a percentage-based gateway fee can be significant; self-hosted options reduce gateway fees but increase engineering and operations costs.
Customer testimonials comparing this product to competitors
- Informal community comparisons to OpenRouter exist in developer/proxy contexts, but they are not structured enterprise evaluations.
Market share and adoption trends
- There is insufficient independent data in the accessible sources to estimate market share. Vendor-reported usage metrics are unverified.