Registry › Compare › Neo vs Open WebUI

Neo vs Open WebUI

Both are Grade A and 4.8 points apart, so choose on what you weigh most. Neo leads on supply-chain integrity and transparency; Open WebUI leads on adoption and rests on broader evidence. Note: Neo's evidence coverage is thinner (coverage B vs A) — its score rests on fewer independent signal types.

A Neo 90.0

Neo.mjs is a self-evolving software organism: a professional end-to-end AI engineering team whose cross-model swarm inhabits live apps via Neural Link, Active Hybrid GraphRAG, DreamService, and self-healing loops.

neomjs/neo · #19 overall · #1 UI & App Builders · coverage B (3/5)

Choose Neo if supply-chain integrity and transparency matter most.

  • +2.1Safety / Integrity: 100% of recent commits signed, against 74%
  • +0.6Transparency: OSSF Scorecard 6.6 against 5.9
A Open WebUI 85.2

User-friendly AI Interface (Supports Ollama, OpenAI API, ...)

open-webui/open-webui · #81 overall · #3 UI & App Builders · coverage A (4/5)

Choose Open WebUI if adoption matters most.

  • +6.4Adoption: 324.4k weekly downloads against 5.2k
  • A vs BEvidence coverage: 4 of 5 independent signal types, against 3

Where they differ

20.7
Safety / IntegrityNeo +2.1
18.6
14.1
TransparencyNeo +0.6
13.5
13.4
AdoptionOpen WebUI +6.4
19.8
+3.9
Runtime calibrationNeo +8.5
-4.6

2 dimensions identical: Identity 18.0 · Maintenance 19.9 · Full evidence table

An independent, evidence-based trust comparison of Neo and Open WebUI, two UI & App Builders projects in the HVTracker registry. Scores come from public, checkable signals — supply-chain provenance, OSSF Scorecard, maintenance, and adoption — not popularity.

Full evidence

Signal Neoneomjs/neo Open WebUIopen-webui/open-webui
HVTrust score 90.0 85.2
Evidence grade A A
Coverage grade B A
Overall rank #19 #81
Rank in UI & App Builders #1 #3
GitHub stars 3.3k 153.5k
Last updated 1d ago 1d ago
Build provenance Yes Yes
OSSF Scorecard 6.6 / 10 5.9 / 10
License MIT NOASSERTION
Downloads 5k/wk 324k/wk
Trust dimensions (points earned)
Safety / integrity / 25 20.7 18.6
Identity & provenance / 18 18.0 18.0
Transparency / 17 14.1 13.5
Maintenance / 20 19.9 19.9
Adoption / 20 13.4 19.8
Runtime capability surface (full matrix)
MCP server Implemented —
External providers — 8 — Amazon Bedrock, Anthropic, OpenAI, …
Requires API keys No Yes
Plugin surface plugins —
Provenance drift Match Unknown
Open in the live compare tool → Neo profile Open WebUI profile More UI & App Builders →

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption, scaled by an evidence-confidence factor. Grade bands: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Signals refresh daily. Full methodology v4.3 →