Purpose
Choosing an SDK means more than finding a package name. You need to know who maintains it, which providers it supports, what it abstracts, and where that abstraction ends.
We’re building a starting point for that work: a curated catalog spanning email, social platforms, domains, sandboxes, files, SMS, search, and databases. Each entry points back to its official documentation and source.
SDK SDK is an independent project by Belweave. Listed projects belong to their respective maintainers. Inclusion is editorial and does not imply a partnership or endorsement.
Editorial approach
We distinguish unified SDKs, provider clients, and developer toolkits. They solve different problems, and a shared category doesn’t make them interchangeable.
- Start with primary sources.Official documentation, source repositories, and package metadata inform every listing.
- Make limitations visible.Provider-specific behavior, account requirements, and important caveats belong beside the features.
- Teach the decision.Our docs cover capabilities, testing, configuration, and fallback semantics so you can evaluate the next SDK yourself.
- Keep scope honest.This is a curated starting collection, not an exhaustive inventory. Package APIs and provider support change; check upstream before shipping.
Our projects
sdk-sdk.com is the umbrella. Our search and database SDKs provide shared interfaces across supported providers. Their current availability is part of each listing, and their shared ownership is disclosed.
searchSDK.devOpen source · source alphaTwelve language and platform SDKs, fourteen search adapters, and thirteen provider-native clients. Public MIT-licensed source, language guides, and a playground with live and key-free demo modes.
Explore searchSDKdbSDK.com / database-sdk.devSource-only · v0.1Provision and manage databases, run typed PostgreSQL queries, use Drizzle, and transfer data between supported providers. Public Apache-2.0 source and docs; install from a source build.
Explore dbSDK