verifier.org

best 9 tools for running llms locally

ranked on what the licence file says as much as on how well they run — because in this category being called open source and being open source have come apart.

last reviewed 27 jul 2026 · 9 tools tested ·list curated by Onur Ozcanxin

the short version
best overallJananyone who wants ollama's convenience without wondering which half of it is open.92/100runner-upllama.cppanyone comfortable at a terminal, and anyone who wants the newest model architecture the week it lands.90/100

every tool here is free to download and most are described as open source in every roundup you'll find. we read the licence file in each repository, and of the nine, only four are unambiguously open with no strings: jan, llama.cpp, gpt4all and localai. the rest carry something the summaries don't mention.

two are simply proprietary. lm studio is closed source under element labs' terms, which license free use 'solely for your personal and/or internal business purposes' and forbid redistribution or offering it as a service — it wraps open engines, llama.cpp and apple's mlx, but the app itself is not open. msty publishes no licence text at all that we could find, sells a $149-a-year tier, and is still described as open source in community posts from 2024.

ollama is the one most people would get wrong. its cli, engine and server are mit, and the desktop gui that most users actually interact with has shipped closed-source since late 2025, alongside a move into hosted cloud models. 'ollama is the open one' is half true and the half that's false is the half you click on.

the subtlest case is open webui, the browser front-end layered on top of most of this list. its licence is a modified bsd-3-clause with a branding clause: you may use it commercially only if you keep open webui's branding, unless you stay under 50 users in any rolling 30 days or buy an enterprise licence. it is source-available, modifiable, and not an osi-approved open-source licence — and it is called open source constantly.

advertisement
  1. 1

    Jan

    gui, server and inference engine all apache 2.0 — the only tool here where every layer is genuinely open.

    92/100

    verdictthe cleanest answer in the category since ollama's gui went closed — smaller and less polished, and the only one with nothing to explain.

    best for
    anyone who wants ollama's convenience without wondering which half of it is open.
    price
    free
    pricing note
    apache 2.0 across the whole stack including its own cortex engine; no paid tier, no commercial restriction
    free tier
    yes
    licence
    apache 2.0
    open source
    fully — all layers
    interface
    gui + local server
    backends
    cuda, metal, vulkan
    price
    free

    gui, local openai-compatible server and the cortex inference engine underneath are all apache 2.0 in the same repository. of the nine tools here that is a claim only jan, llama.cpp, gpt4all and localai can make, and jan is the only one of those four that is also a finished desktop application.

    practically it does what you want: cuda, metal and vulkan backends, gguf models, an openai-compatible endpoint so existing code points at it unchanged, and installers for macos, windows and linux.

    the honest limitation is maturity. the model library is smaller than ollama's, the interface is less polished than lm studio's, and it has less momentum than either. it gained ground through 2026 largely because ollama's licensing drift pushed people to look, which is a thin reason to lead a category and a real one to exist.

    pros
    • +apache 2.0 across gui, server and engine
    • +no commercial-use restrictions of any kind
    • +openai-compatible local server
    • +cuda, metal and vulkan support
    cons
    • smaller model library than ollama
    • less polished than lm studio
    • less momentum and a smaller community
  2. 2

    llama.cpp

    mit, and the engine most of this list is quietly built on top of.

    90/100

    verdictthe actual software doing the work in ollama, lm studio, jan and koboldcpp — unbeatable on licence, backends and speed of support, and not a product for most people.

    best for
    anyone comfortable at a terminal, and anyone who wants the newest model architecture the week it lands.
    price
    free
    pricing note
    mit licence, no restrictions of any kind; the reference implementation the wrappers wrap
    free tier
    yes
    licence
    mit
    open source
    fully
    interface
    cli + server + minimal web ui
    backends
    cuda, metal, rocm, vulkan, sycl
    price
    free

    mit, no conditions, and the widest hardware support here: cuda, metal, rocm/hip, vulkan, sycl and cpu, on desktop, mobile and embedded builds. it is also first to support new model architectures and quantisation formats, usually within days, which is why every wrapper on this list depends on it.

    it ships a cli, a server with an openai-compatible api, and a deliberately minimal built-in web ui. that is enough to run anything, and it is not an experience most people want as their daily driver.

    the reason to know this entry exists even if you never install it directly: when you compare 'ollama versus lm studio versus koboldcpp' on speed, you are mostly comparing the same c++ code with different paint. the differences that matter between those tools are licence, interface and model management, not inference.

    pros
    • +mit with no conditions at all
    • +widest backend support of anything here
    • +first to support new architectures and quant formats
    • +runs on desktop, mobile and embedded targets
    cons
    • no polished first-party gui
    • cli and build flags assume comfort with a terminal
    • not an end-user product on its own
  3. 3

    Ollama

    the easiest way in, and only partly the open-source project everyone believes it is.

    85/100

    verdictbest onboarding in the category and a licence story that has quietly split in two — the part you type is mit, the part you click is not.

    best for
    getting a model running in one command, which it still does better than anything else.
    price
    free
    pricing note
    mit covers the cli, engine and server; the desktop gui has shipped closed-source since around november 2025, and hosted cloud models are billed separately
    free tier
    yes
    licence
    mit (cli/engine only)
    open source
    partly — gui is closed
    interface
    cli + server + closed gui
    backends
    cuda, rocm, metal, partial vulkan
    price
    free; cloud models billed

    `ollama pull` and `ollama run` are why local models became approachable to people who don't build software, and the model library remains the largest and best-curated here. cuda, rocm, metal and partial vulkan, with an openai-compatible server that most local tooling assumes by default.

    the licensing has drifted. the cli, engine and server are mit and remain so. the desktop gui merged into the main distribution around november 2025 without an open licence, so the interface most casual users interact with is closed. the company has also added hosted cloud models on a usage basis, which is a reasonable business and a departure from the project's origins.

    none of that makes it a bad tool — it is still the fastest path from nothing to a running model. it makes 'ollama is the open one' a claim that needs the qualifier this page exists to supply.

    pros
    • +fastest zero-to-running-model experience anywhere
    • +largest and best-curated model library
    • +mit cli, engine and server
    • +the de facto openai-compatible local endpoint
    cons
    • the desktop gui is closed source since late 2025
    • hosted cloud models are a paid departure from local-only
    • gguf via its own registry rather than arbitrary local files
    • reputation for openness now outruns the licence
    advertisement
  4. 4

    LM Studio

    the best desktop experience here, and unambiguously proprietary software wrapped around open engines.

    82/100

    verdictgenuinely the most refined tool in the category and the clearest example of its central problem — it appears in every 'best open source local llm tool' list and is not open source.

    best for
    apple silicon users who want native mlx performance and a polished app, and don't need to ship anything built on it.
    price
    free
    pricing note
    proprietary; free use licensed solely for personal or internal business purposes, no redistribution or offering as a service; paid cloud credits and a bionic pass tier exist
    free tier
    yes
    licence
    proprietary
    open source
    no
    interface
    gui + local server
    backends
    cuda, metal/mlx, vulkan, rocm
    price
    free; paid cloud tiers

    the product case is strong. it bundles both llama.cpp and apple's mlx runtime, so on apple silicon you get native mlx rather than a port, and it configures hardware-aware settings automatically instead of making you guess at layer offloads. gguf and mlx formats, cuda, metal, vulkan and rocm, and an openai-compatible server.

    the licence is a flat contradiction of its reputation. element labs' terms grant free use 'solely for your personal and/or internal business purposes', prohibit resale, redistribution and offering it as a service to third parties, and forbid integrating anything that would oblige the app's own code to be opened. it is closed software that wraps open engines.

    that matters unevenly. for an individual running models on a laptop it changes nothing. for anyone building a product, embedding it in a workflow they sell, or needing to audit what runs on their machine, it is the whole answer. a paid pay-as-you-go tier for hosted third-party models has also been added, moving it beyond purely local inference.

    pros
    • +native mlx runtime on apple silicon, not just llama.cpp
    • +most polished interface with automatic hardware-aware settings
    • +gguf and mlx formats, four gpu backends
    • +openai-compatible local server
    cons
    • fully proprietary despite near-universal 'open source' framing
    • free use limited to personal or internal business purposes
    • no redistribution or offering it as a service
    • added paid cloud credits for hosted models
  5. 5

    LocalAI

    mit, container-native, and the only one here that serves text, images and audio behind one openai-compatible endpoint.

    78/100

    verdictthe right tool if you want infrastructure rather than an app — one mit-licensed endpoint covering more modalities than anything else here.

    best for
    self-hosting a drop-in openai replacement for a team or a homelab, not for chatting on a laptop.
    price
    free
    pricing note
    mit licence, no restrictions; docker-first deployment rather than a desktop installer
    free tier
    yes
    licence
    mit
    open source
    fully
    interface
    server + optional web ui
    backends
    cuda, rocm, vulkan, limited metal
    price
    free

    localai exposes an openai-compatible api spanning chat, image generation and audio, so a codebase written against openai can be pointed at it wholesale rather than per-model. gguf plus onnx and diffusers-family formats, cuda, rocm, vulkan and limited metal.

    it is mit with no conditions, and docker-first, which tells you the intended audience: this is something you deploy, not something you install and click.

    that framing is also the limitation. there is no native desktop app, setup is meaningfully more work than ollama or jan, and a casual user wanting to try a model on their laptop will find it heavier than the job requires.

    pros
    • +mit with no restrictions
    • +one endpoint for text, image and audio models
    • +genuine drop-in openai api replacement
    • +container-native and easy to run on a server
    cons
    • no native desktop gui
    • docker-first setup is heavier than rivals
    • aimed at developers and operators, not casual users
    • metal support is limited compared to cuda
  6. 6

    GPT4All

    mit, with local document chat built into the free app instead of sold as a feature.

    74/100

    verdictunrestricted mit and the easiest local document chat here — on a project whose development pace we could not confirm is keeping up.

    best for
    chatting with your own files locally without assembling a rag pipeline.
    price
    free
    pricing note
    mit licence, no restrictions; localdocs rag included in the free gui with no extra setup
    free tier
    yes
    licence
    mit
    open source
    fully
    interface
    gui + cli + server
    backends
    cuda, vulkan, metal, cpu
    price
    free

    localdocs is the reason to pick it: point the app at a folder and ask questions about its contents, entirely locally, with no vector database to stand up and no configuration. rivals either omit this or treat it as an advanced feature.

    the licence is mit with no conditions, the gui is qt-based and available on macos, windows and linux, and there are python bindings and a local server alongside cuda, vulkan, metal and cpu backends.

    our reservation is about momentum rather than terms. we could not confirm nomic's current release cadence from a primary source, and the feature and model-support pace visibly trails ollama, lm studio and jan. for a tool you rely on, that's worth checking before committing.

    pros
    • +mit with no restrictions
    • +localdocs rag built into the free gui
    • +python bindings and a local server included
    • +cuda, vulkan, metal and cpu backends
    cons
    • release cadence could not be confirmed from a primary source
    • model and feature support trails the leaders
    • interface is dated next to lm studio
  7. 7

    KoboldCpp

    one portable binary, no install, and an agpl licence that obliges you to share modifications you host.

    72/100

    verdictgenuinely open with the strictest obligations here — the copyleft cuts against companies rather than users, which is the opposite of everyone else's catch.

    best for
    creative writing and roleplay, and anyone who wants zero installation footprint.
    price
    free
    pricing note
    agpl-3.0 — free and open, but running a modified build as a network service requires publishing your changes
    free tier
    yes
    licence
    agpl-3.0
    open source
    fully, with copyleft
    interface
    portable binary + web ui
    backends
    cuda, rocm, vulkan, cpu
    price
    free

    it ships as a single dependency-free executable bundling a server and the kobold lite web ui. no installer, no runtime, no package manager — download and run. for a category where setup friction is the main barrier, that is a real design achievement.

    the feature set leans towards long-form fiction and roleplay: memory, world info, instruct and chat modes, all built around keeping a long narrative coherent rather than answering one-off questions. cuda, rocm, vulkan and cpu via its own llama.cpp fork.

    the licence is agpl-3.0, and the direction of its restriction is worth understanding. it is unambiguously open source — but if you modify it and run it as a network service, you must publish your modified source. for an individual that obligation never triggers. for a company building on it quietly, it is the strictest term on this page.

    pros
    • +single portable executable, no installation
    • +genuinely open source under agpl-3.0
    • +purpose-built for long-form writing and roleplay
    • +cuda, rocm, vulkan and cpu backends
    cons
    • agpl obliges publishing modifications you host as a service
    • interface is rougher than the consumer-focused tools
    • narrower appeal outside creative writing
    • recent development activity unconfirmed
  8. 8

    Open WebUI

    the front-end everyone pairs with ollama, under a licence that caps you at fifty users unless you keep its branding.

    68/100

    verdictthe most capable local chat interface there is, and the subtlest licensing trap in the category — source-available, endlessly called open source, and not.

    best for
    individuals and small teams who will keep the branding and stay under the user threshold.
    price
    free under 50 users
    pricing note
    modified bsd-3-clause with a branding clause; commercial use requires keeping open webui branding unless you stay under 50 users per rolling 30 days or buy an enterprise licence
    free tier
    yes
    licence
    modified bsd-3 + branding clause
    open source
    no — source-available
    interface
    web front-end, needs a backend
    backends
    whatever it connects to
    price
    free under 50 users; enterprise above

    as a product it is excellent: the most full-featured browser front-end for local models, actively developed, and it pairs with ollama, llama.cpp, localai or any openai-compatible backend. for most people running models locally with a nice interface, this is the interface.

    the licence is a modified bsd-3-clause with an added branding clause. you may use it commercially only if open webui's branding stays intact — unless your deployment stays under 50 users in any rolling 30-day period, you obtain written permission, or you sign a paid enterprise licence. removing the branding without one is defined in the licence as a material breach.

    that is a source-available licence with a genuine commercial restriction, not an osi-approved open-source licence, and it is the one most likely to catch a company out — because the code is on github, modifiable, and described as open source almost everywhere including by people deploying it at work.

    pros
    • +most full-featured local chat front-end available
    • +works with ollama, llama.cpp, localai and any openai-compatible api
    • +actively developed with a large community
    • +free and unrestricted below the user threshold
    cons
    • not an osi-approved open-source licence
    • commercial use above 50 users needs branding retention or a paid licence
    • removing branding is a defined material breach
    • widely and wrongly described as plainly open source
  9. 9

    Msty

    a nice split-screen model comparison tool that publishes no licence at all.

    60/100

    verdictthe only tool here where we could not find a licence of any kind — and it is still called open source in community posts, which is precisely the confusion this page is about.

    best for
    comparing two models' answers side by side in one window, if the licensing doesn't matter to you.
    price
    free
    pricing note
    freemium — studio free, aurum add-on $149/year or $349 lifetime; no licence text located on the vendor's own pages
    free tier
    yes
    licence
    none published
    open source
    no
    interface
    gui
    backends
    unconfirmed
    price
    free; $149/yr aurum

    the distinctive feature is genuine: a split-chat interface that runs the same prompt against multiple models side by side, plus local rag over your own documents, in one polished window. nothing else here does the comparison view as cleanly.

    the licensing is a blank. we found no licence file, no terms naming a licence, and no public source repository — only a pricing page from cloudstack, llc listing a free studio tier and an aurum add-on at $149 a year or $349 for a lifetime seat. older community posts from 2024 describe it as open source, and there is no current evidence supporting that.

    we also could not confirm its gpu backends from msty's own documentation; third-party sources describe a llama.cpp-based engine, which is plausible and unverified. for a tool asking to run on your machine and read your documents, publishing neither a licence nor an architecture is a lot to ask on trust.

    pros
    • +side-by-side multi-model comparison in one window
    • +local rag over your own documents
    • +macos, windows and linux builds
    • +usable free tier
    cons
    • no licence text published anywhere we could find
    • no public source repository despite being called open source
    • gpu backends unconfirmed from vendor documentation
    • paid tiers at $149/year or $349 lifetime

how this ranking was made

the licence field is taken from the licence file in each project's own repository, or from the vendor's terms page where no repository exists. not the readme, not the marketing page, not a roundup. where a tool has separate components — ollama's cli versus its gui — we say which is covered and which isn't.

'open source' is reported as fully, partly or no, and the entry says what's closed when the answer is partly. source-available licences with commercial restrictions are marked as not open source, because that is what they are, however modifiable the code is.

we publish no throughput benchmarks. inference speed on the same model is dominated by the engine underneath — and most of these tools run llama.cpp — so a tools comparison measuring tokens per second would mostly be measuring the same code twice. what we compare instead is which backends and formats each supports, since that determines whether it runs well on your hardware at all.

restrictions that cut the other way are reported too. koboldcpp is agpl-3.0, which is genuinely open but obliges anyone running a modified build as a network service to publish their changes — a real constraint for a company, and the opposite failure mode from a proprietary licence.

where a project's current activity could not be confirmed from a primary source we say so rather than inferring decline from silence.

our general methodology and disclosures →
was this useful?