Once your SDK is in someone else’s app, you lose sight of it. SDK Garden shows which versions are still running in the wild, where integrations stall before the first successful call, and which parts of your API nobody uses, so you know what to fix, what to deprecate, and who to nudge to upgrade.
Free for your first SDK. About fifteen minutes to set up. The demo needs no signup.
// the blind spot
Download counts stop at the install. Everything after that happens inside apps you don’t own, run by developers you’ll never hear from unless something breaks badly enough to open an issue.
Error tracking
Great for code you deploy. Blind to your library running in thousands of apps you’ll never see.
Product analytics
Built for end users and screens, not for developers calling methods on your API.
SDK Garden
Versions in the wild, integrations that stall, and the API surface people actually depend on, across every language you publish.
// what you'll know
Your issue tracker only hears from the developers who got stuck and bothered to write in. SDK Garden hears from every install.
See the share of real sessions on each release, not just download numbers. Find out that 40% of installs are still on v1.x before you ship a breaking change, and know when it’s finally safe to drop an old major. SDK Garden flags versions nobody has run for 30 days.
Follow every session from process start to the first successful call, and see exactly where integrations stall before they get there. A drop between "started" and "initialized" usually means a missing key, a bad config, or a runtime you don’t support yet.
Wrap your public methods and get call counts, error rates and durations for each. Find the API surface people depend on before you change it, and the parts nobody uses that you can safely deprecate.
| method | calls | errors | p50 |
|---|---|---|---|
| charges.create | 1.2M | 0.4% | 88ms |
| customers.get | 640K | 0.1% | 31ms |
| refunds.create | 52K | 2.3% | 120ms |
| legacy.sync | 14 | — | — |
Error rates per version, compared with your average, the day a release starts rolling out. Catch the regression while it's on 3% of installs, not 60%.
// integration
You add the client to your SDK. Your users don't install or configure anything.
Network failures are swallowed — the client never throws into your users' code. Set disabled: true to turn it off, for example when your own users opt out.
// npm install sdk-garden-js
import SdkGarden from 'sdk-garden-js';
import { version } from '../package.json';
SdkGarden.init({
apiKey: 'sgk_…',
sdkName: 'acme-node',
sdkVersion: version,
});
export class Charges {
@SdkGarden.trackMethod('charges.create')
async create(params: ChargeParams) {
// your implementation
}
}# pip install sdk-garden-python
from sdk_garden import SdkGarden
from acme import __version__
sg = SdkGarden(
api_key="sgk_…",
sdk_name="acme-python",
sdk_version=__version__,
).start()
class Charges:
@sg.track_method("charges.create")
def create(self, **params):
...// pricing
Each client library you ship is its own product, so that's what you pay for. Invite your whole team, and get single sign-on on every paid plan.
$0
For a maintainer with one SDK.
$29 per SDK / month
For companies shipping SDKs in several languages.
Let's talk
For large install bases and procurement requirements.
Node, Python, Go, Java and Swift clients would be five SDKs. Each gets its own dashboard, keys and event allowance.
// your users' data
You’re putting this inside other people’s apps, so here is the whole list.
disabled: true// security
Your customers' security teams will ask. These are the answers.
disabled: trueThese are the companies that process data on our behalf to run SDK Garden. We’ll update this list before we add a new one.
| Company | What it does for us | Data it handles | Location |
|---|---|---|---|
| Fly.io | Application hosting and the managed PostgreSQL database | Account details and SDK events | United States |
| Upstash | Redis for rate limiting | Short-lived request counters, keyed by hashed API key or, for sign-in, by IP address | United States |
| Netlify | Hosting for this marketing site | Standard web request logs. No SDK events | Global CDN |
To report a vulnerability or request our security details, email hello@sdkgarden.com.
// questions
Events go into an in-memory buffer and are sent in batches in the background — on a daemon thread in Python, with fetch in JavaScript. Your methods don't wait on the network.
Nothing your users would notice. Network errors are caught inside the client and never reach their code.
Sentry tells you when your app crashes. Product analytics tells you what your users click. Neither tells you what happens to your SDK once it ships into everyone else’s apps. SDK Garden shows which versions are still running in the wild, where integrations stall before the first successful call, and which parts of your API nobody uses. It works alongside Sentry, not instead of it.
JavaScript/TypeScript (Node and browsers) and Python today. The ingest API is a documented JSON endpoint, so other languages can send events directly while their clients are in progress.
Yes. Single sign-on over OpenID Connect works with Okta, Microsoft Entra ID, Google Workspace, Auth0 and others, on every paid plan.
Free for your first SDK. Setup takes about fifteen minutes, and the dashboard tells you the moment the first event arrives.