[GH-ISSUE #152] Feature request: Model comparison table with cost, context window, and replacement recommendations #91

Closed
opened 2026-10-18 14:06:01 +00:00 by bsakaguchi · 1 comment
Owner

Originally created by @githb-ac on GitHub (Apr 24, 2026).
Original GitHub issue: https://github.com/open-webui/desktop/issues/152

Summary

When a user has multiple models configured across different providers in Open WebUI,
there is currently no single place to compare them side by side. Users have to
cross-reference provider pricing pages manually to make informed decisions about
which model to use for a given task.

Current behaviour

  • Models are listed in the model selector dropdown with no cost or capability metadata
  • There is no way to compare two or more models on price, context window, or
    performance characteristics from within the UI
  • Users running multiple providers (Anthropic, OpenRouter, Ollama, etc.) have no
    unified cost visibility

Proposed behaviour

Add a Model Health / Comparison table in Admin → Models showing all configured
models with the following columns:

Model Provider Input cost (per 1M tokens) Output cost (per 1M tokens) Context window Recommended alternative
  • Costs pulled from provider API metadata where available, or manually entered
  • "Recommended alternative" column suggests a cheaper or higher-performing
    model for the same task category
  • Sortable by cost, context window, or provider
  • Works across all configured providers including local Ollama models (shown as $0.00)

Why this matters

Users managing multiple models across providers spend significant time on external
sites comparing costs. A single in-UI table removes that friction and helps users
make faster, better-informed model-swap decisions.

Reference

A working visual prototype of this table is attached to this issue.

ticket-691-692-model-health-cost.html

Originally created by @githb-ac on GitHub (Apr 24, 2026). Original GitHub issue: https://github.com/open-webui/desktop/issues/152 ## Summary When a user has multiple models configured across different providers in Open WebUI, there is currently no single place to compare them side by side. Users have to cross-reference provider pricing pages manually to make informed decisions about which model to use for a given task. ## Current behaviour - Models are listed in the model selector dropdown with no cost or capability metadata - There is no way to compare two or more models on price, context window, or performance characteristics from within the UI - Users running multiple providers (Anthropic, OpenRouter, Ollama, etc.) have no unified cost visibility ## Proposed behaviour Add a Model Health / Comparison table in Admin → Models showing all configured models with the following columns: | Model | Provider | Input cost (per 1M tokens) | Output cost (per 1M tokens) | Context window | Recommended alternative | |---|---|---|---|---|---| - Costs pulled from provider API metadata where available, or manually entered - "Recommended alternative" column suggests a cheaper or higher-performing model for the same task category - Sortable by cost, context window, or provider - Works across all configured providers including local Ollama models (shown as $0.00) ## Why this matters Users managing multiple models across providers spend significant time on external sites comparing costs. A single in-UI table removes that friction and helps users make faster, better-informed model-swap decisions. ## Reference A working visual prototype of this table is attached to this issue. [ticket-691-692-model-health-cost.html](https://github.com/user-attachments/files/27063656/ticket-691-692-model-health-cost.html)
Author
Owner

@githb-ac commented on GitHub (Apr 24, 2026):

"Closing issue, posted to the wrong repo. Reposting to open-webui/open-webui."

<!-- gh-comment-id:4315600623 --> @githb-ac commented on GitHub (Apr 24, 2026): "Closing issue, posted to the wrong repo. Reposting to open-webui/open-webui."
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
open-webui/desktop#91
No description provided.