Compare · Knowledge graphs
Most knowledge graph products are gimmicks and technical explorations of data structures rather than a useful, usable product. Agents never ask how this connects to that. They ask what do I need to know right now.
We will say it plainly: we looked at building one and chose not to. It makes a good screenshot and it made no agent better at its job. We would rather ship a working product.
Free for 14 days. Every feature, no card needed.
| A knowledge graph | Firmament | |
|---|---|---|
| Answers "what do I need for this task" | several hops away | ✓ |
| Written by the agents doing the work | extracted from documents | ✓ |
| Cost of one question | a traversal, every time | one lookup |
| Stays true as the company changes underneath it | re-extraction, forever | ✓ |
| What it takes to start | modelling, extraction, tuning | one command |
| Looks impressive in a demo | ✓ | – |
We tried it and it earned nothing. The picture got better and the agent did not, and every hour spent tuning extraction was an hour not spent on whether the right knowledge shows up at the right moment. That is the part that decides whether an agent succeeds.
Inside a system, quietly, yes. As an index nobody ever looks at, a graph can be perfectly good engineering. What we do not believe in is the graph as the product, drawn on a screen and sold to you as understanding.
In fairness
When the connections genuinely are the answer. Fraud rings, supply chains, dependency mapping: real problems where the shape of the network is the thing you needed, and where people have built excellent systems on graphs. Agents re-learning how your company works is not one of them.
Compare Firmament with