Skip to content

Blog

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.

DeepSeek V4 Pro Is GA: 1.6T Parameters, 1M Context, and a Price Hike Coming

DeepSeek released the production version of its flagship model this week. Build 0813 ended a preview window that ran nearly four months (Unite.AI). The company formally announced the release on August 13, 2026 (Reuters). DeepSeek models already power the AI chat features on this site. The family’s flagship is now a stable production target.

Calls to the deepseek-v4-pro endpoint now route to the GA build automatically. The endpoint name did not change (AI/TLDR). DeepSeek says the new build “greatly enhances agent capabilities” and is available through the API, the app, and the web (Reuters). The build appeared on OpenRouter’s model page on August 12 (Unite.AI; OpenRouter). API users spotted the swap in the system_fingerprint field, which now returns fp_v4pro_20260812 (r/DeepSeek).

SpecValue
BuildDeepSeek-V4-Pro-0813 (GA, August 12, 2026)
ArchitectureMixture of experts, 1.6 trillion total parameters
Active parameters per tokenAbout 49 billion
Context window1 million tokens
Max output384,000 tokens
AttentionCompressed Sparse Attention + Heavily Compressed Attention
Thinking modesnon-think, think high, think max
Pretraining dataMore than 32 trillion tokens

Sources: GMICloud, Apidog, MindStudio.

The attention design cuts inference cost hard. DeepSeek reports the V4 line runs at 27% of the single-token compute and 10% of the KV cache of V3.2 (Apidog). Long-context workloads are the target, not the edge case.

ItemPrice per million tokens
Input, cache miss$0.435
Input, cache hit$0.003625 (about 120x less)
Output$0.87

Caching is automatic. There is no parameter to enable it (AIHubMix). Teams that reuse long prefixes, like system prompts or document chunks, get the cache-hit rate on every repeated token (Apidog). Concurrency is capped at 500 requests for Pro, versus 2,500 for Flash (GMICloud).

The price holds for now. It will not hold for long. DeepSeek’s pricing page warns that “a significant increase” is coming soon (AI/TLDR). Reuters confirms DeepSeek will raise API pricing for V4 Pro and V4 Flash and introduce peak and off-peak pricing (Reuters).

DeepSeek shipped the family in three steps.

  1. April 24, 2026: the V4 series previewed with open weights for Pro and Flash under the MIT license (Unite.AI).
  2. July 31, 2026: V4-Flash went official first. Flash runs about 300B total parameters with roughly 13B active per token, at $0.14 input and $0.28 output per million tokens (Apidog; Yotta Labs).
  3. August 12, 2026: the Pro flagship went GA as build 0813 (GMICloud).

The order was deliberate. When Flash went official, DeepSeek published agent-benchmark results showing the re-trained small model outscoring the preview Pro on internal coding-agent suites (Unite.AI). Flash became the default agent workload model. The 0813 build is the flagship’s answer.

The V4 series is trained for agentic work: coding assistants, multi-step automation, and long-document synthesis (Unite.AI). The price gap to the frontier is the headline. V4 Pro runs about $0.435 in and $0.87 out per million tokens, against roughly $10.50 per million tokens for Gemini 3 Pro (MindStudio). That is a 50 to 60 times spread on the same class of agentic tasks (MindStudio).

Benchmarks back the value claim. Official scores put V4 Pro on top of Cybergym (83.3) and a terminal automation benchmark (31.8), with a modest gap to leaders on HLE and NL2Repo (MindStudio). Independent testing on a custom coding and agentic benchmark measured 76.25%, up from the preview’s 24.8% (MindStudio).

Integration is a one-line change for most stacks. The API is OpenAI-compatible, so the openai SDK works with model="deepseek-v4-pro" (Apidog). Anthropic Messages format and DeepSeek’s own Responses API also work (Apidog). Thinking modes return a reasoning_content field alongside the answer (Apidog).

One open item: weights. Hugging Face still hosts the April preview builds. DeepSeek has not announced a timeline for publishing the 0813 weights (Unite.AI). The stated cadence for the V4 line runs through the API first.

  1. Track the build, not the endpoint name. deepseek-v4-pro moved from preview to GA with zero code change on your side. If you need reproducibility, log the system_fingerprint so you know which snapshot served a response.
  2. Structure prompts for cache hits. Keep system prompts and document prefixes stable. The 120x cache gap decides whether this model is cheap or not (Apidog).
  3. Budget for the hike now. The increase is announced, with peak and off-peak pricing to follow (Reuters). Model your cost at 1.5x to 2x the current rate.
  4. Match the model to the load. Flash carries high-throughput traffic at 2,500 concurrent requests (GMICloud). Pro earns its 500-cap on long-context reasoning and heavy agent loops.
  5. Do not wait on self-hosting. The 0813 weights are not published. If you need open weights today, the April previews are what exists (Unite.AI).

This continues the cost story from our post on routing cloud AI instead of burning it. The economics just got sharper: a frontier-class agent model at cache-hit prices is now a default, not a bargain.

The 40-Minute Supply Chain Attack That Exposed 434,000 CI/CD Pipelines

The malicious packages behind the largest AI supply chain breach of 2026 survived on PyPI for only 40 minutes (TechJuice). The fallout is still being counted. On August 11, threat intelligence firm CloudSEK published a report linking more than 2,500 organizations and roughly 434,000 software pipelines to the compromise of LiteLLM (CloudSEK via PR Newswire). Independent analysis from Hudson Rock confirmed the scale the next day (Hudson Rock).

LiteLLM is an open-source proxy that gives applications a single API for many large language model providers (CyberInsider). Teams run it as the gateway between their code and models from OpenAI, Anthropic, and others. The library is downloaded more than 95 million times per month (CyberInsider). That reach is why it became a target. An environment running LiteLLM holds API keys, cloud credentials, and configuration files by design.

The attack did not start with LiteLLM. It started with Trivy, the open-source vulnerability scanner (Hudson Rock). TeamPCP, the group behind the campaign, first compromised Trivy’s GitHub Actions pipeline (CyberInsider). The group used an automation token that was rotated but never fully revoked. That gap gave them a 20-day window to force-push malicious code over Trivy’s version tags (TechJuice).

LiteLLM’s own CI pipeline used Trivy to scan its builds. The poisoned scanner had legitimate read access to the build runner. The attackers used that access to exfiltrate LiteLLM’s PyPI publishing tokens (Hudson Rock). With those tokens they published two poisoned releases, versions 1.82.7 and 1.82.8, to PyPI (CyberInsider). The malicious packages were pulled after about 40 minutes (TechJuice). Version 1.82.6 was the last clean release (Endor Labs).

The injection was small and surgical. Twelve lines of obfuscated code were added to a single file, litellm/proxy/proxy_server.py, during the wheel build (CyberInsider). The code decoded a base64 payload and launched it through a Python subprocess when the module was imported. Version 1.82.8 escalated the attack. It added a .pth startup file that runs the payload every time Python starts, even when LiteLLM is never imported (CyberInsider).

The payload harvests a wide credential set. It grabs SSH keys, AWS, GCP and Azure credentials, Kubernetes secrets, environment files, database configurations, and cryptocurrency wallets (CyberInsider). Stolen data is encrypted, packed into a file named tpcp.tar.gz, and exfiltrated to an attacker-controlled domain (CyberInsider). When that path fails, the malware creates a public repository in the victim’s own GitHub account. It uploads the stolen data as a release asset (TechJuice). The payload also moves laterally in Kubernetes. It deploys privileged pods that mount the host filesystem and install a persistent backdoor registered as a systemd service named “System Telemetry Service” (CyberInsider).

CloudSEK identified more than 2,500 organizations potentially impacted. The list spans technology, finance, telecom, cybersecurity, manufacturing, and logistics (CloudSEK via PR Newswire). Hudson Rock obtained a 153GB archive of the stolen data containing 433,909 files. It attributed 118,829 CI runner dumps to 2,488 corporate domains (Hudson Rock). Named victims include NVIDIA, Samsung Electronics, Cisco Systems, Siemens, S&P Global, ServiceNow, and Deloitte (Unite.AI). The trace also surfaced Boeing, Orange, and Roku (TechJuice). The exposed material covers AWS secrets, GitLab identities, Salesforce credentials, Slack tokens, Azure secrets, SSH keys, and AI provider API keys (TechJuice).

An AI gateway is the richest credential store in a modern stack. Every LLM provider key, cloud secret, and pipeline token flows through it. A single poisoned release in that position turns months of build history into an attacker’s keychain. The 40-minute window on PyPI is the core lesson: exposure time no longer measures damage. The packages were published in March 2026, yet organizations are only learning of their exposure in August (Unite.AI).

  1. Revoke, do not just rotate. The entry token was rotated but never revoked (TechJuice). Rotation leaves the old credential alive. Revocation kills it.
  2. Pin with hashes. A lockfile with integrity hashes blocks a malicious release from installing, even when it reaches the index. This is the single cheapest control in the chain.
  3. Separate publish access from build access. The scanner that reads your repo should not also hold your package-publishing tokens (Hudson Rock).
  4. Audit secrets continuously. Environment variables leak into runner dumps and public repos (TechJuice). Scan for them on every run, not once a quarter.
  5. If you ran LiteLLM 1.82.7 or 1.82.8, act now. Treat every credential in that environment as compromised and rotate them. The malware targeted .aws/credentials and .kube/config specifically (TechJuice).

The pattern is familiar to anyone who read our breakdown of credential theft through AI developer tools. The tool that has access becomes the target. The LiteLLM breach just proved it at the scale of the entire AI build ecosystem.

Power Is the New Cloud: Inside Anthropic's $9.1B Data Center Deal with a Bitcoin Miner

On August 10, bitcoin miner Riot Platforms disclosed a 20-year data center lease with a leading frontier AI lab (Riot Platforms, 2026). The deal covers 191 megawatts of critical IT capacity at Riot’s Rockdale, Texas campus (CNBC, 2026). Bloomberg identified the tenant as Anthropic, citing people familiar with the matter (The Decoder, 2026). Neither company confirmed the name publicly. Riot declined to comment, and Anthropic did not respond (crypto.news, 2026).

The contract is expected to generate roughly $9.1 billion in revenue over the initial term, which runs through June 2048 (Riot Platforms, 2026). Two five-year extension options could push the total value to about $16.1 billion (CNBC, 2026). Riot shares jumped roughly 25% in after-hours trading once the deal’s size became public (Quartz, 2026).

This is a colocation agreement, not a cloud contract. Riot builds the data center to the tenant’s specifications and provides the building, power connections, cooling, and operations (The Decoder, 2026). The tenant brings its own servers and AI chips (MLQ, 2026). The 191 MW is enough power for roughly 143,000 homes, per Bloomberg (The Decoder, 2026).

Delivery is phased. The first 96 megawatts go live in December 2027. The full 191 megawatts arrive by June 2028 (Riot Platforms, 2026).

TermDetail
Term length20 years, through June 2048
Capacity191 MW critical IT at Rockdale, Texas
Phase 196 MW by December 2027
Phase 2Full 191 MW by June 2028
Base contract value~$9.1 billion
With both extensions~$16.1 billion
Interim financing$573 million from Morgan Stanley
Riot providesBuilding, power connections, cooling, operations
Tenant providesServers and AI chips

Terms via Riot’s Q2 2026 release. Morgan Stanley’s $573 million interim facility funds initial development while an investment-grade credit backstop is finalized (Quartz, 2026).

Why a bitcoin miner is suddenly a data center developer

Section titled “Why a bitcoin miner is suddenly a data center developer”

Riot is one of the world’s largest bitcoin miners and has owned its power assets for years (Data Center Dynamics, 2026). It controls more than 1,100 acres and 1.7 GW of power capacity across two Texas facilities (Data Center Dynamics, 2026).

The pivot began in January 2026 with Advanced Micro Devices. Riot signed a lease for an initial 25 MW, which it delivered on time and on budget, and a second 25 MW expansion is under construction (Riot Platforms, 2026). That AMD agreement can expand to a total of 200 MW at the campus (Data Center Dynamics, 2026).

The two leases give Riot 241 MW of contracted capacity and about $9.8 billion in long-term contracted revenue (Riot Platforms, 2026). CEO Jason Les called the lease “a defining moment in our evolution into a leading developer of large-scale data centers” (Riot Platforms, 2026).

The financials show the transition in progress. Q2 2026 revenue was $174.2 million, up 14% year over year, with data center revenue of $23.2 million (Riot Platforms, 2026). Riot still posted a net loss of $237.2 million for the quarter (Quartz, 2026). Miners across the sector are chasing the same pivot. Shares of peers IREN, Applied Digital, and TeraWulf moved higher on the news (Yahoo Finance, 2026).

The deal gives Anthropic access to scarce, grid-connected power (CNBC, 2026). Miner campuses already own the hard part of the stack: land, substations, and interconnection rights. A frontier lab cannot wait years for a utility build.

Rockdale is one piece of a much larger Anthropic portfolio. The company is paying SpaceX an estimated $1.25 billion per month through May 2029 for the Colossus 1 data center and plans to deploy two gigawatts of AMD GPUs (The Decoder, 2026). Amazon is investing up to $25 billion toward up to five gigawatts of Trainium capacity (The Decoder, 2026). Gigawatts of Google and Broadcom TPU capacity come online starting in 2027, and a six-year, $10 billion contract with Volta Infra rounds out the portfolio (The Decoder, 2026). Bloomberg also reported a nearly $45 billion compute commitment to xAI in May (Quartz, 2026).

  • Power, not chips, now gates AI capacity. The scarce resource in this deal is 191 MW of interconnected electricity, not GPUs (CNBC, 2026). Capacity planning starts at the substation, not the rack.
  • Colo economics are the new frontier. The landlord supplies shell, power, cooling, and operations. The tenant owns the compute (MLQ, 2026). Budget for hardware separately from facilities.
  • Capacity lands in waves. 96 MW arrives in December 2027, and the rest lands six months later (Riot Platforms, 2026). Plan deployment as two campaigns, not one.
  • Watch the miners. Bitcoin miners hold the interconnected power the AI buildout needs, and they are monetizing it as landlords (Data Center Dynamics, 2026).

You Don't Need Cloud AI for Everything. Route It Instead of Burning It.

Your company is paying $25 per million output tokens for a model that answers the same question 10,000 times a month. The answer never changes. The bill does.

Wendell of Level1Techs made the full case in You Don’t need to use Cloud AI! Switchyard and Nemotron 3.5 Lightning. The argument is blunt: frontier inference for every task is setting money on fire. The fix is a local model router with a feedback loop. NVIDIA shipped both halves this month.

The trap is not just the token price. The trap is turning judgment over to the model.

When a company buys a frontier subscription and turns it loose, it loses the ability to answer three questions. What did the AI do? Why did it take that step? What information did it use? Without those answers, a failure teaches nobody anything (Level1Techs, 2026).

Software engineers want labor augmentation, not delegation. They want supervision. They want structure. They want to know what problem they are solving. A router that logs every decision gives them that. A blank chat window does not.

Switchyard is NVIDIA’s open-source supervision architecture for routing user requests across AI models (NVIDIA Developer Blog).

A request arrives. The router sends it to a specialized local worker, a small model, a customized model, or a tool-calling agent. Each step produces an observable trace. The router accepts the result or escalates it to a stronger model. Human supervision is a first-class component, not an afterthought.

The design gives you three concrete advantages:

AdvantageWhat it buys you
CostA $5-per-million-token local model handles what Opus-class models were doing at $25
ObservabilityYou know which component did what, where, in your organization
Organizational learningEvery routing decision and escalation becomes a dataset

That dataset is the real prize. It shows how your people actually use AI, where they get stuck, and which workflows repeat. It is institutional knowledge, not telemetry (Level1Techs, 2026).

Nemotron 3.5 Lightning: built to be customized

Section titled “Nemotron 3.5 Lightning: built to be customized”

Nemotron 3.5 Lightning is a 30-billion-parameter mixture-of-experts model with 3 billion active parameters (NVIDIA NIM model card). It is fast, it is local, and it is explicitly pitched as a model you are supposed to customize (NVIDIA Developer Blog).

Customization does not mean full retraining. NVIDIA ships the LoRA recipes, the supervised fine-tuning setup, the reinforcement learning config, and the training data. You freeze the base model and train a small set of additional weights for your specific job.

NIM takes it one step further. It keeps one base model resident and dynamically loads and unloads LoRA adapters while serving (NVIDIA Developer Blog).

Accounting gets the accounting adapter. Software engineering gets the code-review adapter. Support gets the support adapter. That undocumented internal product from 2017 gets the adapter containing the dark knowledge known only to Gary. Gary can finally take a vacation.

One base model, many specialists, no retraining, no cloud round-trips.

NVIDIA’s data flywheel blueprint makes the loop explicit (NVIDIA Developer Blog):

  1. Instrument the AI application and log production traffic.
  2. Build evaluation and fine-tuning datasets from those logs.
  3. Evaluate smaller models against the data.
  4. Customize the ones that work.
  5. Promote them and measure again.

You cannot improve what you do not measure. The flywheel saves tokens because the small local model is cheaper on every request. It saves sanity because every escalation is a recorded decision, not a guess.

The benchmark backs it up. On Humanity’s Last Exam, an NVIDIA-orchestrated system scored 37.1% versus 35.1% for GPT-5, at 30% of the cost and 2.5 times faster (Artificial Analysis, Wikipedia). The small model beat the frontier model at the task because it was inside a tool-calling ecosystem, not because it tried to know everything.

Wendell’s sharpest observation is the dark pattern. Recent Codex CLI updates surface less reasoning detail in the UI, and there are open issues about reasoning summaries missing from the session log (Level1Techs, 2026).

High-quality outputs and task traces are exactly the raw material you need to train a cheaper specialized model. OpenAI even sells model distillation around that idea. There is an economic incentive for frontier providers to keep useful internal signals from being trivially exportable.

That is the argument for owning your loop. The company that routes and logs its own AI traffic stops renting intelligence and starts accumulating it.

  1. Route by task class. Send simple, repeated tasks to a small local model. Send only the hard edge cases to the frontier.
  2. Capture every decision. Log what the model did, why, and what the human corrected. That log is your training data.
  3. Customize what repeats. If users ask the same question 10,000 times, give the small model a LoRA adapter that answers it from your own data.

The era of using a frontier model for every little task is ending. The high water mark for cloud token spend is here. The machines that replace it are smaller than you think, and they sit on a desk.