Mintplex-Labs/anything-llm

Choose this fork only if its ARM/Docker and logging changes are specifically valuable to you. If you want the latest AnythingLLM features, active maintenance, or easier upstream compatibility, upstream is the safer choice.

Choose this fork only if its branding and specific provider/search additions are exactly what you need and you are prepared to maintain a stale codebase. For most adopters, upstream is the safer choice because it is much more current, more actively maintained, and likely has broader language and workflow coverage.

Choose this fork if you want a customized AnythingLLM distribution with extra search and deployment-focused changes. Choose upstream if you want the broadest feature coverage, fastest access to recent fixes, and the least merge risk.

Choose this fork only if its deployment and instance-management additions are the point; otherwise upstream AnythingLLM is the safer default because this fork is far behind and appears to have lost a lot of later product work.

Choose this fork if you want a more deployment- and workflow-opinionated AnythingLLM derivative and can tolerate being materially behind upstream. Choose upstream instead if you want the latest fixes, translations, and product polish with lower maintenance risk.

Choose this fork only if its added export, file, and workspace workflows match a concrete need. Otherwise upstream looks much safer: it is far more active, broader in capability, and much lower risk to adopt.

Prefer upstream unless you specifically need this exact snapshot. This fork does not show unique capabilities, and being 93 commits behind makes it a weaker choice for anyone who wants current features, fixes, or provider/support updates.

Choose this fork if you want an API- and deployment-centric AnythingLLM derivative and are comfortable owning divergence. Choose upstream if you want the fastest path to current fixes, polish, and ecosystem compatibility.

Adopt this fork only if you want a frozen copy of AnythingLLM and are comfortable owning future maintenance yourself. For most users, upstream is the better choice because this fork shows no added capabilities and is substantially behind.