Graphify Knowledge Graph

Graphify reads a project's source and builds a knowledge graph from it: nodes for the real abstractions, edges for how they connect, and communities for the parts of a system that belong together. It works from the syntax tree rather than by sending code to a model, so a rebuild costs nothing to run and finishes in seconds.

It is driven by a small CLI that resolves the project from whatever directory you are standing in — build the graph, ask it a question, explain a node and its neighbours, or trace the shortest path between two of them. Output is a written report, a graph file and an interactive view. A single ignore file at the top of the tree keeps vendored bundles out, which is the difference between a graph of the project and a graph of its dependencies.

This site's own graph is 698 nodes and 852 edges across 183 files, with 126 communities detected.

How it came together.

The work moves from the right question to a system the team can actually use.

1. 01

   Strategy

   It starts with a strategy session — I come to you, learn the business inside out, and shape a plan you actually want and that actually works. Goals first, never template-first.

2. 02

   Design

   Then I design it — interface, brand and the feel of using it — mapped straight to that strategy. One person, one vision, no handoff gap between designer and developer.

3. 03

   Development

   I build the real thing: fast, typed end-to-end, Supabase-backed, and yours outright — the website and the operations behind it, shipped on a tight loop.

4. 04

   Iteration

   We iterate on the live product — real usage, real numbers — tightening the funnel and the workflows until it genuinely performs.

5. 05

   Ongoing management

   From there I keep it running and growing — performance, updates, new campaigns and features as the business moves. One number to call, no agency runaround.

Role

Internal tool — design & build

Client

Graphify Knowledge Graph