Dumpster Dyva

Host population

WorkersParallel hosts tried per request (fan-out). Timeout (s)Per-host request timeout in seconds. Hedge delay (s)How long the last-good host gets to respond before the rest of the pool is raced alongside it. Whoever answers first wins. 0 races everything at once. Keeps a dead-but-connected favourite from stalling the whole request. Minimum model countHide models served by fewer than this many hosts from the /api/tags and /v1/models listings that third-party apps read. 0 = show all. (The dashboard always shows everything.) Base pathServe dyva under a secret URL path instead of the root. A path like /some-path moves the dashboard to /some-path/ and the API to /some-path/v1/models — deterrence by obscurity: a scanner hitting the default paths (/v1/models, /api/tags) finds nothing. Blank = served at the root. Takes effect on restart (like the listen port); the --base flag overrides this.

Model list override Advertise a fixed list of model names from /api/tags and /v1/models instead of the discovered catalog, for tools that make you pick one specific model id. Every dyva model name is a routing pattern, so one entry like qwen3 covers every qwen3:* variant on every host. Upload a plain text file, one name per line; blank lines and #comments are ignored. Clear turns the override back off and goes back to advertising the real catalog. Names no host currently serves stay listed (count 0) so the menu can't shift under a tool that pinned one. Minimum model count doesn't apply to an explicit list.

Localhost onlyRestrict inference endpoints to localhost only (a remote host that reaches this port can't chat or generate). Equivalent to the ./dyva -l flag; saved here it persists across restarts. Explore modeDiscover more of the unknown network: route hosts we haven't visited (unknown state) to the front of the line, ahead of known-good ones. Deliberately slower — a request may probe cold hosts first — but it maps out the pool. Off by default. Caution: the unvisited frontier is where the canary honeypots live, and poking a burst of fresh IPs is exactly what trips Cloudflare/WAF reputation — so this raises the chance of a soft IP ban on your egress. Use it for deliberate survey passes, not routine routing.

CloudskipperNever route to — or even connect to — hosts on the ticked clouds. The soft-ban tripwire can fire on the TCP connection itself, so a skipped cloud's hosts are dropped from every request before any connection is made. Clouds are identified by enrichment; the list below is the ones most represented in the current survey. Applies to every source and is always in effect, independent of Explore mode.

Admin passwordProtect this Settings tab and its sources. When set, opening Settings requires this password — everything else (chat, models, the dashboard) stays public. Type a new value to set or change it; leave blank to keep the current one. Forgot it? Clear admin_pw in settings.json and restart.

Additional sources

Each source fetches a JSON list of host rows from its url and maps fields onto host entries. Configured sources are tried before the built-ins, so they win on duplicate hosts.

mapping — each target field is one of:

{"field": "x"} — copy row["x"] from the source row
{"value": 0} — a constant

Map a server (or url) so the host can be keyed; models should resolve to a list of strings. CSV / transform-heavy sources aren't supported here.

Example

[
  {
    "name": "my-list",
    "url": "https://example.com/hosts.json",
    "mapping": {
      "server":  {"field": "url"},
      "models":  {"field": "models"},
      "service": {"value": "ollama"}
    }
  }
]

Extra JSON host sources, fetched before the built-ins (highest priority). A JSON array of {name, url, mapping}.

Dumpster Dyva

Models

Hosts

Host

Hosts

Host population

Map & compare syntax