SDKs
One SDK per stack, the same products everywhere — installation, configuration, framework integrations and the complete API reference.
FlutterDart
nexus_flutteriOS · Android · Web · Desktop
JavaScriptTypeScript
@inverge/nexusBrowser · Node · React
PHPPHP 8.1+
inverge/nexusLaravel · Symfony · any PHP
PythonPython 3.8+
inverge-nexusDjango · Flask · FastAPI · Celery
.NETC#
Inverge.NexusASP.NET Core · workers · console
Each SDK has two parts here:
- Overview — install, initialise, configure, and wire it into your framework.
- API reference — every public class, method, option and type, generated from the SDK's source and doc comments (so it matches the version you install).
Which one?
| You're building | Use |
|---|---|
| A mobile or desktop app (Flutter) | Flutter |
| A web front end (React, Vue, Angular, Svelte…) | JavaScript |
| A Node backend (Express, Fastify, Nest, Next.js…) | JavaScript + Telescope for Node |
| A Laravel, Symfony or PHP backend | PHP |
| A Django, Flask, FastAPI or Celery backend | Python |
| An ASP.NET Core service or .NET worker | .NET |
| Anything else | The REST API, or OpenTelemetry for tracing |
Shared conventions
- One key per environment, from code or
NEXUS_API_KEY. - Buffered telemetry: tracking never blocks and never throws; flush before a short-lived process exits.
- Every product can be switched off with an environment variable — see Switching services off.
- Ambient identity on servers: bind the person once per request (the framework integrations do it), and everything below is attributed.