TabbyAPI

OpenAI-compatible API server for ExLlamaV3, built to run EXL3 quantized models on local NVIDIA GPUs.

Open SourceSelf HostedOffline CapableGPU Required (6GB+ VRAM)
0.0 (0)

About

Built by kingbri, Splice86, and turboderp, this FastAPI server puts an OpenAI-style HTTP API in front of the ExLlamaV3 inference library, so OpenAI-compatible clients can use models on your own GPU. It loads EXL3 quantized weights, which the authors recommend, or plain FP16 and BF16 checkpoints; the older ExLlamaV2 backend, and with it EXL2 and GPTQ support, was removed in mid-2026. Features include continuous batching with paged attention on Ampere and newer NVIDIA cards, speculative decoding with a draft model, tool calling, JSON schema, regex, and EBNF constrained output, Jinja2 chat templates, model swapping over the API, Hugging Face downloads, an embeddings endpoint through infinity, and AI Horde participation. You need an NVIDIA GPU (Turing or newer; Volta is rejected) and Python 3.10 up to 3.14, or the published CUDA Docker image; ROCm support arrives with the next ExLlamaV3 release. The authors call it a rolling-release hobby project, not a production server. Code is AGPL-3.0, so modified versions offered as a network service must share source. Suited to enthusiasts fitting large quantized models onto consumer GPUs.

Should you use TabbyAPI?

Pick it when

You run quantized models through the ExLlamaV2 or ExLlamaV3 backends on consumer NVIDIA GPUs for yourself or a handful of users, and want the official ExLlama API server with streaming, function calling, and OpenAI-style endpoints.

Look elsewhere when

Skip it for real production load, which its maintainers say it is not aimed at, or if AGPL-3.0 is a problem for your product. For many concurrent users use vLLM or SGLang; for CPU or Apple hardware use llama.cpp or Ollama.

Alternatives to TabbyAPI

  • ExLlamaV2

    The underlying library for scripting directly in Python, but the repository is archived; TabbyAPI is the maintained way to serve it.

  • Aphrodite Engine

    Also serves EXL2 to chat front ends with vLLM-style batching for more concurrent users, under the same AGPL-3.0 license.

  • Kobold.cpp

    Runs GGUF models with CPU offload and a bundled web UI, so it handles models larger than your VRAM, also under AGPL-3.0.

  • vLLM

    Apache-2.0 and built for many concurrent users, but needs about 16 GB of VRAM and does not load EXL2 files.

Reviews (0)

Leave a Review

No reviews yet. Be the first to review!