Upstream status
Not published to Relays
Ollama does not publish a status feed Relays can read, so no availability is reported here.
One alias in front of Ollama.
Your application calls a Relays alias. Relays owns the connection to your Ollama endpoint, applies the route policy, and hands back the provider response in the shape your SDK expects.
- Your application
Keeps the OpenAI-compatible request it already sends.
- Relays
Holds the key, picks the candidate, writes the receipt.
- Ollama
Receives the call on its own base URL.
- OpenAI-compatible
- Chat Completions
- No upstream key by default
http://localhost:11434/v1- Maintained Relays preset
Relays’ Ollama preset targets the local OpenAI-compatible endpoint with no upstream authentication by default. Override the registry when your deployment uses a remote host or credential.
What is measured, and what is not.
Availability comes from Ollama. Latency, error rate, and cost per successful request come from your own traffic, so Relays leaves them empty until requests run.
Relays measurements
No sample yet
Time to first token, error rate, and cost per successful request are read from requests that ran through Relays. This route has none, so there is nothing to plot.
Models at the edge.
Model IDs sit behind a Relays alias, so a catalogue change at Ollama never reaches your code.
Catalogue not connected
Relays has not published a Ollama model list on this page. Route candidates are still set by model ID in your route configuration.
Every route carries a policy.
A route is a list of candidates, a budget, and a record of what happened. You set all three before any traffic runs.
Candidates stay inside the contract.
Ollama can be a local-first or fallback candidate in an explicit Chat Completions route, provided the request is compatible with the selected model and endpoint.
See how a route is chosenA ceiling on this route.
Set an alert threshold and a stop threshold for the route rather than for the whole application. Relays checks both before the call goes upstream.
Each attempt is written down.
Every call records the alias, the candidates tried, the status each returned, tokens in and out, and the estimated cost of the attempt that served it.
Read a route receipt
One endpoint is enough to start.
Keep the client you already wrote. Bring us the workload and we will map the first Ollama route with you.