Indexer OS: put a spare machine to work reading the web

If you have an old desktop, a server with room on it, or a machine between projects, Indexer OS gives it something to do: reading the web into the askFinz index.

It is an appliance rather than a package to babysit. You boot it once and it finds the network, works out what the hardware can do, names itself and joins the fleet. There is nothing to configure and nothing to patch, and it updates itself for as long as it runs. Machines lose power and get unplugged mid-sentence, so work in progress is picked up again rather than lost.

What it is and how to run one: https://askfinz.com/indexer_node

The appliance itself: https://askfinz.com/indexer_os

There is a Docker route too, if you would rather not give a whole machine over to it: https://askfinz.com/indexer_docker

Organisations use the same thing differently: pointed at their own corporate pages, product documentation and knowledge clusters, reading them where they sit rather than exporting them somewhere first. That side is here: https://askfinz.com/partners

Fleet figures are live on the page rather than screenshotted into a slide, so you can see what is actually running: https://askfinz.com/web-index

Questions about hardware, bandwidth or what it actually does are welcome here.