GetFluxly SDKs
GetFluxly has six SDKs. Pick the one that matches your runtime or framework, and combine them when your stack has both a browser layer and a server layer.
Available SDKs
| Package | Runtime | Install | Use it for |
|---|---|---|---|
@getfluxly/browser | Browser / JS | npm install @getfluxly/browser | Autocapture, client events, consent |
@getfluxly/react | React | npm i @getfluxly/react | Hooks, provider, SSR-safe wrappers |
@getfluxly/next | Next.js App Router | npm i @getfluxly/next | Client script, server tracking, middleware |
@getfluxly/node | Node.js server | npm install @getfluxly/node | Batched server-side events, identify, alias |
getfluxly | Python | pip install getfluxly | Backend tracking from Python services |
getfluxly | Ruby gem | gem install getfluxly | Rails / Rack backend tracking |
Choosing an SDK
Use @getfluxly/browser for any web page where you want autocapture and consent management with no framework dependency. Use @getfluxly/react when your app is already in React and you want hooks instead of a singleton. Use @getfluxly/next for Next.js App Router projects, it handles the client script injection, server-side tracking in route handlers, and middleware attribution in one package.
For server-side work, @getfluxly/node covers Node.js runtimes including Vercel Functions and Lambda. getfluxly (Python) and getfluxly (Ruby) cover those respective backends with the same track/identify surface.
You can combine SDKs. A common pattern is @getfluxly/next on the client plus @getfluxly/node in API routes for server-side events tied to the same anonymous or identified user.
Experimental: Ruby and Python
identify()are experimental and not yet stitched end-to-end. Usetrack()with a custom identify event on those SDKs for now.