OpenAI compatible API · Attested · Public status

Azure OpenAI Alternative — Attested Private Inference

Keep the privacy that put you on Azure OpenAI. Hardware-attested inference, 220+ models, automatic provider fallback, OpenAI-compatible API. Verify it live.

Verify gateway

Onebase URL to migrate

100sof models and routes

Noneprompt logs by default

Azure OpenAI alternative

Azure OpenAI promises privacy in a contract; TrustedRouter proves it with hardware attestation you can check live.

Teams comparing alternatives to Azure OpenAI usually landed there for one reason: the data-handling terms. Then the operational bill arrives. Deployment quotas that take support tickets to raise. Models retired on Microsoft's schedule, with the migration work left to you. A catalog that only ever holds one vendor's models.

TrustedRouter keeps the property you were buying. Every prompt runs through a hardware-attested confidential-compute gateway. The gateway source is open, the image digest is published, and one curl returns an attestation signed by the CPU vendor's root key, bound to your live TLS session. TrustedRouter does not store prompt or output content by default. Privacy you can check beats privacy you're promised.

Check the attestation Browse 220+ models

migrate.pyPython

from openai import OpenAI

client = OpenAI(
    base_url="https://api.trustedrouter.com/v1",  # was: your Azure endpoint
    api_key="tr-your-key",
)

reply = client.chat.completions.create(
    model="trustedrouter/auto",
    messages=[{"role": "user", "content": "Hello"}],
)

Capacity

Automatic provider rollover

Routes are served across 30+ providers. When a provider goes down, requests roll over to another serving the route automatically. Latency numbers come from real routed requests, published at the latency benchmarks.

Catalog

220+ models, 30+ providers

Claude, GPT, Gemini, DeepSeek V4, Kimi K2.7, Qwen 3.5, GLM-5 and more behind one OpenAI-compatible API. Meta-routes decide per request: trustedrouter/auto for best fit, trustedrouter/cheap for the cheapest capable route in a TEE. Compare at /choose.

Privacy tiers

Set privacy per route

Three tiers: Open, Zero-Data-Retention, and TEE, where even the serving provider cannot read the prompt. Chinese open-weight models such as DeepSeek and Kimi are served by non-Chinese hosts on attested infrastructure. Details on the security page.

Azure OpenAITrustedRouter

Privacy modelContractual commitments backed by Microsoft's compliance programHardware attestation bound to the live TLS session; open-source gateway, published image digest

Model catalogOpenAI models, tightly integrated with Azure services220+ routes across 30+ providers: Claude, GPT, Gemini, DeepSeek, Kimi, Qwen, GLM, more

CapacityReserved capacity if approved; quotas set per region and deploymentAutomatic provider fallback; requests roll over when a provider goes down

Model lifecycleModels retire on Microsoft's schedule; migrations are your workMulti-provider routes; no single vendor decides what stays available

Network and billingVNet integration, private endpoints, committed-spend agreementsPublic attested endpoint; prepaid credits, BYOK, or crypto pay-per-request

Compliance postureMicrosoft's audit certificationsVerifiable architecture plus SOC 2 and HIPAA readiness documentation to assess

For your compliance team

Verify, don't trust.

TrustedRouter publishes a DPA, a BAA, a subprocessor list, and SOC 2 and HIPAA readiness documentation. None of these claim a certification. They give your compliance team a verifiable architecture to assess directly, with the live attestation as evidence. An EU gateway with EU-focused routing covers European workloads.

The pattern holds at production scale: a document-processing company scaled from zero to over a billion tokens per week through the attested gateway within three weeks of onboarding. Pricing is a thin markup over provider list prices, per model, at /pricing. Try any route first in the playground.

Questions

Is TrustedRouter SOC 2 or HIPAA certified?

No. TrustedRouter publishes SOC 2 readiness and HIPAA readiness documentation, plus a DPA, BAA, and subprocessor list. None of them claim a certification. The offer is verifiable architecture plus readiness documentation your compliance team can assess. The prompt path runs in a hardware-attested, open-source gateway whose attestation you can check live, which is evidence an audit report alone does not give you.

How do I migrate from Azure OpenAI to TrustedRouter?

Change the base URL. TrustedRouter exposes an OpenAI-compatible API at https://api.trustedrouter.com/v1, so you keep your SDK, your model ids, and your existing code. After the switch you get 220+ model routes across 30+ providers, automatic provider fallback when one goes down, and meta-routes like trustedrouter/auto that pick the best-fit route per request.

How do I verify that prompts stay private?

Request an attestation from the live gateway: call the attestation endpoint with a nonce and you get back a JWT signed by the CPU vendor's root key. The image digest matches the published open-source artifact, and the attestation binds to the live TLS session, so it cannot be replayed. TrustedRouter does not store prompt or output content by default. The full procedure is on the security page.

How does TrustedRouter handle capacity and quotas?

Routes are served across multiple providers. When a provider goes down, requests roll over to another provider serving the route automatically. Latency is measured from real routed requests and published on the latency benchmarks page. Payment is prepaid credits through Stripe, bring-your-own provider keys, or crypto pay-per-request through x402.