Registry › Compare › Arize Phoenix vs OpenLLMetry

Arize Phoenix vs OpenLLMetry

OpenLLMetry leads on trust: 84.2/100 (Grade A) against 76.9/100 (Grade B), a 7.3-point gap. Arize Phoenix leads on maintenance and rests on broader evidence; OpenLLMetry leads on supply-chain integrity and transparency. Note: OpenLLMetry's evidence coverage is thinner (coverage B vs A) — its score rests on fewer independent signal types.

B Arize Phoenix 76.9

AI Observability & Evaluation

Arize-AI/phoenix · #236 overall · #8 Observability & Evaluation · coverage A (4/5)

Choose Arize Phoenix if maintenance matters most.

  • +6.1Maintenance: last push today, against 1d ago
  • A vs BEvidence coverage: 4 of 5 independent signal types, against 3
A OpenLLMetry 84.2

Open-source observability for your GenAI or LLM application, based on OpenTelemetry

traceloop/openllmetry · #114 overall · #5 Observability & Evaluation · coverage B (3/5)

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

  • +7.0Safety / Integrity
  • +5.4Transparency

Where they differ

12.5
Safety / IntegrityOpenLLMetry +7.0
19.5
8.5
TransparencyOpenLLMetry +5.4
13.9
20.0
MaintenanceArize Phoenix +6.1
13.9
16.7
AdoptionOpenLLMetry +0.1
16.8
+1.2
Runtime calibrationOpenLLMetry +0.9
+2.1

1 dimension identical: Identity 18.0 · Full evidence table

An independent, evidence-based trust comparison of Arize Phoenix and OpenLLMetry, two Observability & Evaluation projects in the HVTracker registry. Scores come from public, checkable signals — supply-chain provenance, OSSF Scorecard, maintenance, and adoption — not popularity.

Full evidence

Signal Arize PhoenixArize-AI/phoenix OpenLLMetrytraceloop/openllmetry
HVTrust score 76.9 84.2
Evidence grade B A
Coverage grade A B
Overall rank #236 #114
Rank in Observability & Evaluation #8 #5
GitHub stars 12.2k 7.5k
Last updated today 1d ago
Build provenance Yes Yes
OSSF Scorecard — 6.3 / 10
License NOASSERTION Apache-2.0
Downloads 137k/wk 449k/wk
Trust dimensions (points earned)
Safety / integrity / 25 12.5 19.5
Identity & provenance / 18 18.0 18.0
Transparency / 17 8.5 13.9
Maintenance / 20 20.0 13.9
Adoption / 20 16.7 16.8
Runtime capability surface (full matrix)
MCP server Implemented Implemented
External providers 6 — Amazon Bedrock, Anthropic, E2B, … 9 — Amazon Bedrock, Anthropic, Cohere, …
Requires API keys No No
Plugin surface plugins —
Provenance drift Partial Match
Open in the live compare tool → Arize Phoenix profile OpenLLMetry profile More Observability & Evaluation →

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.4 →