AIToday
Large Language ModelsAI Coding AssistantsOpen-Source AIHacker NewsPublished: Jul 24, 2026, 22:00 JST

llmproxy: Open-source Flask proxy routes local AI clients to NVIDIA cloud API

llmproxy: Open-source Flask proxy routes local AI clients to NVIDIA cloud API

3 Key Points

  1. What happened

    A developer released llmproxy, a lightweight Flask server that emulates the HTTP APIs of Ollama, OpenAI /v1, and llama.cpp, transparently forwarding all requests to NVIDIA's OpenAI-compatible API at integrate.api.nvidia.com/v1. The tool supports chat, completions, embeddings, streaming, multi-model discovery, optional authentication, automatic retries, response caching with configurable TTL and size, and a live /stats dashboard.

  2. Why it matters

    Any existing tool that speaks Ollama, OpenAI, or llama.cpp can now talk to NVIDIA-hosted models without client-side changes — you point the client at llmproxy instead of a local runtime. This bridges local and cloud AI providers seamlessly, enabling cost tracking and automatic failover for teams already invested in those client libraries.

  3. What to watch

    The project is open-source under the MIT License and published as a prebuilt Docker image on Docker Hub (lordraw/llmproxy), with Docker Compose deployment instructions and a test runner (scripts/tests.sh) included in the repository.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, in your inbox every morning.

Context & Analysis

llmproxy addresses a practical friction point: many AI tools and SDKs are written to speak Ollama, OpenAI, or llama.cpp protocols, but teams may want or need to use a different inference backend—in this case, NVIDIA's cloud API. Rather than forking or rewriting client code, the proxy sits in the middle as a protocol translator, intercepting requests in the client's native format and converting them to OpenAI format for NVIDIA. This is especially valuable for teams already invested in local-first development workflows or tools like Open WebUI that natively support those APIs.

The tool also bundles practical features: automatic retries shield against transient upstream failures, response caching reduces redundant API calls for identical queries, cost tracking through metrics visibility helps teams understand their NVIDIA spending, and inbound authentication gates who can use the proxy. The fact that it ships as a prebuilt Docker image (lordraw/llmproxy on Docker Hub) and includes Docker Compose configuration lowers the barrier to production deployment, making it accessible even to teams without deep DevOps experience.

FAQ
What APIs does llmproxy emulate?
llmproxy emulates the HTTP APIs of Ollama, OpenAI /v1, and llama.cpp's llama-server, forwarding all requests to NVIDIA's OpenAI-compatible API.
How do I deploy llmproxy?
You can run it locally or in Docker. The quickest start is to configure your NVIDIA API key in .env, then run `docker compose up -d` or use the prebuilt Docker Hub image lordraw/llmproxy:latest.
What features does llmproxy include?
It supports streaming, multi-model discovery, optional inbound authentication, automatic retries on transient errors, optional response caching with configurable TTL and size, and a live /stats metrics dashboard.

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleTeen skepticism of AI surges as kids dismiss hype