Skip to main content

Rightsize

Quantize and fit any model to your hardware. Pick a model, pick your hardware, get a ranked plan with the quantization, runtime and framework that fit, plus the commands to make it happen.

Status: placeholder release 0.0.1. The package name is reserved; the engine is being built feature by feature. See docs/plans for the roadmap and each feature's plan. Nothing here estimates anything yet.

The problem

Running a model on your own hardware today means choosing a fine-tuning framework, a quantization toolkit, a format and a runtime by hand, then finding out by out-of-memory error whether the combination fits. Calculators tell you the VRAM for one LLM; fine-tuning UIs run a job that then OOMs; Hub badges compare file sizes. Nothing joins fine-tune box + target device + task into a ranked, runnable answer.

What Rightsize will do

Two flows, one engine, five model families (LLM/VLM, diffusion, audio, vision, embeddings):

  • Hardware-first. "I have an RTX 4070 to train on and want to run on a MacBook Air 16 GB for coding help." Rightsize returns ranked models with the quant and framework for each stage.
  • Model-first. "I want Qwen3 14B." Rightsize returns what it needs to fine-tune (LoRA/QLoRA/full) and to run, the quant per runtime, and the cheapest cloud GPU if your box is too small.

Every answer carries a memory breakdown, a speed estimate, a confidence, the formula used, and the rules that fired with their source URLs. Every plan renders the actual commands for the chosen toolkit (llama.cpp, Unsloth, Axolotl, MLX, optimum, diffusers, whisper.cpp and more).

Surfaces: Python SDK, CLI with --json, MCP server so agents can call it.

How it stays light

  • The core depends on httpx, pydantic and pyyaml only. No torch, no transformers. Enforced in CI.
  • Hardware tables, quant tables, rules and recipes are versioned data, not code.
  • Frameworks are declarative recipes that render commands. Running them is an opt-in extra (rightsize[unsloth], rightsize[llamacpp], ...), loaded lazily.
  • Model metadata is fetched on demand from safetensors and GGUF headers (a few KB) and cached.

Install

pip install rightsize        # or: uv add rightsize
rightsize --version

Roadmap

Feature Plan Status
Competitor landscape 00-competitors research done
F1 Model catalog F01 planned
F2 Hardware DB + detection F02 planned
F3 Fit engine F03 planned
F4 Rules + ranking F04 planned
F5 Framework registry + recipes F05 planned
F6 SDK / CLI / MCP F06 placeholder CLI
F7 Cloud fallback F07 planned
F8 Execution + eval gate F08 phase 2
F9 Calibration loop F09 phase 2
F10 Cloud provider connectors F10 phase 3

Contributing

See CONTRIBUTING.md. Adding a framework means adding a recipe file, not code.

License

Apache-2.0. See LICENSE.

Release files for rightsize 0.0.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for rightsize 0.0.1
File Size Uploaded
rightsize-0.0.1.tar.gz 14.5 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for rightsize 0.0.1
File Interpreter ABI Platform
rightsize-0.0.1-py3-none-any.whl Python 3 none any Details

Total release size: 30.3 kB

Release files / rightsize-0.0.1.tar.gz

Download URL rightsize-0.0.1.tar.gz
Size 14.5 kB
Tags Source
SHA-256 checksum
How to use checksums
da3d28fc3e5abaad74dd37f721cd9b9a42f228a2967b881d4c38b1c20b088aa0
BLAKE2b-256 checksum
How to use checksums
cde9415d76a54d11c0d9c1a6b5dd257e4d2685da1d22fc8f7ee2fd928f49e177
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 25, 2026.

Transparency log

Release files / rightsize-0.0.1-py3-none-any.whl

Download URL rightsize-0.0.1-py3-none-any.whl
Size 15.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
cb76cf80ab63981c12957bc72aaee3f53b96b7c269fdbdc3aaa321567a201070
BLAKE2b-256 checksum
How to use checksums
1650dd15beddc96c25e28ab1a54b75b341943d61e1f112c8f74fda285f469ed4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 25, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.0.1 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page