Find published research by company, product, platform or technology.
Showing 141–160 of 227 dossiers
The most broadly relevant issue lets attackers potentially drive TLS retransmission state into unbounded behavior or acknowledge packets that cannot be outstanding. Several additional fixes narrow local or configuration-dependent Windows attack paths.
The faster browser cadence is now moving from planning into production: Firefox 155 ships September 1 and Chrome 153 follows September 8. Web teams have less time between major versions for compatibility testing, documentation and enterprise rollout decisions.
Anthropic’s pre-IPO economics now include another enormous reported infrastructure commitment: Reuters says the company will spend $45B over six years on Nscale capacity beginning in late 2027. Anthropic declined to comment, so the deal remains sourced reporting rather than a company-confirmed obligation.
Shopify's App Pricing migration is now clearer: directly matching subscriptions can move through plan setup, while usage-based and price-mismatched subscriptions stay on the Billing API until a separate Migration API arrives.
Audience-management systems can now fail with `SEGMENT_LIMIT_EXCEEDED`, while old geography identifiers begin returning invalid-field errors after August 31. LinkedIn also opened the Matched Audiences API to applications from qualified developers, increasing the importance of handling these limits correctly.
Astro 7.2’s experimental incremental-build mode attacks the page-generation phase rather than only bundling speed. Large static sites can opt routes into cache-aware reuse, but teams must choose correct cache keys and persist Astro’s cache directory in CI to benefit safely.
Vercel KMS gives Functions OIDC-authenticated access to managed RSA, ECDSA and EdDSA signing keys. Builders can scope grants by project and environment, constrain JWT claims with JSON Schema, rotate keys centrally and publish standard OIDC/JWKS metadata for verification outside Vercel.
The underlying migration is unchanged, but Reddit’s own deadline documentation is not stable. Integrations should be ready for the earlier September 21 date while treating October 30 as the current published cutoff for hourly reports longer than seven days.
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.
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.
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 Anthropic ruling is not merely a political dispute: a procurement classification that could prevent defense contractors from using Claude on Pentagon work has been struck down. Builders serving government customers still need to watch separate directives and appeals, but one material supplier-risk constraint is no longer enforceable under the current ruling.
The new recovery rule does not remove refresh-token rotation, but it makes the upcoming January 2027 migration safer: losing a successful refresh response no longer necessarily forces a merchant to reopen and reauthorize the app.
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.
Reprise was already Symfony’s recommended modern bundler integration, but 1.0 changes the adoption decision: applications can now depend on a documented compatibility contract rather than an experimental 0.x API, while Encore remains available in low-maintenance mode.
Memory-bound agents, retrieval systems and stateful services can now choose 2-, 4-, 8- and 12-CPU Render plans with much wider RAM ratios. Existing plan prices and legacy IDs stay compatible; the new choices change the cost trade-off for workloads that previously had to overbuy CPU to get enough memory.
DigitalOcean’s MySQL 8.0 support window now has a hard operational endpoint. Existing managed clusters need application and schema compatibility testing before October 30 because the provider will move them to 8.4 during maintenance rather than leave 8.0 running indefinitely.
The latest private-SaaS deal-size benchmark shows median ACV moving down, with bootstrapped companies at $18,643 versus $39,880 for equity-backed peers. For small SaaS operators, the useful question is whether larger contracts improve retention and economics enough to justify the longer sales motion.
Apple’s October EU terms rewrite replaces the per-install Core Technology Fee with transaction commissions and lets alternative payments coexist with IAP. The exact rate table makes the economics clearer: developers need to model checkout method, program eligibility and distribution channel rather than install scale alone.
Chrome 153 introduces a breaking provider-integration change in the Email Verification origin trial: issuance requests move to JSON with HTTP Message Signatures. Chrome has also extended the experiment through 156, making the migration more than a one-release test detail while the underlying protocol remains experimental.