Monthly AI Changes
A dated monthly log of what changed, why it matters, and where to verify it.
How this changelog works
AI vendors ship changes weekly. Pricing shifts, model names get renamed, capabilities get deprecated, and policy pages get rewritten without announcement. If you build workflows on top of these platforms, you need a single place to track what actually changed — not marketing claims, and not rumor.
This page is that single source. Each month we log the changes that matter for people running AI in production: pricing updates, plan restructures, regulatory milestones, and model releases that change what you can build. Every entry links to the vendor's own source page so you can verify the claim yourself.
We do not chase every model release. We log the changes that force a decision: a plan you need to re-evaluate, a deprecation that breaks a workflow, a compliance date that changes your roadmap. If a change shows up here, treat it as worth a 10-minute review at your next planning meeting.
March 2026
- OpenAI pricing page reflects latest plan structure and model access tiers.
- Perplexity plan guidance updated with Standard/Pro/Max and enterprise options.
- EU AI Act implementation timeline remains active with August 2026 milestone approaching.
February 2026
- Anthropic released Claude Sonnet 4.6 update information.
- DeepSeek published updated pricing guidance for V3.2 APIs.
January 2026
- Google AI plan pages continued clarifying AI Pro and premium capabilities.
- Microsoft Copilot pricing page continued listing business plan structure and add-ons.
What qualifies as a change
Not every vendor update makes this log. We include a change only when it meets one of four tests.
- Pricing or plan structure shifts: a new tier, a renamed plan, a seat minimum change, or a capability moved behind a paywall.
- Model availability changes: releases, deprecations, rate-limit shifts, or API pricing updates that affect production cost models.
- Policy or compliance updates: regulatory milestones, terms-of-service changes, data-handling shifts, or vendor-published governance guidance.
- Capability or integration changes: new MCP connectors, workspace features, or agent capabilities that change what you can ship.
We do not log benchmark wins, marketing launches, or blog posts that don't map to an actual product change. The bar is: if a reader acts on this entry, something in their stack, budget, or plan will be different.
How to use this page
Treat this as a monthly review input. At the start of each month, scan the latest entries against your current AI spend, your active model contracts, and any compliance commitments you've made. Flag anything that requires a decision and move it into your ops review.
Every linked source is the vendor's own page, not a third-party summary. If you're presenting a finding to a stakeholder, quote the vendor source directly — that's what they'll ask for when you propose a change.
FAQ
How often is this page updated?
Monthly. We add a new dated entry at the start of each month covering the prior month's material changes. If a critical mid-month change lands — a major deprecation or compliance update — we add it immediately and note the date.
Why don't you include every model release?
Because most releases don't force a decision. We include releases that unlock new capability classes, deprecate existing endpoints, or change pricing. A slightly-better benchmark score is not a change worth logging.
How do I verify an entry?
Click the source link under each entry. Every claim on this page resolves to the vendor's own documentation, pricing page, or official announcement. If a vendor page has changed since we logged the entry, the archived version is usually retrievable via the Wayback Machine.