--- title: SDK Getting Started description: "Get started with a Statsig SDK by choosing your platform, installing the package, initializing with your API key, and evaluating your first gate." product: general token_estimate: 1245 --- # SDK Getting Started > For AI agents: a documentation index is available at [/llms.txt](/llms.txt). Append `.md` to any page URL for markdown, or send `Accept: text/markdown`. This guide describes how to fully implement your Statsig instance with SDKs. If you want a faster implementation, read the [SDK Quickstart](https://docs.statsig.com/sdks/quickstart) guide. Statsig's SDKs are the in-code tool you'll use to show experiment variants, flag features, and log key business metrics. Statsig's SDKs: - **Abstract the complexity:** Statsig handles caching, retry mechanisms, and networking. - **Encourage best practices:** Built around parameters and language-specific best practices. - **Broad deployment support:** 30+ SDKs across clients, servers, the edge, and more. ## When to use Statsig SDKs ### 1. Targeting and assignment Decide who sees new features and experiment variants. Target based on any user attributes (for example, location or device type) or environment-level attributes to control rollouts and experiment enrollment. Statsig assigns each user deterministically, so the same user gets a consistent experience across sessions and devices as long as you pass a stable identifier. You can also layer multiple targeting rules and set overrides to force specific users into a variant for testing or QA. ### 2. Logging events Log key business metrics to power experiment and product analytics. Events flow into Statsig automatically. For web-based platforms (for example, JavaScript, React), Statsig also supports [Autocaptured events](https://docs.statsig.com/webanalytics/overview). Attach a value and custom metadata to each event so you can build precise metrics and segment results later. Because metrics are defined in the Statsig console, you can create new metrics from events you already log without shipping additional code. ## Choose between client and server SDKs Statsig offers both client-side and server-side SDKs, each suited to different use cases: - **Client-side SDKs**: Designed for user-facing applications where you log events directly from the browser or mobile app. These SDKs operate in real time and provide instant feedback on user behavior. - **Server-side SDKs**: Designed for backend services. Use server-side SDKs to control experiments, feature flags, and log server-side events. Server-side SDKs provide more control for use cases involving system-level actions or business logic. For a detailed comparison, go to the [Client vs Server SDK Overview](https://docs.statsig.com/sdks/client-vs-server). For frameworks like **Next.js** that bridge client and server-side logic, go to the [Next.js SDK](https://docs.statsig.com/client/Next) guide. ## Available SDKs Statsig offers SDKs for a wide variety of platforms: ### Client-side SDKs ### [JavaScript](https://docs.statsig.com/client/javascript-sdk) Browser JavaScript ### [React](https://docs.statsig.com/client/React) Client-Side React ### [React Native](https://docs.statsig.com/client/ReactNative) Bare React Native SDK ### [Next.js](https://docs.statsig.com/client/Next) Next.js SSR, SSG & Client-Side ### [Angular](https://docs.statsig.com/client/Angular) Angular bindings for Javascript SDK ### [Swift](https://docs.statsig.com/client/iosClientSDK) iOS, MacOS, tvOS SDK ### [Android](https://docs.statsig.com/client/Android) Android Kotlin/Java SDK ### [.NET Client](https://docs.statsig.com/client/DotNet) Client SDK for .NET framework ### [Roku](https://docs.statsig.com/client/Roku) Roku Brightscript SDK ### [Unity](https://docs.statsig.com/client/Unity) Unity game engine SDK ### [Dart/Flutter](https://docs.statsig.com/client/Dart) Flutter/Dart Mobile App SDK ### [C++ Client](https://docs.statsig.com/client/CPP) C++ client-side SDK ### Server-side SDKs ### [Node.js](https://docs.statsig.com/server-core/node-core) Node.js server SDK ### [Java](https://docs.statsig.com/server-core/java-core) Java server SDK ### [Python](https://docs.statsig.com/server-core/python-core) Python server SDK ### [Go](https://docs.statsig.com/server/go) Go server SDK ### [Ruby](https://docs.statsig.com/server/ruby) Ruby server SDK ### [.NET Server](https://docs.statsig.com/server-core/dotnet-core) .NET server SDK ### [PHP](https://docs.statsig.com/server-core/php-core) PHP server SDK ### [Rust](https://docs.statsig.com/server-core/rust-core) Rust server SDK ### [C++ Server](https://docs.statsig.com/server-core/cpp-core) C++ server SDK --- ## How to install your SDK 1. **Select your SDK**: Choose the client or server SDK that fits your platform from the lists above. 2. **Follow the installation guide**: Each SDK has an installation guide that walks you through setup. 3. **Start experimenting**: After you integrate the SDK, set up feature flags, run experiments, and log events for analysis. If you have questions or need help with installation, reach out in the [Slack community](https://statsig.com/slack).