rankun203/llm-proxy

llm-proxy-ondemand is a lightweight intermediary that sits in front of a vLLM server (a system for running large language models) and ensures the heavy model only runs when someone actually needs it. Instead of keeping a memory-hungry model loaded and waiting around the clock, the proxy starts the model the moment the first request comes in, and shuts it down again after a period of inactivity. This saves compute resources, which is especially valuable in environments where GPUs are scarce or expensive. Here's how it works at a high level. When you start the proxy, it immediately opens a web server that speaks the same API language as OpenAI. Any application can send standard chat or completion requests to it. The first time a request arrives, the proxy launches the actual model server, waits for it to be ready, and then forwards the request. Subsequent requests pass straight through. After a configurable idle period (thirty minutes by default), the proxy kills the model server. The next request triggers another startup automatically. The primary audience is researchers or engineers running language models on shared computing clusters. For example, if you have access to a university or lab SLURM cluster (a job scheduler for shared computing resources), you can use this proxy to request a GPU node, launch the model there, and tunnel the connection back to your local machine, all triggered automatically when a request arrives. This means a teammate's script can point at a familiar API endpoint, and the expensive GPU only spins up for the duration of the actual work. One notable aspect is how it handles networking in cluster environments. When running on a remote compute node, the proxy sets up a reverse SSH tunnel, creating a bridge so requests from your local machine reach the model running on the cluster. This requires passwordless SSH access to be pre-configured, and the README notes that SSH credential issues can be tricky to debug. The tradeoff is that once configured, the complexity is invisible to the end application, which just sees a standard, always-available API.