This release is a pre-release and may not be stable for production use.
vLLM RBLN Plugin
This repository provides the hardware plugin that enables vLLM on RBLN NPUs, including ATOM and REBEL.
Built on top of vLLM’s Plugin System, it allows seamless integration with the vLLM ecosystem and provides high-throughput, low-latency LLM serving on RBLN hardware. Our plugin supports a wide range of popular LLMs and continues to expand to support all features enabled in vLLM, including advanced attention mechanisms.
🚀 Getting Started
📋 Prerequisites
rebel-compileroptimum-rbln
⚙️ Installation
You can install this project using pip or from source.
Install via PyPI
Using uv
uv pip install vllm-rbln --extra-index-url https://wheels.vllm.ai/0.30.0/cpu --torch-backend cpu
Using pip
pip install vllm-rbln --extra-index-url https://wheels.vllm.ai/0.30.0/cpu --extra-index-url https://download.pytorch.org/whl/cpu
Or from source
Using uv
git clone https://github.com/rbln-sw/vllm-rbln.git
cd vllm-rbln
uv pip install -e .
Using pip
git clone https://github.com/rbln-sw/vllm-rbln.git
cd vllm-rbln
pip install -e . --extra-index-url https://wheels.vllm.ai/0.30.0/cpu --extra-index-url https://download.pytorch.org/whl/cpu
⚠️ Installing on Ubuntu 22.04 or Enterprise Linux 9
If installation fails with an error like the following, add the option below to your installation command:
vllm==0.30.0+cpu has no wheels with a matching platform tag
(e.g., `manylinux_2_35_x86_64`)
hint: Wheels are available for `vllm` (v0.30.0+cpu) on the following platforms:
`manylinux_2_39_aarch64`, `manylinux_2_39_x86_64`
This error means that the upstream vLLM CPU wheel requires a newer glibc version than your system provides.
The wheel requires glibc 2.39 or later and libstdc++ from GCC 14 or later (CXXABI_1.3.15). Ubuntu 22.04 (glibc 2.35, GCC 12) and Enterprise Linux 9 (RHEL, AlmaLinux, and Rocky Linux 9.x; glibc 2.34, GCC 11) do not meet these requirements.
The --find-links option makes compatible vLLM wheels from the vllm-rbln v0.12.0 release assets available to the installer:
--find-links https://github.com/RBLN-SW/vllm-rbln/releases/expanded_assets/v0.12.0
When using uv, also add --no-sources-package vllm to allow installation of the compatible wheel.
🛠️ Development setup
Building from source? See DEVELOPMENT.md for the uv dev workflow.
📚 Documentation
🤝 Contributing
We welcome all contributions! Whether it's reporting issues, proposing enhancements, or improving docs—your input helps make the project better.
See our CONTRIBUTING.md for more information.
📄 License
This project is licensed under the Apache License 2.0.
See the LICENSE file for more information.
📧 Contact
- Join discussions and get answers in our Developer Community
- Contact maintainers at support@rebellions.ai
1 maintainer
Metadata
1 maintainer
Release files for vllm-rbln 0.12.1a4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| vllm_rbln-0.12.1a4-py3-none-any.whl | Python 3 | none | any | Details |
Release files / vllm_rbln-0.12.1a4-py3-none-any.whl
| Download URL | vllm_rbln-0.12.1a4-py3-none-any.whl |
|---|---|
| Size | 647.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8418120b24af841396cbe94454f5b3dfb805cd99f3429d82e8fe527c1eb6a154
|
|
BLAKE2b-256 checksum How to use checksums |
4688d2ef05e980b4a96a7eb3433fb6e131ec741829113617bdd53947ffc8f8dd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Security for vllm-rbln 0.12.1a4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
