Find published research by company, product, platform or technology.
Showing 121–140 of 458 dossiers
From January 2027, Gmail will no longer send mail as non-Google addresses or fetch third-party accounts through Gmailify/POP on the web. Forwarding into Gmail and third-party accounts in the mobile app remain available, so small-business and custom-domain users need to distinguish the affected desktop workflow from Gmail’s broader mail protocols.
This is a platform architecture migration rather than a user-facing feature. Pantheon says no action is required, but builders operating storage-sensitive WordPress or Drupal workloads should know when their tier moves and verify backup, restore and file-handling behavior around the change.
Periskope is moving toward a hybrid SaaS model: core access is still licensed per user, but variable AI work is now represented by credits that can be topped up separately. Monthly customers also face a 17–25% seat-price increase while annual rates remain unchanged.
Manifest V2 was already disabled for modern Chrome users. The August 31 change closes the remaining Web Store path, turning any still-pinned legacy install into an effectively frozen artifact with no Store update or reinstall route.
The two August 28 changes move a common production-agent problem out of bespoke application code: builders can derive memory boundaries from authenticated JWT claims, enforce them with Cedar policy, and organize the stored memory using runtime tenant dimensions.
Azure’s old PostgreSQL versions do not switch off on September 1, but they do become a paid legacy choice. Extended Support is automatic, billed by vCore-hour for running servers, and cannot be declined while an unsupported engine version remains in use.
A third-party GEO dataset recorded an 86.4% relative collapse in Reddit’s visible ChatGPT Search citation share while Google AI citation changes were much smaller. The result is a useful warning against building an AI-discovery strategy around one source platform, not proof of an OpenAI penalty or Reddit removal.
Cloud Run instances sit between autoscaling serverless services and a small VM. They run one individually addressable container continuously, can be stopped and restarted, and use shared CPU economics; Google’s launch example prices 1 vCPU plus 1 GiB running for 30 days at $5.70.
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.
Product teams can launch a root-cause investigation from an Insights report, an alert or Mixpanel Agent instead of manually trying breakdown after breakdown. The result is operationally useful, but it remains an automated statistical diagnosis rather than proof of causation.
The August 28 transition is now active, and Railway’s current documentation removes an earlier ambiguity about new services in existing projects. Config as Code is legacy-only from here; production users should migrate and validate `.railway/railway.ts` before the December hard cutoff.
Google is changing Gemini Notebook’s packaging from feature-style quotas toward a compute budget. That gives users more flexibility but makes the effective cost of one request less predictable and ties premium upgrades more directly to computational intensity.
Google is tying licensed commercial content directly to an AI workspace: book ownership becomes the access control for grounded AI use. That gives publishers a new distribution path while keeping paid-source entitlement inside the AI experience.
For some queries, Google is no longer waiting for a user to open a longer AI Overview. The system can expand it automatically, creating a larger zero-click answer surface and moving traditional results further down the page.
Postmark’s new IP Allowlisting creates an extra sending boundary around API credentials: trusted infrastructure can send normally, while requests from outside configured ranges fail even if the token itself is valid. SMTP is not covered.
Amplitude’s new consent gating separates the visible experiment experience from persistence and measurement. Sites can avoid experiment flicker before a consent decision, but denied users’ buffered impressions are discarded and Analytics consent still has to be handled separately.
AgentControl now spans more production stacks: applications can resolve different prompts and models by context, track token/cost behavior, require approvals, use Bedrock without proxying inference through LaunchDarkly, and inspect multi-step agent runs as one conversation.
The price changes are not uniform: H100/H200 rise about 14%, B200 30%, B300 25% and GB300 about 11%. Builders using dedicated inference or training should re-run workload economics before assuming newer accelerators remain the cheapest route per completed task.
v5 gives DigitalOcean users a more composable VM shape instead of choosing only from fixed bundles, with vendor-claimed per-core performance gains up to 30%. The billing model deserves equal attention: long-running v5 instances do not inherit a monthly usage ceiling.
GLM-5.3-Flash combines open weights, multimodal coding/agent capability and an 18B-active sparse architecture with a large anonymous pre-launch trial. Z.ai has already issued a chat-template correction for early downloads, showing that day-one self-hosted deployments need artifact-level validation as well as model benchmarking.