Hardware-aware fine-tuning for open models from the Hugging Face Hub, with browser, terminal and notebook interfaces.
ModelForge reads your GPUs, works out how large a model fits, picks a training recipe for your goal, and runs it while you watch the loss come down. It shows its reasoning before anything starts, so you don't find out at step 40 that the run doesn't fit in memory.
- Hardware-aware planning. Total VRAM, the strategy's memory overhead and a per-parameter cost set a ceiling on model size. ModelForge picks full fine-tuning, LoRA or QLoRA (8-bit or 4-bit) to match.
- A recipe for each goal. Supervised fine-tuning (SFT), preference training (DPO) and reinforcement training (GRPO), plus native trainers for summarization and extractive QA.
- Model recommendations. Searches the Hub for popular models of the right type that fit your hardware, or validates any model ID you enter.
- Multi-GPU. Data parallel by default, switching to FSDP automatically when a full fine-tune is too large for one card.
- Live runs. Streamed training logs, checkpoints you can resume from, and TensorBoard logging.
- Playground. Chat with a finished model or any checkpoint in the browser, even while another run is training.
ModelForge needs Python 3.13 or newer. Real training needs an NVIDIA GPU with CUDA. Apple Silicon (MPS) and CPU-only machines work, but only with small models.
pip install modelforge-finetuning
# Optional extras: the terminal wizard, and Liger kernels for CUDA
pip install "modelforge-finetuning[cli,gpu]"Per-OS instructions, including PyTorch with CUDA, are in the installation guides.
modelforge runThis starts the server and opens the browser console. The link it prints includes a one-time token that connects your browser. On a remote machine, use modelforge run --no-browser --host 127.0.0.1 and connect through an SSH tunnel.
For gated models such as Llama, accept the licence on the model's Hub page, then log in once with hf auth login.
| Interface | Command | Best for |
|---|---|---|
| Browser console | modelforge run |
Most people |
| Terminal wizard | modelforge cli |
Headless servers over SSH (needs [cli]) |
| Notebook | modelforge-nb |
Jupyter and Colab |
The Quick Start guide walks through a first run.
Full documentation is at modelforge-finetuning.readthedocs.io. A shorter version ships inside the app at /app/docs.
- What's new in v4 and migrating from v3
- Dataset formats
- How planning works
- Training strategies
- REST API
- Troubleshooting
Building or installing from a source checkout needs Node.js and npm, because the browser UI is compiled into web/frontend_dist/. That directory isn't committed.
git clone https://github.com/ForgeOpus/ModelForge.git
cd ModelForge
uv sync --extra dev
python scripts/build_frontend.py # or, from web/frontend: npm ci && npm run build
uv run modelforge run --no-browserpip wheel ., python -m build and uv build run the frontend build automatically, and fail if Node.js is missing, so a wheel is never published without a UI. Installing an already-built wheel doesn't need Node.
See the development guide and DEVELOPER_GUIDE.md for the codebase tour, tests and the release process.
Contributions are welcome. Read the contributing guide and the code of conduct, and report bugs or request features through GitHub issues.
ModelForge is released under the BSD 3-Clause License.
