npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@opennodes/ollama-router

v0.1.2

Published

OpenNodes for Ollama: one Ollama-compatible endpoint across your local models, LAN machines (auto-discovered), and verified public nodes from the OpenNodes registry — with advisor routing (auto, auto-cheap, auto-private) and signed receipts for public cal

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

saikou.soshitesaikou.soshite

Keywords

ollamaopennodesonprouterload-balancerlanlocal-llmopen-webuimcpai

Readme

OpenNodes for Ollama

One Ollama-compatible endpoint for your local models, your other machines, and verified public nodes — so Open WebUI, Continue, Zed, JetBrains AI, Msty, Enchanted, Raycast, and anything else that speaks Ollama gains three tiers behind one model list, without changing a line.

npx @opennodes/ollama-router                  # local Ollama + LAN peers + public nodes from registry.opennodes.io
npx @opennodes/ollama-router --registry none  # LAN-only: nothing leaves your network

Then set OLLAMA_HOST=127.0.0.1:11435 in your app.

| Tier | Models come from | Name | Cost | |---|---|---|---| | local | your own Ollama (http://127.0.0.1:11434) | llama3.1:8b | — | | lan | other machines: plain Ollama servers or ONP Node Kit nodes, via --peer or mDNS | lan/gpubox/llama3.1:70b | — | | public | the OpenNodes registry — verified providers, disclosed hardware, measured latency, pinned prices | onp/org.example.lab/qwen3-235b | signed receipt per call, budget cap |

Plus the advisor models, routed per request from the prompt's features (which never leave this machine): auto · auto-cheap · auto-fast · auto-quality · auto-private (only local and LAN — nothing leaves your network).

What it does: Ollama native API (/api/tags, /api/chat, /api/generate, /api/show, /api/ps, embeddings and model management passed to local) with streaming translation for public nodes; OpenAI /v1 alongside; a bare model name that isn't local falls through to a LAN copy; public calls are pinned to a card revision, receipted, verified (amount = usage × pinned price), and capped by --max-request-usd. Introspection: /router/catalog, /router/advice, /router/receipts.

Options: --port, --ollama <url>, --peer <origin> (repeatable), --registry <url>, --min-tier community|verified, --max-request-usd 0.05, --region eu, --key host=token (BYOK for imported catalogs), --ledger file.jsonl, --no-mdns, --public-bind (listen on all interfaces for other LAN machines).

Publish your machine as a node so the rest of your LAN (or the world) can discover it: pipx install onp-node && onp-node init --engine http://127.0.0.1:11434/v1 --id org.example.mybox --public-url http://<lan-ip>:8800 && onp-node serve --mdns.

Part of OpenNodes · Apache-2.0.