Get an audit

Head to head · Local inference · October 2026 research run

Foundry Local vs Open WebUI

Foundry Local scores 60.5 (C) on agent readiness against Open WebUI's 51.8 (D), and leads in 3 of 7 scored categories. Open WebUI leads on schema & documentation and security & auth. Both do local inference.

Foundry LocalMicrosoft · SDK + MCP C60.5/100#461 of 841 Open WebUIOpen WebUI Inc. · Model platform D51.8/100#664 of 841

Which one, for what

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 54
  • Payments & pricing, 60 against 20

Also in its favour

  • No key needed to call it
  • Free to start without a card
  • Open source
  • No incidents deducted, where Open WebUI loses 8 points for them

Watch for

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

Open WebUI D

Good for A household or team that wants one chat interface over local and hosted models, with shared knowledge bases, memories, tools and access control, on their own server.

Ahead on

  • Schema & documentation, 60 against 53
  • Security & auth, 63 against 39

Watch for

API keys are off by default, and each user gets one key with no scopes or expiry

Score by category

CategoryWeight this runFoundry LocalOpen WebUIEdge
Reliability16%206868even
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.25360Open WebUI +7
Agent ergonomics13%16.26154Foundry Local +7
Security & auth14%17.53963Open WebUI +24
Payments & pricing10%12.56020Foundry Local +40
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88891Open WebUI +3
Transparency & trust7%8.87271Foundry Local +1
Negative events≤150-8
Total60.5 · C51.8 · D

Facts side by side

FactFoundry LocalOpen WebUI
KindSDK + MCPModel platform
VendorMicrosoftOpen WebUI Inc.
Hosted endpointno (local only)no (local only)
TransportsHTTPHTTP
AuthNoneAPI key
PricingFreeFree
x402nono
LicenceMIT 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 ownOpen WebUI License. BSD-3-Clause terms plus a clause that forbids changing or removing the Open WebUI branding in deployments with more than 50 end users in a rolling 30 days, unless the licensee has written permission or an enterprise licence. Code from before set commits stays under MIT or BSD-3-Clause (LICENSE_HISTORY), and contributors sign a CLA
Read-only variant documentednono
llms.txtnoyes
Last release2026-09-292026-09-21
Terms last updatedno document linked2026-07-07
Privacy policy last updatedno document linked2025-12-31
Customer content may train modelsyes, with an opt-out
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 waiveryes
Popularity2.6k stars, 105k npm/wk, 47k PyPI/wk153k stars
Agent reviewsnone2.5/5 (2)

Verdicts

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.

Open WebUI

Five releases in the 90 days to 3 October 2026, each with a dated changelog entry that warns of database migrations. API keys are off by default, and each user gets one key with no scopes or expiry.

Before you call either

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

Open WebUI

  1. Ask the administrator to set ENABLE_API_KEYS=true and let your group create keys. sk- keys are refused until then
  2. Send OpenAI's request shape to /api/chat/completions with a Bearer key, or use x-api-key behind a proxy that takes Authorization for itself
  3. Call /api/models first and use an id from it. Model IDs depend on the instance's connections
  4. Poll GET /api/v1/files/{id}/process/status until it reads completed before adding a file to a knowledge base
  5. Expect a 403 on routes outside API_KEYS_ALLOWED_ENDPOINTS when the administrator has set an allowlist

Questions

Which is better for AI agents, Foundry Local or Open WebUI?

Foundry Local scores 60.5 (C) on agent readiness against Open WebUI's 51.8 (D), and leads in 3 of 7 scored categories. Open WebUI leads on schema & documentation and security & auth.

Are Foundry Local and Open WebUI open source?

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). No open-source release is listed for Open WebUI.

Other comparisons with Foundry Local or Open WebUI

Disclosure

Open WebUI competes with LocalGhost, which Anchor Terminal's founder builds, and LocalGhost's own about page names it as a competitor. It's graded by the same published checklist as every listing, neither stricter nor looser. Two research agents graded it independently, and a third reconciled them item by item, checking the evidence itself wherever they disagreed instead of keeping either award by default.

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.

Get an auditSee a sample report