anonrouter
Sign up

AnonRouter vsVercel AI Gateway

Vercel AI Gateway is built around observability: centralized credentials, request logs, and spend controls for a team. AnonRouter is built around the opposite property, and publishes the code that enforces it.

Start building Compare the details

What’s the difference between and ?

Both services put one API in front of many providers and add failover. They disagree about what the layer in the middle should remember. Vercel AI Gateway centralizes credentials, request logs, and spend for a team that wants those controls without running its own proxy. AnonRouter puts a strict content-retention boundary and privacy-aware routing layer between your application and 200+ models.

  1. You + Ticket

    Anonymous

    encrypted

  2. Protected hardware

    Intel TDX enclave

    protected

  3. Your model

    Private

Protected hardware isolates prompt handling. The model and provider you choose determine the route’s privacy level.

At a glance

AnonRouter vs Vercel AI Gateway

Eight things AnonRouter does that a managed observability gateway does not. Every row is a capability, not a setting you have to trust someone to leave switched off.

Source of the code handling prompts

AnonRouter

Yes. Apache 2.0, including every component that can touch plaintext.

Vercel

No. The gateway is a closed, managed service.

Verifying the privacy claim

AnonRouter

Yes. Pull the enclave attestation with the SDK and check it against the published build.

Vercel

No. There is nothing to attest against, so the documentation is the guarantee.

Per-request logging

AnonRouter

None to inspect. Usage metadata exists only to settle your balance.

Vercel

Central to the product. Each request's provider attempts, latency, tokens, status, and cost are recorded.

End-to-end encrypted routes

AnonRouter

Yes, wherever the provider runs an enclave. The router holds no key.

Vercel

No. Prompts are handled by the managed gateway.

Confidential compute

AnonRouter

Yes. Prompt handling runs inside an attested hardware enclave.

Vercel

No. Not offered by the gateway.

Identity separated from request content

AnonRouter

Yes. A ticket flow splits account identity, plaintext, and provider credentials.

Vercel

No. Keys are team-scoped and usage is attributed to your team.

Privacy floor on automatic routing

AnonRouter

Yes. /auto stays inside a privacy boundary and fails closed when nothing qualifies.

Vercel

No. Routing and fallbacks are ordered by preference, not by a retention guarantee.

Account without an email address

AnonRouter

Yes. Private accounts open with a recovery phrase instead of an inbox.

Vercel

No. A Vercel account and team are required.

What each gateway is for

One is built to show you every request. One is built to keep none.

Vercel's logging is a feature, not an oversight: teams want it. That is exactly the design decision AnonRouter makes in reverse, and the reason the two suit different work.

“Inspect each request's model, provider attempts, latency, token usage, status, and cost in request logs.”
Vercel's own documentation, describing AI Gateway's request logging. AI Gateway docs

What the product optimizes for

AnonRouter

Non-retention. Routing, failover, and prepaid billing with no content and no per-request log to read back.

Vercel

Observability. Centralized credentials, request logs, budgets, and provider failover for a team.

Who the request belongs to

AnonRouter

A ticket. The system that knows your account and the system that sees content are separated.

Vercel

A Vercel team. Keys are team-scoped and usage is attributed for budgets and logs.

Code that can touch plaintext

AnonRouter

Published under Apache 2.0 as the confidential content plane, which is every component inside the enclave.

Vercel

Closed source. The gateway is a managed Vercel service.

How you check it

AnonRouter

Run the SDK, pull the enclave's attestation, and compare it against the published build.

Vercel

Read the security and compliance documentation.

Confidential compute

AnonRouter

Enclave-backed routes, and E2EE routes where the router holds no key at all.

Vercel

Not offered. Prompts are handled by the managed gateway.

Read the code that handles your prompt

Inspect the code that handles request content, then use the verification SDK to check a supported confidential route.

anonrouter/confidential-content-planeEvery component inside the attested TEE that can touch prompt or response plaintext. Apache-2.0.anonrouter/anonrouter-sdkVerify the confidential routes and run confidential inference from your own process, in JavaScript or Python. Apache-2.0.

Why AnonRouter

Privacy is part of the architecture

The value is not only access to models. It is what the router is structurally unable to retain.

Audit the router instead of trusting it

Every component that can touch prompt plaintext is published under Apache 2.0, and the SDK checks the enclave's attestation against that build.

Remove prompt logging from the product

Prompts and responses are never written to disk. There is no router-side content logging switch to enable later.

Know what you pay

Model usage is billed at listed rates. Credit purchases include a separately disclosed platform fee, currently 5%.

Separate identity from request content

The private ticket flow splits the systems that know your account, handle plaintext, and hold provider credentials.

Route inside a privacy boundary

The /auto router filters to eligible privacy levels first, then selects for capability, quality, and cost.

See what every route guarantees

Anonymous, Private, TEE, and E2EE labels make the actual privacy boundary visible before a request is sent.

Upstream provider policy still matters on both services. A no-log router cannot make every model provider private. Review the exact route label, and use an explicitly supported E2EE route when you need the strongest available boundary.

Which one is right for you?

Choose AnonRouter if…

  • A per-request log is a liability rather than a feature
  • You need to audit the code that handles prompts, not just read a policy
  • Enclave-backed or end-to-end encrypted routes are a requirement
  • Account identity and request content must stay separated
  • You want a private account without an email address

Choose Vercel AI Gateway if…

  • You want a per-request log of every routing attempt
  • Team budgets and spend caps are a hard requirement
  • Your stack is already built on the AI SDK
  • You rely on BYOK with automatic fallback

Common questions

Vercel documents request logs covering each request's model, provider attempts, latency, token usage, status, and cost, which is telemetry rather than prompt content. Vercel does not advertise storing prompt bodies, and nothing here claims it does. The structural point is narrower: the gateway is a closed managed service, so what it can see is not something you can verify from the outside, and the product's whole value is a durable per-request record tied to your team.
No. The AI SDK is open source, but the gateway itself is a managed Vercel service and its source is not published. AnonRouter publishes the part that matters most: the confidential content plane, every component inside the attested enclave that can touch prompt or response plaintext, is Apache 2.0 at github.com/anonrouter/confidential-content-plane.
Yes. AnonRouter is an OpenAI-compatible HTTP endpoint, so it works from Vercel Functions, edge runtimes, or any other host without special integration. Point your existing OpenAI client at AnonRouter's base URL with an AnonRouter key. Your application does not need to run anywhere in particular.
AnonRouter charges the listed model rates against prepaid credits. A separate platform fee is shown when you buy credits, currently 5% during the launch promotion. See each service's pricing page for its model rates and payment terms.
When you want the request log. If your team needs to inspect routing attempts, enforce budgets per project or per key, and keep an auditable record of spend, that is a real operational need and AnonRouter deliberately does not serve it. We cannot show you a per-request history of content we never keep.

Keep exploring

Compare across the ecosystem

AnonRouter vs OpenRouterAnonRouter vs LiteLLMAnonRouter vs Blackbox
View all comparisons

Sources & methodology

Check the primary sources

This comparison is published by AnonRouter and is not affiliated with Vercel AI Gateway. It uses current public product pages and documentation, reviewed September 16, 2026. Pricing can change; each service's live checkout is authoritative.

See for yourself

Point your OpenAI SDK at AnonRouter, or browse the catalog first. A private account does not need an email address.

Start building Browse models