Enterprise DNAEnterprise DNA

Open Source

piqc

Free, read-only GPU waste scanner for Kubernetes inference clusters, by Paralleliq. Finds idle GPUs, oversized GPU tiers and wasted capacity in vLLM deployments.

Our verdict

Not reviewed yet

We have not reviewed piqc yet

No one at Enterprise DNA has checked this listing against its sources. The description comes from public listings gathered automatically. Any fact below shows where it came from and when it was last checked.

How we review records

From the listing

About piqc

piqc is a free, read-only GPU waste scanner for Kubernetes inference clusters. It finds idle GPUs, oversized GPU tiers, and wasted capacity in vLLM deployments. The tool is written in Python and published as an open-source community project by Paralleliq.

Best for

Teams running vLLM on Kubernetes who want a free, safe way to spot GPU waste

Use cases

  • Detect idle GPUs in Kubernetes inference clusters
  • Identify oversized GPU tier allocations
  • Audit vLLM deployments for wasted capacity

Notes

32 stars on GitHub. Last updated 2026-10-04. Licensed Apache-2.0.

Pros

  • Read-only, so it poses no risk to running workloads
  • Free and open source
  • Focused specifically on GPU waste in vLLM deployments

Cons

  • Limited to Kubernetes and vLLM environments
  • Read-only, so it does not automatically reclaim wasted GPUs
  • Small community with 32 stars, indicating early-stage adoption

Key facts

What we have checked

Days since the last commit
5
Checked GitHub
GitHub forks
2
Checked GitHub
GitHub stars
32
Checked GitHub
Days to a first reply on issues
109.4
Checked GitHub
Open issues
11
Checked GitHub
Releases in the last 90 days
0
Checked GitHub

Each value shows when we last confirmed it and where it came from. Values we have not confirmed are left out, never guessed.

Stars and usage

How piqc is growing

GitHub stars

32 to 32

stars. 5 Oct 2026 to 7 Nov 2026, 3 readings.

Source: GitHub. Checked .

Health and security

Is piqc looked after, and what do its setup files show

Health score

38 out of 100

Does someone look after this repository? It does not say the code is good or safe. Worked out from GitHub signals checked . How it is worked out

PartPointsWhat we saw
Recent activity30 of 30Last push 5 days ago
Releases0 of 150 releases in 90 days
Issue replies0 of 20First reply in 109.4 days (median)
Maintainer0 of 15Owned by a single user
Official sourceNot countedMCP servers only

Sources

Where this comes from

  • GitHubRegistry

    Checked · Days since the last commit, GitHub forks, GitHub stars, Days to a first reply on issues, Open issues, Releases in the last 90 days

A source shows what was published when we checked it. It does not certify security, performance or a working installation. Read our method.

Changelog

What changed

No changes recorded yet. Releases, price changes and deprecations appear here, with their dates, once we track them for this record.

Free 27-page guide

Get the free Developer’s Field Guide

A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.

Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.

No spam. Unsubscribe any time.