Three families, and how to tell which one you need
The catalogue is organised by the problem a tool solves rather than by
the language it is written in. Performance Accelerators sit inside a
Python process you already have and make one part of it faster. Agent
Infrastructure sits around a running agent and controls what it can
coordinate, schedule and read. Developer Tools sit in the loop a human
or an agent runs dozens of times a day. A team usually adopts from one
family for months before it touches another, and nothing here assumes
you take more than one.
| What is going wrong | Family | Where to look first |
|---|
| One CPU core pinned while an agent service queues requests | Performance Accelerators | Accelerators |
| Checkpoint or serialisation cost dominates a multi-step graph | Performance Accelerators | fast-langgraph vs LangGraph |
| Several coding agents conflicting on one repository | Agent Infrastructure | Agent Infrastructure |
| An agent needs production data and nobody has written the rules down | Agent Infrastructure | ormai |
| The edit-test loop is slow enough that people stop running it | Developer Tools | Developer Tools |
| Background jobs need a broker the service does not justify | Developer Tools | fastworker |
What a catalogue entry commits to
Every project listed here has a marketing site on its own subdomain,
reference documentation under docs.neullabs.com, and a source
repository. Where a source URL did not resolve at the last audit, the
entry says so rather than quietly linking somewhere else. Licences are
recorded per repository and per release; there is no blanket portfolio
licence claim, and the repository metadata is the authority.
Performance figures on these pages are workload- and version-specific.
They were measured on the hardware and inputs described alongside each
project, and the linked method is the claim — not the headline
multiplier. The reasoning behind that policy is set out in the
engineering evidence method.
Frequently asked questions
Do I need to adopt a whole family?
No. Each project installs on its own and none of them requires a sibling
to be useful. The families are a way of navigating the
catalogue, not a bundle.
Are these products or open-source projects?
They are open-source projects. Neul Labs separately offers scoped
engineering work, described on the solutions page,
and the two are deliberately kept apart: nothing here requires a
commercial relationship.
How do I evaluate one honestly?
Reproduce the benchmark on your own workload before you believe the
number. Each repository documents its method, and the comparison pages
name the cases where the alternative is the better choice rather than
pretending there are none.
What if the tool I need is not here?
The full index at all projects is longer than
these three families, and the 2026 landscape
groups every entry by category with its current status.