vllm-project / vllm-project/aibrix
[Call for Adopters] Tell us how you use AIBrix 🚀
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.1k
- Forks
- 697
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 104
Description
🚀 Feature Description and Motivation
We’re collecting real-world AIBrix usage to help guide the roadmap and (optionally) showcase adopters on aibrix.ai and the README.
How we’ll use this
- Prioritize features based on real deployments
- Share anonymized stats and lessons learned
- (Optional) List your org/logo as an adopter
How to participate
Comment on this issue with the template below. Share only what you’re comfortable making public.
Template (copy/paste)
Organization / Project Name:
Website / Repo (optional):
Workloads & Impact
- Key AIBrix features in use: (StormService, P/D disaggregation, EP, KVCache, APA/HPA/KPA, heterogeneous routing, Lora, etc.)
- Top wins: (latency / cost / stability / ops)
- Pain points:
- feature requests:
Cluster Snapshot (optional but very helpful)
- GPU types: (e.g., H100 , L40S )
- Storage / cache: (KVCache L1/L2 backend, offload tiers, object store)
(Optional) Logo & Listing
- Consent to list your name/logo on aibrix.ai & README: Yes / No
- Logo link (SVG/PNG):
- Contact (optional): (email or GitHub handle)
Privacy note: If you prefer to share details privately, say so and we’ll reach out.
Thanks! Your input directly shapes AIBrix’s roadmap.
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 with the participation template in the issue and review the README and aibrix.ai references it names. Done means submitting the requested public usage details, feedback, and optional listing consent in a comment, or sharing privately as described.
Written by the indexing model from the issue text.
Assessment
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 30/100