Semantic Kernel vs Anthropic
Side-by-side trajectory, velocity, and editorial themes.
Semantic Kernel READMEs now name a successor — Microsoft Agent Framework is the next stop.
Semantic Kernel's most recent Python release (1.42.0) added an explicit 'Microsoft Agent Framework successor callout' to the READMEs — Microsoft is publicly pointing users toward a different framework as the forward path. The rest of the recent cadence is consistent with a project in late-stage maintenance: security hardening (path validation in CloudDrivePlugin, gRPC plugin, OpenAPI plugin; SQL escaping in connectors; Snappier and Kiota vulnerability bumps), dependency bumps via dependabot, vector-store connector polish, and small prompt-template fixes. Feature additions are narrow — ImageContent in tool/function results, OpenAI text-to-image model support, prompt template serialization improvements.
The project is transitioning from active framework to maintained predecessor. Microsoft's agent stack is consolidating under the new Microsoft Agent Framework banner, and Semantic Kernel is shifting into security-and-deps mode — the kind of release pattern you see when a team is keeping production users safe while migration paths are being built elsewhere. Read in parallel with the eight-month silence at AutoGen, the picture is clear: Microsoft is collapsing three previous agent-framework efforts (SK, AutoGen, Semantic Workbench) toward one supported runtime.
Expect SK to stay on a security-and-deps cadence for at least another two quarters, with a hard deprecation timeline likely announced once Microsoft Agent Framework has feature parity. Anyone building net-new on Semantic Kernel today should plan a migration; existing deployments are safe for the moment but on borrowed roadmap time.
Anthropic is buying, deploying, and SKU-ing in parallel — the enterprise build-out is in full sprint.
Anthropic is running a dense enterprise expansion: two Big 4 deployments (PwC and a 276,000-seat KPMG alliance), an M&A move (Stainless), a $200M Gates Foundation partnership, a new Small Business SKU, and a financial-services agents push. A compute deal with SpaceX and the formation of a joint enterprise AI services company with Blackstone, Hellman & Friedman, and Goldman Sachs sit behind it as supply-side and distribution-side reinforcement. Public-facing posts on 'widening the conversation on frontier AI' provide the policy framing around the buildout.
The arc is unmistakable: Claude is being placed at every layer of the enterprise stack — at Big 4 consulting firms (who will resell and implement it), inside a new joint services company with private-equity and bank partners, and into a Small Business SKU at the other end of the market. Acquiring Stainless brings SDK-generation in-house, which signals investment in developer-tooling depth rather than just model access. The Gates Foundation deal extends the surface beyond commercial verticals into global-development use cases, and SpaceX compute secures the capacity to back all of it.
Expect a Claude Financial Services GA off the back of the agents post, and a third Big 4 deployment to close the pattern. The Stainless acquisition will likely surface as a sharper Claude API SDK / typed-agent toolkit within a quarter — the integration target is the developer surface, not just the SDKs themselves.
See more alternatives to Semantic Kernel →
See more alternatives to Anthropic →