A
archify
96.0
97,376 stars · Apache-2.0
AI Agents
Open WebUI leads by 3.1 · narrow
A
96.0
97,376 stars · Apache-2.0
B · leads
99.1
158,922 stars · MIT
archify versus Open WebUI is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. archify is written mainly in JavaScript; Open WebUI is written mainly in Svelte. The composite score is 96.0 for archify and 99.1 for Open WebUI.
Open WebUI has 158,922 GitHub stars to archify's 97,376, a gap of 61,546 (1.63×). Forks are 6,647 for archify and 23,097 for Open WebUI. On the log scale used inside this pair, adoption is 96 versus 100, and the fork community is 88 versus 100.
Push history: archify was last pushed on 17 November 2026 (0 days ago), and Open WebUI was last pushed on 17 November 2026 (0 days ago). Open issues stand at 368 for archify (0.004 per star) and 208 for Open WebUI (0.001 per star). Issue-health scores are 96 and 96; activity scores are 100 and 100.
archify is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Open WebUI is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. License scores in this pair are 96 for archify and 96 for Open WebUI. This is a procurement signal, not legal advice.
In AI Agents, both archify (97,376 stars) and Open WebUI (158,922 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: archify is open source, Open WebUI is open source.
Open WebUI is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 12 points (88 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
Open WebUI finishes ahead at 99.1 against archify at 96.0, a 3.1 point narrow margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | archify | Open WebUI |
|---|---|---|
| GitHub stars | 97,376 | 158,922 |
| Forks | 6,647 | 23,097 |
| Open issues | 368 | 208 |
| Adoption | 96 | 100 |
| Activity | 100 | 100 |
| Community | 88 | 100 |
| Issue health | 96 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.0 | 99.1 |
Turn any idea, plan, or codebase into a beautiful interactive diagram. An agent skill for Claude Code, Codex, and more.
Open WebUI is a self-hosted chat interface for local and remote language models, including Ollama. It adds users, documents, and tools around the model endpoint.
Open WebUI has more GitHub stars: 158,922 versus 97,376 for archify. The gap is 61,546 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both archify and Open WebUI as self-hostable. Confirm each project's deploy docs before you plan a migration.
archify is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Open WebUI is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Open WebUI scores 99.1 and archify scores 96.0. This page calls that a narrow lead for Open WebUI.