Developer Tools
Google Opens Speakeasy's SDK Generator to Combat Platform Risk
Google and Speakeasy partner to release open-source tooling for generating client libraries across multiple languages, addressing vulnerabilities in proprietary code-generation infrastructure.
Google Developers Blog (AI)
Google has announced a partnership with Speakeasy to release an open-source SDK code generator, responding to a critical gap that emerged when the company's previous generation tooling provider shut down unexpectedly. The move underscores a growing industry concern: reliance on proprietary infrastructure for converting API specifications into production client code poses unacceptable business continuity risks.
The Problem That Triggered the Shift#
Building clean, language-specific SDKs from evolving API definitions is inherently complex, requiring management of streaming protocols, error structures, and type systems across multiple programming environments. For years, specialized proprietary generators served this role effectively. However, when Google's SDK provider was acquired and abruptly announced discontinuation in May 2026—just as the company was rolling out its new Interactions API at Google I/O—the weakness of depending on a single closed-source tool became painfully apparent.
This disruption forced Google to quickly rearchitect its SDK pipeline while maintaining stability for developers and preventing breaking changes to existing libraries.
The Open-Source Solution#
Rather than rebuild generators in-house, Google collaborated with Speakeasy to migrate client libraries and, crucially, to open source the entire code-generation suite under the AGPLv3 license. The new tooling includes:
- Multi-language SDK generation for Python, TypeScript, Go, Java, C#, PHP, and Ruby, with each library including static typing, streaming support, automatic retries, and pagination
- Agent-native CLI generation that produces standalone binaries AI agents can invoke directly from the terminal
- Documentation MCP server generation, converting OpenAPI specs into Model Context Protocol servers that coding agents can query for verified schema information
The licensing model allows organizations to run the generator in development or CI pipelines while retaining ownership of generated code under their preferred open-source license (MIT, Apache 2.0, etc.). Modifications to the generator itself remain subject to AGPL requirements, ensuring improvements flow back to the community.
