head to head · open source

graphify vs loop-engineering

graphify has 141,064 GitHub stars, 13,483 forks, 1,350 open issues and last shipped yesterday. loop-engineering has 11,683 stars, 1,575 forks, 9 open issues and last shipped yesterday. graphify leads on adoption by 1,107% (141,064 vs 11,683 stars). graphify is written in Python under Apache-2.0; loop-engineering is written in TypeScript under MIT. graphify has attracted 10% as many forks as stars, loop-engineering 13%. graphify was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 3 topic tags (ai-agents, claude-code, codex), so they are genuine substitutes rather than adjacent tools.

Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.

graphify ★ 141K loop-engineering ★ 12K category AI & Machine Learning

← all 20902 open source comparisons

Side by side

graphify loop-engineering
GitHub stars ★ 141K ★ 12K
License Apache-2.0 MIT
Written in Python TypeScript
Last push 2026-11-02 2026-11-02
Forks ⑂ 13K ⑂ 1.6K
Self-hosting Yes Yes
Data ownership Your server Your server

pick graphify if

  • You weight community size — 141K stars and counting
  • You want the Apache-2.0 license terms
  • Your stack matches Python
  • You value the larger contributor base for long-term maintenance

full graphify profile →

pick loop-engineering if

  • You want the loop-engineering feature set and don't need the biggest community
  • You prefer the MIT license terms
  • Your stack matches TypeScript
  • You evaluated both and loop-engineering fits your workflow better

full loop-engineering profile →

About graphify

Read this in other languages 🇺🇸 English 🇨🇳 简体中文 🇯🇵 日本語 🇰🇷 한국어 🇩🇪 Deutsch 🇫🇷 Français 🇪🇸 Español 🇮🇳 हिन्दी 🇧🇷 Português 🇷🇺 Русский 🇸🇦 العربية 🇮🇷 فارسی 🇮🇹 Italiano 🇵🇱 Polski 🇳🇱 Nederlands 🇹🇷 Türkçe 🇺🇦 Українська 🇻🇳 Tiếng Việt 🇮🇩 Bahasa Indonesia 🇸🇪 Svenska 🇬🇷 Ελληνικά 🇷🇴 Română 🇨🇿 Čeština 🇫🇮 Suomi 🇩🇰 Dansk 🇳🇴 Norsk 🇭🇺 Magyar 🇹🇭 ภาษาไทย 🇺🇿 Oʻzbekcha 🇹🇼 繁體中文 🇵🇭 Filipino 🇮🇱 עברית Early access to the graphify platform is open before the public v1 launch: app.graphify.com Type /graphify in your AI coding assistant and it maps your entire project (code…

read the full graphify overview →

About loop-engineering

Loop Engineering Stop prompting. Design the loop. Get a score. Start in 5 minutes · Quickstart · What do you want to do? · Refactor path · 中文 · Pattern picker tool defaults to claude if you omit it. Swap for grok , codex , or opencode . Week one is report only . You design a system that discovers work, hands it to agents, verifies results, and persists state — instead of typing the next prompt yourself. New here? Quickstart · Refactor a project · Thin GitHub Action loop (no STATE.md required) What do you want to do? This is a pattern library for operating agents around a codebase . It is not a “rewrite the…

read the full loop-engineering overview →

More in AI & Machine Learning

Related comparisons

More AI Development Platforms projects

Compare either of these against the rest of the AI Development Platforms field.

Frequently asked questions

Is graphify or loop-engineering more popular?

graphify has 141,064 GitHub stars and loop-engineering has 11,683. graphify has the larger community by that measure.

Are graphify and loop-engineering free?

Both are open source. graphify is licensed under Apache-2.0 and loop-engineering under MIT. Neither carries a licence fee.

What is the difference between graphify and loop-engineering?

graphify is written in Python and loop-engineering in TypeScript. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.

Which should I choose, graphify or loop-engineering?

Choose graphify if you want the larger community (141,064 stars) or its Apache-2.0 licence terms. Choose loop-engineering if its feature set, stack or MIT licence fits better. Both are self-hostable.