RAGFlow
RAGFlow's dev builds settle permission ownership while the rest is migrations and test plumbing.
A side-by-side editorial comparison of Arize Phoenix and LiteLLM — release velocity, themes, recent moves, and the top alternatives to consider.
Phoenix evals pins out a compromised LiteLLM release and the emSign root.
Arize Phoenix is shipping near-daily releases across its server, Python evals and TypeScript packages. The past week was mostly fixes and dependency hygiene: evals 3.9.3 excluded the compromised LiteLLM 1.107.0 and required a certifi build that distrusts the emSign root, and later patches refreshed playground presets and evals kwargs handling. Server 20.25 and 20.26 mainly carried the team's internal issue-to-PR agent tooling, plus a service.version attribute on Phoenix's own OpenTelemetry resource.
LiteLLM's 1.109 dev build stacks 704 PRs and 15 required config changes.
LiteLLM is patching four stable lines (1.103 to 1.106) in lockstep, most recently with leaner failure logs, a proxy-level GCS logger config and a new cosign signing key. On Oct 28 it opened a 1.109.0 dev line with 704 merged PRs and 15 items flagged as action required. Those include a new image-verification key, Gemini 3.6 Flash rejecting temperature/top_p/top_k, no more local token-count estimates, and budget edits on keys restricted to admins.
Arize Phoenix is shipping near-daily releases across its server, Python evals and TypeScript packages. The past week was mostly fixes and dependency hygiene: evals 3.9.3 excluded the compromised LiteLLM 1.107.0 and required a certifi build that distrusts the emSign root, and later patches refreshed playground presets and evals kwargs handling. Server 20.25 and 20.26 mainly carried the team's internal issue-to-PR agent tooling, plus a service.version attribute on Phoenix's own OpenTelemetry resource.
Phoenix keeps widening tracing coverage through integration pages (Pipecat, Microsoft Agent Framework) and its TypeScript evals, which now run classifiers on AI SDK decision models. The core product sees small, frequent fixes rather than large features right now, and supply-chain pinning has become part of the release routine.
The TypeScript decision-model support is pinned to experimental AI SDK versions, so expect follow-up patches as that API changes.
LiteLLM is patching four stable lines (1.103 to 1.106) in lockstep, most recently with leaner failure logs, a proxy-level GCS logger config and a new cosign signing key. On Oct 28 it opened a 1.109.0 dev line with 704 merged PRs and 15 items flagged as action required. Those include a new image-verification key, Gemini 3.6 Flash rejecting temperature/top_p/top_k, no more local token-count estimates, and budget edits on keys restricted to admins.
The stable lines get hardening and backports, while the next minor is moving the gateway toward stricter defaults: tighter key and budget permissions, explicit max_tokens for unmapped Anthropic models, and provider-side token counting. The size of the action-required list means upgrades are turning into real migrations for self-hosters.
Expect more 1.109 dev and rc builds that trim or document the breaking list before a stable 1.109.0, while the 1.103 to 1.106 lines keep getting matching patches.
Other ai-ml-platforms products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Arize Phoenix or LiteLLM.
RAGFlow's dev builds settle permission ownership while the rest is migrations and test plumbing.
AnythingLLM's Docker image can now run models itself, no Ollama or LM Studio required.
MLflow 3.17.2 records dataset, scorer and agent lineage on every GenAI evaluation run.
Kubeflow's main repo is now a signpost: real releases live in seven subprojects.
Label Studio's only tracked signal is a nightly build toward 1.24.
Mem0 is teaching coding agents to search memory less and trust it more.
See all Arize Phoenix alternatives → · See all LiteLLM alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — supply-chain security — within ai-ml-platforms. Arize Phoenix and LiteLLM are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Arize Phoenix and LiteLLM are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other ai-ml-platforms products to evaluate alongside.
Top Arize Phoenix alternatives in ai-ml-platforms are ranked by recent ship velocity. Browse the "Arize Phoenix alternatives" section above for the current picks, or visit /alternatives/arize-phoenix for the full list with editorial commentary on each.
Top LiteLLM alternatives in ai-ml-platforms are ranked by recent ship velocity. Browse the "LiteLLM alternatives" section above for the current picks, or visit /alternatives/litellm for the full list with editorial commentary on each.