For API teams choosing - or pruning - their client libraries
SDK PortfolioShip SDKs for the languages your integrators actually use - and retire the rest on evidence, not gut feeling.
Describe the API and list every language with its traffic share, deal requests and today's status. Your browser reads each language against a self-set add-threshold and your vertical's language map, gives it one action - add, keep, promote, community, self-service, retire or gather evidence first - ranks the build model, checks the three versioning policies stay apart, and holds every end-of-life to the exclusive-usage evidence. Then the strategy, and the end-of-life cases.
The API, and a short interview free
The languages free
The checks free
What the page flags
The gates
Every language and its decision
The build model, ranked
Area by area
Your portfolio table free
The table the strategy opens with - every language, its decision and why - with the self-set threshold written down.
Portfolio (Markdown)
The portfolio strategy metered
Pricing as soon as the session is ready...
Sign inThe reply could not be read. Here it is as it came back:
Caveats
Caveats
The page's check of this reply
Saved portfolios
How it works - and what is sourced
The order follows the skill: the integrating vertical decides it, not a popularity chart - fintech front-loads Java, C#, Ruby and Go, AI and dev-tools front-load Python and TypeScript. A language earns an official SDK at or over the add-threshold (a share of traffic, or named deal requests - self-set, since no vendor publishes one), or when the team already maintains it fluently and the vertical ranks it top four; with no telemetry, the vertical's top three stand in until it exists. A community SDK past the threshold goes through the promotion gate; below it, the community list or spec-driven self-service.
An official SDK below the threshold is never dropped on downloads alone: with no exclusive-usage count it needs evidence first; with accounts or revenue that depend on it alone, it stays; with none, it retires - final release, announcement, archive. The build model defaults to a commercial generator driven by the spec, steps down to the free OpenAPI Generator when procurement or self-hosting rules a vendor out, and becomes a handwritten flagship only when the API is the product and one language carries half the traffic.