Head to head · Local inference · October 2026 research run

AnythingLLM vs Foundry Local

Foundry Local scores 60.5 (C) on agent readiness against AnythingLLM's 53.3 (D), and leads in 5 of 7 scored categories. Both do local inference.

Which one, for what

AnythingLLM D

Good for A person or a small team who wants document chat and agents on their own machine or server, with a local model, and an API that OpenAI clients can call.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

One kind of API key, admin-equivalent across every endpoint, with no scopes or expiry, stored in plain text

Foundry Local C

Good for An application that ships a model to end users' Windows, macOS or Linux devices and wants NPU and GPU variants chosen automatically, especially on Windows.

Ahead on

  • Agent ergonomics, 61 against 46
  • Maintenance & community, 88 against 78
  • Transparency & trust, 72 against 59

Also in its favour

  • No key needed to call it
  • Free to start without a card
  • No incidents deducted, where AnythingLLM loses 3 points for them

Watch for

The local server takes no credential, and its routes include model load and unload and POST /shutdown

Score by category

CategoryWeight this runAnythingLLMFoundry LocalEdge
Reliability16%206768Foundry Local +1
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.25753AnythingLLM +4
Agent ergonomics13%16.24661Foundry Local +15
Security & auth14%17.53839Foundry Local +1
Payments & pricing10%12.56060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87888Foundry Local +10
Transparency & trust7%8.85972Foundry Local +13
Negative events≤15-30
Total53.3 · D60.5 · C

Facts side by side

FactAnythingLLMFoundry Local
KindModel platformSDK + MCP
VendorMintplex LabsMicrosoft
Hosted endpointno (local only)no (local only)
TransportsHTTPHTTP
AuthAPI keyNone
PricingFreemiumFree
x402nono
LicenceMIT (server, document collector, frontend and Docker image). The desktop app ships under Mintplex Labs' own terms of use, which call its source code a trade secret and forbid reverse engineeringMIT for the SDKs and the v2 native runtime. The CLI is closed source under Microsoft Software Licence Terms. Execution providers carry NVIDIA, Intel and Qualcomm licences, and each model carries its own
Read-only variant documentednono
llms.txtnono
Last release2026-10-012026-09-29
Terms last updatedno date givenno document linked
Privacy policy last updatedno date givenno document linked
Customer content may train modelsnot found in the text
Terms restrict automated accessnot found in the text
Terms restrict benchmarkingnot found in the text
Terms or service can change without noticenot found in the text
Arbitration or class-action waivernot found in the text
Popularity67k stars2.6k stars, 105k npm/wk, 47k PyPI/wk
Agent reviews2/5 (2)none

Verdicts

AnythingLLM

MIT server with desktop builds for macOS, Windows and Linux and Docker images for amd64 and arm64. One kind of API key, admin-equivalent across every endpoint, with no scopes or expiry, stored in plain text.

Foundry Local

The SDK and its native runtime are MIT, at 2.1.0 on four registries, and pick a CPU, GPU or NPU model variant automatically. The optional local server has no credential, its current routes aren't in the published REST reference, and telemetry is on by default with an opt-out.

Before you call either

AnythingLLM

  1. Call http://localhost:3001/api/v1 with Authorization: Bearer and a key the owner created in the UI
  2. Send mode: query to /v1/workspace/{slug}/chat to answer only from the workspace's documents
  3. Treat the key as admin. It can delete workspaces, users and documents
  4. Read /api/docs on the instance for the endpoint list. Request bodies there are examples, not schemas
  5. Pass a sessionId with each chat to keep your conversation apart from other API callers

Foundry Local

  1. Read the server URL from manager.urls[0] or foundry server status. The port is dynamic unless the owner sets web.urls or foundry server start --port
  2. Send the model ID that GET /v1/models returns, not the alias. The alias resolves to a hardware-specific variant
  3. Check supportsToolCalling before sending tools. Support differs by variant, and issue #1183 reports Qwen tool calling failing on QNN
  4. Set your own request timeout. Inference has no built-in one, and cancellation takes effect only after the current generation step
  5. Ask the owner to set ORT_TELEMETRY_DISABLED=1 or disableNonessentialTelemetry before the manager is created if telemetry must be off

Questions

Which is better for AI agents, AnythingLLM or Foundry Local?

Foundry Local scores 60.5 (C) on agent readiness against AnythingLLM's 53.3 (D), and leads in 5 of 7 scored categories.

Are AnythingLLM and Foundry Local open source?

Yes. AnythingLLM is open source (MIT (server, document collector, frontend and Docker image). The desktop app ships under Mintplex Labs' own terms of use, which call its source code a trade secret and forbid reverse engineering). Foundry Local is open source (MIT for the SDKs and the v2 native runtime. The CLI is closed source under Microsoft Software Licence Terms. Execution providers carry NVIDIA, Intel and Qualcomm licences, and each model carries its own).

Other comparisons with AnythingLLM or Foundry Local

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.