Add Node.js bindings (cuvs-node) to language support / integrations list
Nobody has claimed this yet.
- Dominant language
- Cuda
- Stars
- 854
- Forks
- 236
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 62
Description
Hi cuVS team,
We've built and open-sourced Node.js bindings for cuVS: cuvs-node.
cuvs-node provides native C++ N-API bindings to the cuVS C API, giving Node.js developers in-process GPU-accelerated vector search.
What's implemented:
- CAGRA (build, search, serialize, deserialize)
- IVF-Flat (build, search, serialize, deserialize)
- IVF-PQ (build, search, serialize, deserialize)
- Brute-force (build, search, serialize, deserialize)
- CAGRA to HNSW conversion (build on GPU, serve on CPU)
Status:
- 99 tests passing
- Verified on A10, A100 H100 GH200, B200
- Published on npm:
npm install cuvs-node - Apache-2.0 licensed
- Benchmarked at 733x faster index builds vs CPU (hnswlib-node) at 768d, 1M vectors on A100 SXM
Links:
- GitHub: https://github.com/638Labs/cuvs-node
- npm: https://www.npmjs.com/package/cuvs-node
- Blog: https://638labs.com/blog/2026-04-13-opensource-nvidia-cuvs-node-bindings/
We'd love to be listed alongside the other cuVS language bindings and integrations.
Happy to submit a PR updating the README or docs if that's preferred.
cheers
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the README or documentation page that lists cuVS language bindings and integrations, then compare its existing entry format with the cuvs-node links in this issue. The work is done when cuvs-node is listed with its repository or npm link and the documentation remains consistent with the surrounding entries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, node.js
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100