TensorProxyEU control plane

EU control plane for BYOK AI

Govern every model call without surrendering provider control.

Built for European software teams that need one OpenAI-compatible endpoint, enforced project budgets, understandable diagnostics, and provider billing that stays on their own accounts.

BYOKFailover controlsSpend ceilingsDiagnosticsEU control plane
OpenAI-compatible request path
const client = new OpenAI({
  apiKey: process.env.TENSORPROXY_API_KEY,
  baseURL: process.env.TENSORPROXY_BASE_URL,
});

await client.chat.completions.create({
  model: "gpt-4.1-mini",
  messages,
});
  1. Add your provider keyStore your own OpenAI or Anthropic credential.
  2. Mint a gateway keyGive your app one OpenAI-compatible endpoint to call.
  3. Inspect request outcomesSee request duration, tokens, and fallback reasons in the dashboard.

What the product actually does

Operational controls that stay close to the real architecture

One gateway, explicit governance

Authenticate with gateway keys, apply plan and budget policy, and keep the request path consistent for your application.

BYOK without shared billing

Customer traffic still bills against the customer's own provider account rather than a pooled platform key.

Ordered failover

Team plans can define provider order so requests keep moving when a preferred model path is unavailable.

Hard spend ceilings

Project budgets are enforced on the request path instead of being decorative dashboard numbers.

Diagnostics people can use

Review usage, request duration, token counts, and fallback reasons per request without exposing prompts or secrets.

EU-hosted control plane

Keep gateway configuration, team controls, budgets, and diagnostics on European infrastructure. Upstream inference location remains determined by the provider account and endpoint you choose.

How teams work through it

A concise flow from provider key to governed production traffic

01

Connect provider credentials

Add your OpenAI or Anthropic key once, then keep that boundary separate from your application runtime credentials.

02

Issue app-facing gateway keys

Give each environment a scoped key and direct existing SDK traffic at the OpenAI-compatible endpoint.

03

Operate with budgets and diagnostics

Watch request health, review activity, and control fallback order without changing the application contract again.

Start with the real product surface

Free tier: one project, two keys, seven days of retention.

No card required. Create an account, add a provider key, and send your first request through the gateway.

Create account