Arize Phoenix OSS is MIT-licensed, free, unlimited. One Docker command to full observability. When you’re ready for production-grade monitoring, alerting, and enterprise controls, Arize AX picks up exactly where Phoenix leaves off. One company. One roadmap. Built for agents.
Same open-source DNA.
Different trajectory.
Open source that grows with you.
Open source, new ownership.
Langfuse built a strong open-source community and a solid tracing foundation. Then ClickHouse acquired them before they closed their Series A. The team is talented, the tooling is real, but the roadmap now belongs to a database company, and database companies optimize for what sells databases.
What AI builders are saying
from field interviews
We were hitting tooling gaps with Langfuse. Limited visibility into what was happening, too much manual debugging. We needed to see the full picture without stitching logs together ourselves.
Langfuse worked fine early on, but we kept hearing from other teams that hit walls at scale. Arize’s database architecture is built for enterprise volume. That mattered when we started planning for production traffic.
We have regulatory requirements and needed real SLAs. Langfuse’s support terms didn’t meet our bar. When you’re in a regulated industry, a 30-day SLA isn’t going to cut it.
Where the architecture diverges
Open source is the starting line, not the finish
Whose roadmap is it?
ClickHouse acquired Langfuse before the team closed their Series A. The stated rationale is infrastructure alignment – Langfuse v3 already runs on ClickHouse.
But infrastructure alignment means product priorities follow database strategy, not AI observability strategy. Arize is an independent AI company. Our roadmap is set by what AI engineering teams need, not what sells more database seats.
General-purpose OLAP vs. purpose-built AI
ClickHouse is a strong analytics engine. It was designed for logs, metrics, and columnar queries at scale.
AI observability is a different problem – embeddings, agent decision trees, eval telemetry with high cardinality across sessions, spans, and tool calls. Arize built adb for exactly this workload. Purpose-built beats repurposed when your agents are in production.
From open source to enterprise - without switching vendors
Phoenix is MIT-licensed, free, unlimited. One Docker command. When you need production monitoring with automated alerting, SSO/RBAC, SOC 2 compliance, and Alyx – you upgrade to AX. Same platform, same data, same team.
Langfuse’s upgrade path now routes through ClickHouse’s enterprise sales motion. Different incentives, different priorities.
Open source shouldn't mean ops burden
Langfuse self-hosted requires Kubernetes, managed Postgres, Redis, S3, and a ClickHouse cluster. Teams report 40-80 hours of engineering setup and $3-4K/month in ongoing infrastructure costs. Docker Compose deployments lack HA and aren’t production-ready.
Phoenix runs with one Docker command. Arize AX handles the infrastructure so your team ships AI, not YAML.
When Langfuse is the right call
If you’re early-stage, self-hosting is a hard requirement, and you need basic tracing and prompt management to get started – Langfuse’s community and documentation are genuinely strong.
When your agents hit production and you need depth, scale, and a roadmap you can trust – we’ll be here.
Where the difference is most felt
Trillions of data points. No tradeoffs.
First trace to full production visibility
Find what you didn't know to look for
One deployment. Total control.
No ops burden
Predictable costs
Simpler operations
AI evolved from ML. So did we.
We’re Jason and Aparna.
We built the foundational ML infrastructure at Uber, Apple, and TubeMogul.
Before LLMs existed, we watched models break in production with nothing to fix them. So we started Arize to fix it.
Our mission since 2020: make AI work.
ML first. Then LLMs. We shipped the first open-source library for LLM evaluation: Phoenix.
Now agents.
That’s Arize AX — the Agent Experience.