Find published research by company, product, platform or technology.
Showing 21–40 of 144 dossiers
The previously reported Stripe–OpenRouter deal is now official. The companies have announced an acquisition agreement, removing the dossier’s main uncertainty; the next questions are closing, product independence, pricing and how deeply Stripe integrates token routing with billing.
Bing’s AI Performance reporting now shows not just whether a site is cited in AI answers, but how its visibility breaks down by query intent, topic and citation share over time.
Search Console’s new generative-AI reports separate AI-feature impressions from overall search performance, exposing pages, countries, devices and time trends for AI Overviews, AI Mode and Discover.
Google Ads has changed a long-standing edge case in automated bidding: budget-constrained campaigns now aim more consistently at their configured target instead of sometimes materially overachieving it.
The August 20 tagging overhaul collapses Google’s lightweight tag and GTM into one platform, changing how marketers manage measurement code without requiring existing Google tags to behave differently on-page.
Node.js shipped v22.23.2, v24.18.1 and v26.5.1 to close a set of runtime vulnerabilities including an HTTP/2 use-after-free and a Permission Model path-matching bug that can over-grant filesystem access.
Supabase’s self-hosted stack now routes through Envoy by default, bringing new API-key support and hardened gateway defaults while breaking some Kong-specific assumptions.
Gemini API Managed Agents now combine Gemini 3.7 Flash by default with environment hooks, token budgets, scheduled triggers and persistent sandboxes — a much more production-shaped agent runtime.
Google must build Prebid integrations, let rival publisher ad servers receive real-time AdX bids, make publisher data portable and stop preferential AdWords bidding under a six-year court-supervised remedy.
WebMCP has crossed from a browser experiment into usable platform integration: ChatGPT’s built-in browser discovers site tools, Chrome exposes the proposed standard experimentally, and WordPress Playground now bridges plugin-defined tools from embedded WordPress into that agent-facing layer.
The change turns cache poisoning from mostly a workflow-design warning into an enforceable permission boundary. Teams can let untrusted jobs restore caches without writing them, prevent reusable workflows from escalating cache access and isolate jobs that only need to publish cache entries.
This is a platform migration with a real rewrite boundary. Existing HTML games need to be rebuilt through Unity, Cocos or Laya, then have login, ads, purchases and other TikTok capabilities reintegrated and retested before relaunch.
The governance layer is moving beyond plugin and MCP allowlists. Enterprises can now decide which agent operations are blocked, require human approval or proceed automatically, with managed restrictions that local settings and saved approvals cannot weaken.
This is a useful reminder that exploitation pressure does not scale neatly with plugin popularity: Wordfence says it has blocked more than 250,000 attempts against a plugin with a five-figure install base.
The important development is active exploitation, not the original vulnerability disclosure. WordPress operators running Elementor Pro 4.2.1 or earlier should treat this as an immediate patch-and-hunt event, especially on sites with public forms that include optional file uploads.
Jalapeño is working first-party silicon rather than a roadmap item, and OpenAI now says AI itself materially accelerated the design process. The distinction still matters: tape-out means the design was finalized for manufacturing; it does not mean fleet-scale production qualification or API deployment is complete.
The architecture is unchanged—Quack/CONNECT, a stable extension ABI, new storage and parser foundations—but the migration window is now concrete. Builders can test real 2.0 alpha clients before the projected October release.
The change creates an authentication compatibility boundary for server-to-server Gemini integrations: an architecture that works in an existing project may not be reproducible with a newly introduced service account, and Google has not published an end date for the restriction.
Railway’s managed MySQL path can now gain automatic failover without rebuilding the database elsewhere. The trade-off is real operational complexity: conversion briefly drops connections, hard-coded URLs need manual repair, replicas are for failover rather than read scaling, and each extra database/proxy node consumes billable resources.
The checkout ScriptTag shutdown already had an earlier deadline; this is the separate storefront cutoff. Pinning an old Admin API version will not preserve write access after October, and any feature still depending on an injected storefront script stops working in March.