Find published research by company, product, platform or technology.
Showing 141–160 of 227 dossiers
Rosetta’s transition is now an application compatibility deadline rather than an open-ended safety net. Intel-only Mac apps need an Apple-silicon build before support ends after macOS 27, with only a narrow exception retained for older unmaintained games.
Cloud SQL’s SQL Server HA path is becoming more transparent to applications: supported proxies and connectors can target one write endpoint and be redirected when the primary changes. Teams still need retry-safe connection handling around the failover itself.
The useful finding is not that one pricing model has 'won.' It is that observable SaaS pricing is much more heterogeneous than the default per-seat narrative suggests—and that the answer changes sharply with methodology. PulseSignal’s living public-price census keeps moving, and its latest disclosed extraction audit improved to 90%, but the data should still be treated as directional packaging evidence rather than a universal market truth.
Self-Hosted Machines changes the architecture of Cursor’s Cloud Agents more than another model option would. Teams can keep code, build outputs, secrets and terminal/browser actions on infrastructure they control, but the planning/inference loop remains a Cursor service and enterprise teams become responsible for worker images, scaling, secrets and production validation.
The interesting part is not another AI scanner. Cloudflare is connecting source-code evidence to what is actually deployed and being attacked at the edge, validating findings outside the model, then preparing both a code patch and, where appropriate, a narrowly scoped WAF mitigation for customer review.
Brazilian customers can now authorize Pix Automático mandates for Paddle subscriptions. The new path broadens local-payment access for SaaS, while delayed renewals, fixed mandate amounts and documentation that still mentions early access create implementation caveats.
npm v12 disables dependency lifecycle scripts, Git dependencies and remote-URL dependencies by default unless projects explicitly allow them. GitHub has now also expanded npm trusted publishing and made malware scanning a gate before staged packages can be approved.
The new AWS–Azure pairing is less about raw bandwidth than an operational boundary shift: each cloud provider now manages its side of the private cross-cloud connection, with prebuilt capacity and native provisioning instead of a bespoke interconnect stack.
K2 Horizon is notable less for another benchmark claim than for reproducibility: IFM is publishing model weights, architecture, training code, data or construction recipes, evaluation resources and intermediate training material instead of stopping at a final checkpoint.
Funes treats agent memory as user-owned data rather than a hosted account feature: retrieval and reranking run locally, provenance stays attached to recalled passages, and cross-machine sharing is optional. The main risk is that publishing session-derived memory can still expose secrets if redaction misses them.
Tailcat is deliberately smaller than a tailnet: peers exchange a short connection token out of band, then Tailscale’s data-plane code tries direct UDP and falls back to DERP. The trade-off is that the new tool has no stability or service guarantees yet.
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.
Hugging Face has released 207 Apache-2.0 WebGPU kernels, a JavaScript loader and Fleet, a browser benchmarking service. The package makes kernel contracts and correctness evidence inspectable, but performance remains device- and workload-dependent.
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.
The limits themselves were already documented; the material change is enforcement. Free-tier D1 workloads that previously relied on soft overage behavior now need query-cost awareness, indexes and a plan for temporary failures or paid migration.
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.
The DuckLabs deal separates company ownership from project governance: AWS gets the team behind DuckDB, while the DuckDB Foundation keeps stewardship and the MIT license stays in place. Builders should watch whether that separation remains meaningful as AWS integrates the Duck Stack into its analytics services.
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.
From September and October, Copilot Business and Enterprise seat access becomes more tightly coupled to upfront payment. A separate September 28 policy migration enables a unified Copilot experience by default, retains github.com chat data for the life of the account and changes code review’s default effort from Lite to Balanced.
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.