Skip to content

observability

1 post with the tag “observability”

Dynatrace Buys Arize for $915M: AI Evaluation Meets Production Observability

On August 13, 2026, Dynatrace signed a definitive agreement to acquire Arize for $915 million (Dynatrace). The deal joins AI evaluation, agent tracing, and production monitoring in one platform. At that price, it is a strong signal that AI observability is now a platform category, not a niche tool.

ItemDetail
BuyerDynatrace (NYSE: DT)
TargetArize, based in San Francisco
Total value$915 million, cash and stock
Cash portionAbout $815 million
BalanceReplacement equity awards for Arize employees
AnnouncedAugust 13, 2026
Expected closeThis quarter or early in Dynatrace’s Q3

Sources: Business Wire, Pulse 2.0.

Arize founders Jason Lopatecki and Aparna Dhinakaran join Dynatrace at closing. Lopatecki keeps leading the Arize team and reports to Dynatrace CEO Rick McConnell (Business Wire).

Arize builds observability for AI models, applications, and agents. Its tools detect hallucinations, measure output quality, and trace how AI systems behave (MSSP Alert). The platform is open-source native and works across the major AI frameworks and model providers (Engineering.com).

Its Phoenix tool gives developers a free evaluation harness. That is the entry point this deal wants. Engineers choose evaluation tooling while an app is still being written, months before an operations team sees it (Forbes).

Arize CEO Jason Lopatecki: “We founded Arize because AI teams needed a way to know their agents were actually working correctly, not just running” (Business Wire).

Dynatrace was not buying blind. Its AI Observability app traces gen_ai spans, scores live production responses with LLM-as-a-judge evaluators, and detects drift in those scores over time (Forbes). What it lacked was a foothold with the AI engineers who pick the evaluation harness. Those choices happen months before anything reaches operations (Forbes).

The purchase targets fragmentation. Teams evaluate models with one set of tools, then monitor production with another set. Dynatrace wants one loop: model and agent performance, application health, infrastructure data, and business outcomes in a single view, with production data feeding back into development (Engineering.com).

The financial math is public. Dynatrace projects the deal adds about 200 basis points to annual recurring revenue growth in fiscal 2027. It expects non-GAAP operating margin to drop about 175 basis points during integration (Pulse 2.0).

The move also answers the competitive field. Datadog and Splunk hold the neighboring ground in observability (Forbes). Dynatrace recently added Bindplane, an OpenTelemetry data collector, and DevCycle, a feature-flag company. Open standards are the throughline (Constellation Research).

The AI chat features on this site run on an OpenAI-compatible stack. The failure modes this deal targets, drift, output quality, and agent tracing, are the ones any AI workload hits in production.

  1. Run evaluation and production monitoring as one loop. Feed eval results into the same dashboards your SREs watch.
  2. Standardize on OpenTelemetry gen_ai spans. They are the common format that makes eval and production data comparable.
  3. Track hallucination rate and score drift as real SLOs, with owners and alert thresholds.
  4. Re-check your AI toolchain roadmap. Consolidation changes vendor plans, and the vendors you choose now decide whether evaluation and operations stay joined.

The deal closes this quarter or early next, subject to regulatory review (Dynatrace). If you run AI in production, the platforms you pick in the next six months will set the shape of your AI operations for years.