What is Gnarl?
Gnarl is decentralized search infrastructure.
Instead of moving every document into one cluster before you can search it, Gnarl turns each place your data already lives into a node. Nodes index locally, publish a signed summary of what they can answer, and cooperate on queries. The result is one searchable surface across many independent operators — without a central cluster, and without anyone's data leaving home.
gnarl node up --data ./corpus # index what you already have
gnarl join # announce yourself to a network
gnarl search "satellite imagery" # query everyone who can answer
The problem with the cluster
Classical distributed search assumes the cheapest place to search data is a cluster you control, so step one is always the same: copy everything in.
That assumption breaks down in the situations that matter most today.
- Data gravity. Petabyte archives cost more to move than to search.
- Sovereignty. Some data legally cannot cross a boundary, ever.
- Blast radius. One coordinator, one config change, one bad night.
- Economics. You pay twice — once to store the data, once to duplicate it.
The shape of a network
A Gnarl network has no coordinator, no elected master, and no shared cluster state to keep in sync. It has three moving parts.
| Part | What it does |
|---|---|
| Node | Indexes a local corpus, answers queries against it, enforces its own policy |
| Manifest | A signed, compact statement of what a node can answer — never the documents |
| Query plan | Chooses which nodes to ask, fans out, merges the ranked results |
A query enters at any node. That node reads the manifests it knows about, decides who is worth asking, fans the query out, and merges what comes back into one ranked result set. Nodes that cannot contribute are never asked, and nodes that are offline simply do not answer.
What Gnarl is not
- Not a blockchain. There is no ledger, no token, and no consensus round in the query path. Signatures establish provenance; they do not order history.
- Not a crawler. Gnarl indexes corpora that operators deliberately expose. It does not go looking for content on its own.
- Not a replacement for your database. It is a retrieval layer over data that keeps living wherever it lives now.
Where to go next
- Install Gnarl — get a node running locally.
- Join the network — announce a node.
- Architecture — how a query actually executes.