Start here
SDKs Matrix
Compare the supported SDKs, the runtime each one targets, and the fastest path into production for your stack.
| SDK | Best for | Key capabilities | Next step |
|---|---|---|---|
| Node.js services and modern browser apps | TypeScript support, Node.js and browser usage, default values, local rule evaluation, and optional usage reporting. | Open quickstart | |
| Traditional server-rendered applications, APIs, and background workers | Context-aware evaluation, safe defaults, first-match rule evaluation, and local rule caching. | Open quickstart | |
| Laravel applications that want framework-native configuration and facades | Laravel-focused integration flow, application configuration, and framework-friendly evaluation patterns. | Open quickstart | |
| Django, Flask, FastAPI, and any WSGI or ASGI Python application | Sync and async clients, context-aware evaluation, deterministic bucketing, safe defaults, and ~1ms local flag evaluation. | Open quickstart | |
| Cloud-native services, API gateways, and other latency-sensitive Go backends | Context-aware evaluation, deterministic bucketing, local rule caching, and middleware for net/http, Gin, and Echo. | Open quickstart |
JavaScript repository
Examples, changelog, TypeScript support notes, and runtime-specific configuration details.
PHP repository
Examples, operator behavior, rollout bucketing, and default-value patterns for PHP applications.
Laravel repository
Framework integration details, service provider behavior, and example Laravel usage patterns.
Python repository
Examples, async patterns, Django and Flask integration notes, and PyPI package details.
Go repository
Examples, middleware submodules for Gin and Echo, and Go module registry details.
Next step
Take the next integration step in your own stack.
Start with the quickstart that matches your runtime, then return to the reference pages when you need exact request and payload details.
Language and framework names and logos shown above are trademarks or registered trademarks of their respective owners. Their use here is for identification purposes only and does not imply endorsement of, or affiliation with, Zenmanage.