SDKs
Official libraries for connecting to Nexo from your application. All SDKs expose the same unified API across Store, Pub/Sub, Queue, and Stream brokers.
Versioning
Nexo is released as a single product: the Docker image and every SDK move to the next version together. You do not need to check compatibility tables or guess which SDK works with which image — matching versions are guaranteed to work.
This means:
- One version number covers the Docker image, the TypeScript SDK, the Python SDK, and any future SDK.
- A new SDK enters at the current Docker image version, not from
v0.1.0. - When the Docker image bumps, all SDKs bump at the same time.
Example release flow
| Release | Docker image | TypeScript SDK | Python SDK | Note |
|---|---|---|---|---|
| Initial | v0.3.0 | v0.3.0 | — | TypeScript SDK ships with the image. |
| New SDK | v0.5.0 | v0.5.0 | v0.5.0 | Python SDK joins at the current image version. |
| Patch | v0.5.1 | v0.5.1 | v0.5.1 | All artifacts bump together. |
If your Docker image is at v0.5.1, install SDK v0.5.1 — same version, guaranteed compatibility.
Available SDKs
Pick the SDK that matches your running Docker image version.
TypeScript
- Package:
nexo-client
bash
npm install @emanuelepifani/nexo-clientPython
- Package:
nexo-client
bash
pip install nexo-clientOr with uv:
bash
uv add nexo-client