A precision toolkit for force-directed layouts, dependency analysis, and interactive node-graph visualization. Drop into any stack. Render a million edges. Stay sane.
Six interlocking primitives. No magic. Every layout you see assembled from a small alphabet of operations.
Velocity Verlet integration with adaptive timestep. Drag a node, watch the rest of the graph reorganize. The simulation never blocks the main thread — we run on a worker by default.
const g = graphers('#canvas') .nodes(data.nodes) .edges(data.edges) .simulate({ charge: -240 });
SVG for < 500 nodes. Canvas2D for < 50k. WebGL2 for the rest. Switch at runtime — we hot-swap the renderer without touching state.
A small declarative query language for selecting subgraphs. BFS, DFS, shortest-path, Tarjan SCCs and topological sort built in. Compose them like middleware.
// neighbors of "main" within 2 hops g.match('(:fn {id:"main"})-[*1..2]-(n)') .highlight({ color: '#ff6b35' });
PNG, SVG, JSON, GraphML, DOT. Lossless round-trip with layout coordinates intact.
"It's the first graph library where I didn't have to write the layout myself. Everything just composes."
Hover any panel to wake the simulation. Drag the nodes. The edges are elastic.
Visualize the full import graph of a monorepo. Detect cycles, find the package nobody imports, watch a refactor land in real time.
Wire entities, relations, and timestamps. A first-class citizen for retrieval-augmented systems.
SREs use it to map service meshes. Edges turn orange when latency spikes.
A research lab plugged 240k papers into the engine. Communities surfaced. Vertex Purple marks the cluster of self-citations.
Documentation that respects your time. Concept page, API page, recipe page. Nothing else.
Install, mount, render. Eight minutes from zero to your first graph.
/docs/quickstart →Nodes, edges, attributes, attributes-on-edges. The internal representation explained without lying.
/docs/data-model →Choose the right algorithm. Tune parameters. Understand the trade-offs of each force.
/docs/layouts →SVG vs Canvas vs WebGL. When to pick which. How to write your own.
/docs/renderers →Copy-paste solutions for the things you'll absolutely need: lasso selection, sticky nodes, exported PNGs with print resolution, server-side static rendering, custom edge bundling, hover overlays that don't fight your tooltip library.
/docs/recipes →Every method, every option, every event. Generated from source. Stays current.
/docs/api →Every layout is documented with the formula it implements. No black boxes. If you want to know why a node landed where it did, the answer is in the docs.
We benchmark every release against the previous one. Regressions block the merge. The 60fps line is sacred.
Method names that read like English. No clever DSLs. The library should disappear into your code.
Twelve small functions that compose beat one giant function with forty options. Every time.