InfraNodus vs Graphify: Text to Knowledge Graph

Graphify is a command-line tool and AI agent skill that turns your documents into a knowledge graph: an LLM reads the text, extracts the notable concepts, and asserts typed relations between them (such as "is a" or "cites"), each with a confidence score. The result is a curated concept map that you can traverse or export to Obsidian.

InfraNodus approaches the same problem from the other side. Instead of asking an AI model what the text claims, it builds the graph directly from the text itself: words are normalized to their base forms and connected when they co-occur close to each other. The result is a complete, reproducible network of the discourse, where every connection keeps the original statements attached to it as evidence, which you can then explore in an interactive graph and analyze with built-in AI.

Both tools cluster the resulting graph to reveal the main topics, find the influential concepts, and use an LLM to generate insights from the structure. The differences are in how the graph is built, how deep the analytics go, and what each tool considers the primary layer: the AI model's interpretation of the text or the text itself.

InfraNodus vs Graphify: Feature Comparison

Feature	InfraNodus	Graphify
Graph Construction	Deterministic text network analysis: same text, same graph, no API costs	LLM extraction: non-deterministic, token cost on every run
Coverage of the Text	Exhaustive: every meaningful word, plus optional named entities, hashtags, and [[wikilinks]]	Curated: the concepts the LLM deems notable
Evidence on Every Edge	Full original statements attached to every connection	File and line reference only; the sentence itself is discarded
Typed, Directed Relations	Via statement tags and categories; direction lives in the sentence	Directed labels (is_a, cites…) with confidence scores
Structural Gap Detection	Native: ranked content gaps between under-connected topics	No
Network Analytics	Betweenness centrality, entropy, bias / focus / dispersion diagnostics	Degree-based hubs and cross-cluster connections
Interactive Visualization	Interactive graph: explore, filter, remove nodes, recalculate in real time	CLI output; visualization via Obsidian export
Live Data Sources	Google, YouTube, X, RSS, PDF, CSV, Obsidian, and more	Local files only
Image Analysis	Text-based formats only	Extracts concepts from images via vision models
Multilingual Support	Dedicated NLP pipeline for ~20 languages	Whatever the underlying LLM handles
Time Axis	Timestamps and temporal filtering to see how a discourse evolves	None
AI Insights	Built-in AI interprets the graph: topics, gaps, research questions, GraphRAG	AI is the extraction mechanism; insight via agent workflows
Code Repo & Obsidian Vault Graphs	Via the /infranodus agent skill: docs, docstrings, code comments, commit history	Core use case: AST parsing of code files
Product	Web app + API + MCP server + Obsidian plugin + agent skill	CLI + agent skills + MCP + Obsidian export

How They Build the Graph: Two Different Philosophies

A tempting but wrong framing is "Graphify edges mean something, InfraNodus edges are just statistics." In fact, both graphs carry meaning — they just store it at different layers.

Graphify is abstraction-first. The LLM reads a chunk of text, asserts a directed, labeled, confidence-graded relation between two concepts, and the original sentence is discarded. What you keep is a traversable schema of what the model understood the text to claim. The price is non-determinism (re-running the extraction yields a different graph), token costs on every run, and trust in the model's assertions. The extraction is also chunk-local: two similar ideas in different parts of your corpus never get linked unless the model happens to see them together.

InfraNodus is evidence-first. Every connection in the graph keeps the full statements it was derived from, so the original sentence is the relation's description. Statement tags and categories let you type and filter the connections, and the co-occurrence graph is global across the whole corpus: the same concept appearing in different documents converges into one node. The graph is deterministic, reproducible, free of model calls, and works the same in ~20 languages.

For prose, this makes InfraNodus the more principled instrument: nothing is lost, nothing is hallucinated, and you can always click any connection to read the exact statements behind it.

The Key Difference: What's Missing vs What's There

Everything Graphify computes — hub concepts, communities, surprising cross-cluster connections — is a presence operation: it tells you what is connected in your knowledge. InfraNodus does all of that too, but its genuine differentiator is reasoning about absence: the structural gaps between topic clusters that are both prominent but poorly connected to each other.

These gaps are where the interesting questions live: a latent research direction, a blind spot in your thinking, a content opportunity your competitors missed. Graphify tells you what's in the graph; InfraNodus tells you what's conspicuously missing from it — and its built-in AI can then generate the ideas, research questions, or content that would bridge the gap.

InfraNodus structural gap detection in a knowledge graph

On top of the gap analysis, InfraNodus measures the overall shape of your discourse — whether it's too biased towards one topic, well focused, or too dispersed — and ranks concepts by betweenness centrality, surfacing the ideas that hold your narrative together rather than just the ones that appear most often.

InfraNodus Is Also an Agent Skill

Graphify's natural habitat is an AI coding agent: you install it as a skill, point it at a folder, and get a knowledge graph. InfraNodus works the same way. The free /infranodus agent skill turns any code repository or Obsidian vault into InfraNodus knowledge graphs, right from Claude Code or Claude Desktop.

Invoked inside a project folder ("graph this repo", "analyze this vault", or simply /infranodus), the skill mines your documentation, PDF text, docstrings, WHY / NOTE code comments, and commit, PR, and issue history into saved graphs, along with a written report. The extraction is deterministic — no LLM pass over your files, so no token costs and the same result every time — and the graphs are uploaded to your InfraNodus account via the MCP server, where you can explore them visually and run the full analytics on top.

Once built, the skill saves a manifest into the project, so any later question about the project's themes, decisions, rationale, or blind spots is answered by querying the graphs first instead of re-reading the files — the same "knowledge graph as project memory" workflow Graphify targets, with InfraNodus's structural analytics and interactive interface added on top.

How to Install the /infranodus Skill

Download the skill from the InfraNodus skills repository on GitHub.
Claude Code: copy the infranodus skill folder into ~/.claude/skills to make it available in all your projects, or into .claude/skills inside a project for project-specific use.
Claude Desktop: go to Settings → Capabilities, enable "Code execution and file creation", then use "Upload Skill" to add the skill.
Connect the InfraNodus MCP server and set your INFRANODUS_API_KEY (available with your InfraNodus API access) so the skill can upload and query your graphs.
Open a project folder, type /infranodus, and ask it to graph your repo or vault.

The same repository also contains companion skills that compose with it — notably the ontology creator, which uses an LLM to generate typed [[wikilink]] relations (the closest equivalent to Graphify's labeled edges, and it pastes straight into InfraNodus), and the LLM wiki skill for maintaining an AI-authored knowledge base on top of your graphs.

Better Together: Using Graphify with InfraNodus

The two tools compose rather than compete: one asserts what the text claims, the other reveals how the discourse is organized. Graphify's extracted relations, serialized as [[wikilink]] statements, are valid InfraNodus input — so you can use Graphify to distill a curated concept layer from your files and then import it into InfraNodus to get the interactive visualization, structural analytics, and gap detection on top.

You can also connect both to the same AI agent: Graphify as the local extraction step, and the InfraNodus MCP server as the analysis layer that reveals the main topics, blind spots, and research questions in whatever the agent is working on.

Want to Try It Yourself?

Create an account to visualize your own texts as a knowledge graph and see the topics, influential concepts, and structural gaps in seconds: