selfhost.directory

The index of self-hostable projects — ranked, categorized and served with live updates.
Own your data and stop giving it to big tech.

Turbo-LLM logo

Self-host Turbo-LLM

v1.14.5

Local LLM platform running any engine with auto-tuning

ReleaseSource AvailableFSL-1.1-ALv2
npm install -g turbollm
Updated9 hours ago
LanguageTypescript
Setup difficultyModerate
MobileNative app
ThemeDark mode
Stars
285
CPU
Any modern CPU (x86_64 or ARM64)
Port
6996 (Main daemon HTTP API and web UI)
Requires
Llama.cpp-compatible engine
Chat screen in dark mode showing real generation speedChat screen in light mode showing real generation speedEngines screen in dark mode with hardware-fit marksEngines screen in light mode with hardware-fit marksModels screen in dark mode with measured tokens/sec and VRAM-fit verdictsModels screen in light mode with measured tokens/sec and VRAM-fit verdictsCustomize screen in dark mode with editable agents and skillsCustomize screen in light mode with editable agents and skillsCode screen in dark mode showing local coding agent sessionCode screen in light mode showing local coding agent session

What is Turbo-LLM?

TurboLLM is a self-hosted local LLM platform that runs any inference engine — llama.cpp, community forks, vLLM, MLX, KoboldCpp, llamafile, and more — auto-tuned to your GPU. It provides a polished web UI and both OpenAI- and Anthropic-compatible APIs, enabling tools like Claude Code to run against local models with one command. Key features include benchmark-based auto-tuning with VRAM-fit verdicts before you commit, actual generation speed measured on your machine, a model-loading gateway that automatically loads models when requested and keeps favorites ready, a local coding agent with LSP integration, MCP server integrations, ComfyUI GPU sharing, live hardware monitoring, and a native Android app. It runs via npm (npx turbollm), Docker with NVIDIA/AMD GPU support, or native installers on Windows, macOS, and Linux. The project is source-available under FSL-1.1-ALv2 (converting to Apache-2.0 after two years).

Should you self-host Turbo-LLM?

Turbo-LLM scores 48/100 on selfhost.directory (how scoring works) and ranks #19 of 25 in LLM Inference. It has 285 GitHub stars.

It shipped 33 stable releases in the past year. The latest, v1.14.5, came out on 4 October 2026. New versions land roughly every 1 days.

Setup is moderate: expect some configuration beyond a single command. It is FSL-1.1-ALv2-licensed and written mostly in Typescript.

Its closest alternative on selfhost.directory is AnythingLLM (88/100, 67 669 stars). It scores higher overall, so compare the two before you pick. See Turbo-LLM vs AnythingLLM side by side.

Features

  • Anthropic-compatible API
  • Any engine including community forks
  • Benchmark-based auto-tuning
  • ComfyUI GPU sharingExperimental, off by default
  • Live hardware monitoring
  • Local coding agent
  • MCP integrations
  • Model-loading gateway
  • Native Android appCurrently in closed/open testing
  • Offline First
  • OpenAI Compatible API
  • Real measured tokens/sec
  • Verifiable telemetry

Turbo-LLM README

How to install Turbo-LLM

Install Turbo-LLM with Docker

NVIDIA GPU with CUDA support, NVIDIA drivers, NVIDIA Container Toolkit
# Ubuntu / Debian example
curl -fsSL https://nvidia.github.io/libnvidia-container/gpgkey | \
sudo gpg --dearmor -o /usr/share/keyrings/nvidia-container-toolkit-keyring.gpg

curl -s -L https://nvidia.github.io/libnvidia-container/stable/deb/nvidia-container-toolkit.list | \
sed 's#deb https://#deb [signed-by=/usr/share/keyrings/nvidia-container-toolkit-keyring.gpg] https://#' | \
sudo tee /etc/apt/sources.list.d/nvidia-container-toolkit.list

sudo apt update
sudo apt install -y nvidia-container-toolkit

sudo systemctl restart docker

docker compose -f docker-compose-nvidia.yaml up -d

Requires NVIDIA GPU, drivers, and NVIDIA Container Toolkit

How to configure Turbo-LLM

  • --addr127.0.0.1:6996Full host:port override, e.g. 0.0.0.0:6996 for LAN sharing

    Full host:port override, e.g. 0.0.0.0:6996 for LAN sharing

    values: any host:port

  • --config~/.turbollm/config.jsonPath to a custom config file (its directory becomes the data dir)

    Path to a custom config file (its directory becomes the data dir)

    values: any file path

  • config.jsonMain configuration file located at ~/.turbollm/config.json

    Main configuration file located at ~/.turbollm/config.json

  • --no-openfalseStart without opening a browser window

    Start without opening a browser window

    values: true/false

  • --port6996Listen on a specific port (default: 6996)

    Listen on a specific port (default: 6996)

    values: any valid port

  • --print-tokenfalsePrint API token on startup (used in Docker)

    Print API token on startup (used in Docker)

    values: true/false

  • --stopfalseStop a running TurboLLM daemon

    Stop a running TurboLLM daemon

    values: true/false

Turbo-LLM releases & version history

FAQ

Why not MIT/Apache from day one?

FSL prevents a large vendor from re-skinning it as their own product while it's young, and the future grant guarantees the full open-source outcome anyway.

When does it become fully open source?

Each release converts to Apache-2.0 exactly two years after that release is published. The first public release shipped June 2026, so it converts in June 2028.

Can I fork it or redistribute it?

Yes — modify, fork, and redistribute freely for any permitted purpose; keep the license text and copyright notices with it.

What's the one restriction?

You can't take TurboLLM and ship it (or its functionality) as a competing commercial product or service.

Can I use it for free?

Yes. Personal use, internal business use, education, research, and self-hosting — including commercially, inside your company — are all free.

More in LLM Inference

Rate this project

Click to rate — no account needed.

0 comments

Posting as guest
Loading comments…