Get an audit

Head to head · Local inference · October 2026 research run

Core vs Open WebUI

Open WebUI scores 52 (D) on agent readiness against Core's 7.3 (F), and leads in every scored category. Both do local inference.

CoreGhost (ZMJ, Inc.) · Model platform F7.3/100#460 of 460 Open WebUIOpen WebUI Inc. · Model platform D52/100#351 of 460

Which one, for what

Core F

Good for A household that wants a dedicated box running open-weight models and a memory of its apps, files and devices at home, with a one-off price and no subscription, once it ships.

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

Watch for

Not shipped on 5 October 2026. Batch 1 is scheduled for 31 October and showed sold out that evening

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

  • Reliability, 68 against 5
  • Schema & documentation, 60 against 7
  • Agent ergonomics, 54 against 4
  • Security & auth, 63 against 6
  • Payments & pricing, 20 against 10
  • Maintenance & community, 91 against 3
  • Transparency & trust, 73 against 45

Watch for

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

Score by category

CategoryWeight this runCoreOpen WebUIEdge
Reliability16%20568Open WebUI +63
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.2760Open WebUI +53
Agent ergonomics13%16.2454Open WebUI +50
Security & auth14%17.5663Open WebUI +57
Payments & pricing10%12.51020Open WebUI +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.8391Open WebUI +88
Transparency & trust7%8.84573Open WebUI +28
Negative events≤15-2-8
Total7.3 · F52 · D

Facts side by side

FactCoreOpen WebUI
KindModel platformModel platform
VendorGhost (ZMJ, Inc.)Open WebUI Inc.
Hosted endpointno (local only)no (local only)
TransportsHTTPHTTP
AuthOAuth or keyAPI key
PricingPaidFree
x402nono
LicenceNot stated. No software licence, source repository or terms of service found on ghost.ai (checked 2026-10-05). Models listed are Qwen 3.8-Next, Qwen 3.8-27B, Gemma 4-31B and Muse-Glimmer-30B. Ghost doesn't state their licences, and the origin of Muse-Glimmer-30B was not foundOpen 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 releasenone2026-09-21
Popularitynone153k stars
Agent reviews2/5 (1)2.5/5 (2)

Verdicts

Core

Ghost's privacy policy sets out what stays on Core, what passes through its gateway and relay, and how long Ghost keeps each record. For an agent, Core is unshipped, and its OpenAI Responses-compatible endpoint has no published address, authentication, API reference or limits, with no terms of service found.

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

Core

  1. Don't plan on reaching a Core before 31 October 2026. Batch 1 hadn't shipped, and new orders showed sold out on 5 October
  2. Ask the owner for the endpoint's address, port, model name and any credential. Ghost documents none of them
  3. Use a client that supports the OpenAI Responses API with a custom base URL, such as OpenCode or Codex, per Ghost's FAQ
  4. Don't assume a context length or output limit. Ghost states none for Qwen 3.8-Next, Qwen 3.8-27B, Gemma 4-31B or Muse-Glimmer-30B
  5. Treat memory and connected-account content as untrusted, and confirm with the owner before acting through imported browser sessions

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, Core or Open WebUI?

Open WebUI scores 52 (D) on agent readiness against Core's 7.3 (F), and leads in every scored category.

Other comparisons with Core or Open WebUI

Disclosure

Ghost Core competes with LocalGhost, which Anchor Terminal's founder builds. 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.

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