BitRun vs PrivateGPT

BitRun 30

Read with the API lines, for the local server an agent calls. No spec of its own. The server is llama-server's OpenAI-compatible surface, and the README documents one route, /v1/chat/completions, with one curl and one Python example (3 of 25). No llms.txt or docs site. The README is Markdown readable raw on GitHub (3 of 10). The README states what each command does and which model suits which job, but nothing on when not to use the server (6). No parameter reference. The model tags are a fixed list in the README (4). Examples for curl and the OpenAI Python SDK. No error responses documented (6). Release notes per tag on GitHub, and the routes sit under /v1 (8).

PrivateGPT 83

An OpenAPI file of 38 paths in the repository (fern/openapi/openapi.json, version 1.0.1), also served by each instance at /openapi.json, with the messages API modelled on Anthropic's (25). docs.privategpt.dev serves llms.txt, a Markdown copy of every page and a docs MCP server (10). The docs explain each endpoint group, startup and model discovery, and a compatibility table says which parts of the Claude API are supported, partial or missing, such as prompt caching and OAuth (15 of 20). Pydantic models with literal type discriminators and required fields, while settings and tool context are wide objects (12 of 15). curl examples for each guide and a /v1/messages/validate route, with error shapes not documented as a list (9 of 15). /v1 paths and a dated changelog, though releases trail main by more than four months (12 of 15). 25 + 10 + 15 + 12 + 9 + 12 = 83.

BitRun 38

Read with the local-software lines, since BitRun runs on the owner's machine with no hosted service. Archives for macOS arm64, Linux amd64 and Windows amd64 on GitHub Releases and one-line install scripts, with supported platforms stated in the README. No package registry, no checksums published, and the shell installer appends to the user's shell profile (15). No CI workflow (the repository has no .github folder). Three Go test files cover Modelfiles, the Cockpit view and power estimates, with nothing running them in public (0). No issue or pull request has been filed in the project's three days, so there is no record to judge. We gave the middle of the scale (15). Semver-style pre-release tags with notes on each release, but no changelog file, and the v0.2.0-beta engine swap from bitnet.cpp to patched llama.cpp is described as an improvement, not a breaking change (8). Version 0.2.0-beta, not 1.0 or declared stable (0).

PrivateGPT 70

Read with the local-software lines, since PrivateGPT runs on the owner's hardware with no hosted service behind it. Homebrew tap, uv tool install from Zylon's own wheel index (not PyPI) and Docker Hub images zylonai/private-gpt 1.0.1 of 18 June 2026. Python 3.11 only, stated in pyproject.toml, and it needs a separate OpenAI-compatible model server (17 of 20). tests.yml runs format, lint, typecheck and the tests affected by each push on main, with the full suite of 217 test files on release pull requests. We couldn't see run results because the GitHub API refused us, and issue #2441 of 1 November reports the Claude spec update workflow failing (15 of 25). GitHub shows 3 open issues of about 1,250, because a stale bot closes quiet issues, two security reports among them, with no maintainer reply (12 of 25). release-please keeps a changelog with breaking changes marked, but no release has been cut since 1.0.1 while main carries 51 commits since 8 August, among them a breaking observability change of 23 October (11 of 15). Version 1.0.1 (15). 17 + 15 + 12 + 11 + 15 = 70.

BitRun 40

Read with the API lines. Output size is controlled through the OpenAI fields llama-server accepts, which BitRun doesn't document. Context windows run from 768 to 8,192 tokens by model (10). No list endpoints worth paging. One model per server process (5). Errors are whatever llama-server returns, with none documented by BitRun (5). Generation has no side effects, so a retry is safe, though nothing documents it (10). Few required parameters, a default port and a placeholder key, and OpenAI's SDKs work against it. No SDK of its own (10).

PrivateGPT 64

Read for an HTTP API an agent calls on a local instance. Token counting, top_k style retrieval settings, citation output and response byte caps let a caller size context (18 of 25). Artifact listing by namespace and retrieval filters, with no documented cursor pagination (12 of 20). FastAPI validation errors name the field and the validate route checks a request before running it, but there is no error catalogue (12 of 20). Async messages and ingestion return task ids with status, cancel and delete routes. No idempotency keys were found (10 of 20). Anthropic SDKs and Claude Code work by pointing ANTHROPIC_BASE_URL at the server, but a model server and an embedding server have to be configured first (12 of 15). 18 + 12 + 12 + 10 + 12 = 64.

BitRun 59

v0.2.0-beta on 15 October 2026 (30). Three releases in four days, 12 to 15 October 2026 (20). No issues or pull requests filed yet, so responsiveness can't be shown. Project only three days old (5). Not in the official MCP registry (no MCP server) and no SDK (0). Go 1.24 with current Bubble Tea dependencies, but no CI or dependency updates set up (4).

PrivateGPT 41

The last release is 1.0.1, dated 16 June 2026 in the changelog and tagged 18 June, 141 days before the check (10 of 30). No release or dated changelog entry in the 90 days since 8 August (0 of 20). Maintainers commit most days and outside pull requests merged in October, but 23 pull requests are open and the stale bot closes issues, including two security reports, with no maintainer reply (13 of 25). Homebrew tap, wheel index and Docker images ship with releases, and Anthropic SDKs work against it. No product MCP server of its own, though it connects to remote MCP servers (10 of 15). Dependabot, uv.lock, actions pinned by commit since 19 October and dependency CVE upgrades in June, July and August (8 of 10). 10 + 0 + 13 + 10 + 8 = 41.

BitRun 54

The editorial half. MIT, all source public, including the C++ patches (30). No privacy statement or statement of what the software sends. The Go source has no network telemetry, and the outbound calls we found are model downloads from huggingface.co on pull (8). No deprecation policy, and v0.2.0-beta replaced the engine within three days (0). The README's "telemetry" is local power and CPU readings shown on screen. Nothing says that nothing leaves the machine, and nothing needs an opt-out (8).

PrivateGPT 64

Apache-2.0 (30). The OpenAPI description says no data leaves the execution environment, but the docs list cloud gateways as model providers and web search goes to outside services when enabled, and no privacy statement covers the software. Zylon's privacy policy covers its website (15 of 30). The 1.0 rewrite was marked as a breaking change in the changelog, and there is no deprecation policy (6 of 20). No telemetry to Zylon found in the source. OpenTelemetry tracing is off by default and its exporters write local files or to the owner's collector, documented on the observability page (16 of 20). 30 + 15 + 6 + 16 = 67.