Persistent global cache
Repeated strings can be served from cache rather than creating another vendor charge.
- Cache lookup before vendor call
- Automatic write-back after success
- Lower repeat spend and faster responses
Floutai Translate / Translation API Proxy Cache
Keep your vendor.
Spend less on repeats.
Put Flout in front of Microsoft, Google and DeepL. Repeat translations are served from a persistent global cache instead of being billed again.
Explore the proxy ↗
Built for developers and API-driven platforms
translate()cachesaved↺
Core economic benefit
The more your content repeats,
the more you save.
Repeated strings, pages, products, interface labels, and content fragments do not need to become repeated vendor charges.
1. Your app sends the same vendor-shaped request.
→2. Flout checks persistent cache first.
→3. A vendor call happens only when it is needed.
Designed for the workload
A cost-reduction layer, not more infrastructure.
Vendor limit handling
Accept large requests, chunk them safely for the vendor, and reassemble results transparently.
- Up to 500,000 characters per request
- Automatic vendor-safe chunking
- Results returned in original order
Stable endpoint
Your application calls one endpoint while Flout handles routing and engine selection underneath.
- One integration point
- Engine selection via header
- Switch vendors without app rewiring
Vendor parity
Keep your existing vendor request and response shape while adding caching and routing.
- Vendor-native request format
- Vendor-native response format
- Status codes and errors pass through
Also built in
Centralised authorisation.
Hard guardrails.
Flout centralises vendor credentials at the proxy layer, enforces customer-level access, and stops oversized requests before they can turn into runaway usage.
Customer keyAuthorise at the proxy layer.
500,000 charactersA hard per-request ceiling.
HTTP 413Fail fast when a payload exceeds the limit.
Translation cost control