Google DevelopersAmir Hardon, Philipp Schmid3 min readintermediate
Why client SDK generation belongs in the open
Summary
Google partnered with Speakeasy to open‑source their OpenAPI‑based multi‑language SDK generator, covering Python, TypeScript, Go, Java, C#, PHP, and Ruby. The move replaces a now‑defunct proprietary generator, reduces maintenance overhead to ~1 engineer, and adds a CLI and documentation server generator under AGPLv3.
- Closed‑source SDK generators pose platform risk; open tooling mitigates disruption.
- Speakeasy’s generator produces idiomatic client libraries with static typing, SSE streaming, retries, and pagination across seven languages.
- Open‑sourcing under AGPLv3 lets teams run the generator in CI while licensing generated SDKs as they wish.
- Google’s migration reduced engineering effort from multiple engineers to roughly one, showing maintainability benefits.
Reliance on proprietary codegen can break developer pipelines when vendors disappear. Open, deterministic generators ensure continuity for fast‑moving APIs like Google’s GenAI services and enable broader ecosystem tooling (CLIs, MCP docs).
5/10



