Open source / self-hosted 10 services

This category is not relays at all, but open-source projects you can use to run a relay of your own — One API, New API, LiteLLM and similar. What they share: open code, self-deployable, and data entirely under your own control.

When is self-hosting worth it? The test is fairly clear: the data is genuinely sensitive and cannot pass through a third party; the call volume is large enough to amortise the operational cost; and someone on the team can take on deployment and maintenance. If any one of the three is missing, a ready-made service is usually the better deal.

The cost of self-hosting is not just a server. You also have to account for where the upstream keys come from (you connect to each vendor's open platform yourself), high-availability design (a single-machine deployment stops everything when it fails), and ongoing maintenance (upstream API changes have to be tracked). Once all of that is counted, "self-hosting is cheaper" usually does not hold — what you buy is control, not savings.

A pragmatic middle path is a self-hosted gateway with official upstreams: use a tool such as One API for unified authentication, quotas and logs, and connect directly to each vendor's official platform. That keeps control of your data and accounting without having to run the forwarding path yourself.

• Most stable：Highest current uptime. Fewer samples means more distortion, so we state the source (public dataset / our own measurement) and you can check it on the detail page.
• Fastest：Ordered by the home-page response time of the most recent probe. A single measurement is noisy, so treat it as a range rather than an absolute.
• Broadest model coverage：This uses the model count our endpoint probe actually detected, not the support list the service advertises — the two are measured differently, and the advertised figure is usually the more optimistic one.

Is self-hosting cheaper than using a ready-made service?

Usually not, unless your volume is large. What you save is the rate markup; what you add is server cost, the labour for deployment and maintenance, and the work of high-availability design. At modest monthly volume, a ready-made service's markup is normally less than the hidden cost of self-hosting.

What is the difference between One API and New API?

New API is a fork that continues active development on top of One API, with a faster-moving feature set and quicker support for newer protocols. Choose on maintenance activity and the range of upstreams you need — both provide the core ability to unify multiple upstreams behind one endpoint.

Where do the upstream keys come from once I self-host?

You register on each vendor's open platform and obtain them yourself. That means dealing with each vendor's identity requirements, payment methods and quota limits — work that is routinely underestimated. If avoiding the markup is your only reason, price this part first.

Does a self-hosted gateway guarantee no downgrading and no substitution?

Yes — and that is the most concrete value of self-hosting: there is no third party in the path, so the model you request is the model you reach. The price is carrying upstream stability yourself: when the official platform throttles you, there is no alternative channel.

Is self-hosting suitable for a small team?

Not if nobody can maintain it continuously. Self-hosting means tracking upstream API changes, handling certificates and domains, and running backups and monitoring. A reasonable compromise is to start with a ready-made service and re-evaluate once both your volume and your data sensitivity pass a threshold.