badlogic/pi

CLI tool for managing vLLM deployments on GPU pods from Prime Intellect, Vast.ai, DataCrunch, etc.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 7 minutes ago
Added to GitGenius on June 2nd, 2026
Created on July 31st, 2025
Open Issues & Pull Requests: 1 (+0)
GitHub issues: Enabled
Number of forks: 17
Total Stargazers: 96 (+0)
Total Subscribers: 1 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 45.5 hours
Mean response time: 26.0 hours
90th percentile: 45.5 hours
Tracked items: 7

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 16 days
Stale 30+ days: 1
Stale 90+ days: 1

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

pi is a CLI tool for managing vLLM deployments on GPU pods from cloud providers like Prime Intellect, Vast.ai, and DataCrunch.

The tool solves the problem of quickly deploying large language models on rented GPU infrastructure without complex orchestration. It automates the setup process on clean Ubuntu pods by installing vLLM, Python, CUDA drivers, and dependencies in minutes. Once configured, it manages multiple concurrent model instances across available GPUs, automatically allocating them via round-robin assignment and supporting tensor parallelism for large models that span multiple GPUs. The resulting deployments expose OpenAI-compatible APIs, allowing existing client code to work without modification.

The tool is designed for individuals experimenting with open-weight LLMs for coding assistants and local AI workflows who lack sufficient local hardware. It requires only SSH access to a provisioned pod and a HuggingFace token for model downloads; users must create pods themselves through their chosen provider rather than relying on the tool for provisioning. The approach trades deployment sophistication for simplicity—it is not intended as an optimized production infrastructure but rather as a quick-start solution for developers wanting to run models on rented GPUs without Kubernetes, Docker, or manual configuration. The tool disables vLLM telemetry by default and exposes endpoints without authentication, reflecting a privacy-first but permissive security posture suitable for personal use.

Development activity shows consistent engagement with practical improvements to the deployment workflow. The project maintains active responses to issues and incorporates user feedback into feature refinements. Work focuses on expanding cloud provider support and improving GPU allocation logic rather than architectural overhauls. The codebase remains lean and focused on the core deployment and management problem, with recent changes addressing edge cases in multi-GPU scenarios and compatibility with newer GPU architectures.