Project-HAMi/HAMi
Heterogeneous GPU Sharing on Kubernetes observed · 2026-08-28
Health v2 · maintenance only
95/100
- Activity 99
- Release rhythm 86
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.
- gap_med: 47
- age_days: 1814
- days_rel: 12
- days_push: 7
- n_releases_24m: 16
Adoption not part of the score
4438 stars · 794 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
HAMi (Heterogeneous AI Computing Virtualization Middleware) is a CNCF Incubating, Kubernetes-native GPU virtualization and scheduling middleware that lets multiple workloads share GPUs and other AI accelerators with hard memory/compute isolation. It works via device plugins, a mutating webhook, and a custom scheduler, supporting NVIDIA, Ascend, Cambricon, Hygon, and other vendors without application code changes.
Use cases
- share one GPU across multiple Kubernetes pods
- slice GPU memory for AI inference workloads
- schedule heterogeneous accelerators like NPU and MLU in Kubernetes
- prevent one pod from OOMing other tasks on a shared GPU
- improve GPU utilization in an AI cluster
- allocate fractional GPU resources (e.g. 1/2 or 1/4 of a card) to jobs
- monitor GPU memory and core usage across vendors
When to choose
- you run Kubernetes with expensive GPUs that are underutilized by exclusive allocation
- you need VRAM/compute isolation for shared GPUs without MIG-capable hardware
- you manage mixed-vendor accelerators (NVIDIA, Ascend, Cambricon, Hygon, etc.) and want one scheduling workflow
- you want device-aware scheduling policies like binpack, spread, or topology-aware placement
When to avoid
- you need hardware-level isolation guarantees such as NVIDIA MIG on A100/H100
- your cluster is not Kubernetes-based
- you only run a single workload per GPU and don't need sharing
- you require vendor-official support rather than a community middleware layer
Facets
service · maturity active
container-orchestration scheduling monitoring gpu-computing cloud-computing gpu-computing infrastructure-as-code machine-learning go self-hosted gpu-virtualization vgpu device-plugin gpu-sharing heterogeneous-accelerators cncf ai-infrastructure gpu-scheduling nvidia ascend cambricon containers kubernetes linux docker
7 sources
- readme: https://github.com/Project-HAMi/HAMi · fetched 2026-08-28 · 3b9fdd7bc80f
- homepage: https://project-hami.io · fetched 2026-08-29 · b7821d2f989b
- site_page: https://project-hami.io/docs/userguide/device-supported · fetched 2026-08-29 · 8754d0f64ad8
- site_page: https://project-hami.io/docs/core-concepts/gpu-virtualization · fetched 2026-08-29 · 136c47637cfa
- site_page: https://project-hami.io/docs · fetched 2026-08-29 · 47e99a283b4c
- site_page: https://project-hami.io/docs/get-started/deploy-with-helm · fetched 2026-08-29 · 5fe813d69a05
- site_page: https://project-hami.io/changelog · fetched 2026-08-29 · 8c9a7e085843
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| Project-HAMi/HAMi | main | 95 |
For agents
markdown · JSON · MCP: product_card(name="Project-HAMi/HAMi")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem