pickfit

BrowseLocal AI tools

Ferro

Tiny C++ inference engine that runs GGUF embeddings, decisions and chat on Intel N100 iGPU.

Tested on Linux

Use it

Linux x86_64

You need first

  • A GPU is optional

These steps ran from a folder named work in the home folder, which already existed. Make it and run them from there:

mkdir -p "$HOME/work" && cd "$HOME/work"
  1. fresh clone of paragontasx/ferro and KhronosGroup/OpenCL-Headers, then make -j4 CL_INC=<headers> builds ./ferro-embed

    cd "$HOME"/work && rm -rf ferro OpenCL-Headers && git clone --depth 1 https://github.com/paragontasx/ferro ferro && git clone --depth 1 https://github.com/KhronosGroup/OpenCL-Headers OpenCL-Headers && cd ferro && make -j4 CL_INC="$HOME"/work/OpenCL-Headers
Where the README and reality differ
  • README: make -j4 # needs OpenCL headers: CL_INC=../ferro-gpu/third_party/OpenCL-Headers (default)
    What worked: The default CL_INC path does not exist in the repo or next to it. Clone https://github.com/KhronosGroup/OpenCL-Headers and pass CL_INC=<that path> to make (the make test target also needs the same CL_INC).
  • README: make test # kernel + decision + serving tests
    What worked: Without CL_INC on the command line, make test fails with 'CL/cl.h: No such file or directory' in tests/test_kernels. With CL_INC passed it passes. Also the prompt tests are skipped without the d1 model, so the 'decision' coverage here is partial.
Verified in pickfit: the commands exactly as its sandbox ran them

For the record only: they name the sandbox's home, /home/sbx.

cd /home/sbx/work && rm -rf ferro OpenCL-Headers && git clone --depth 1 https://github.com/paragontasx/ferro ferro && git clone --depth 1 https://github.com/KhronosGroup/OpenCL-Headers OpenCL-Headers && cd ferro && make -j4 CL_INC=/home/sbx/work/OpenCL-Headers
cd /home/sbx/work/ferro && make test CL_INC=/home/sbx/work/OpenCL-Headers
cd /home/sbx/work/ferro && make test CL_INC=/home/sbx/work/OpenCL-Headers

Check that it works

cd "$HOME"/work/ferro && make test CL_INC="$HOME"/work/OpenCL-Headers

The output should contain “ALL PASS”.

First thing to try

cd "$HOME"/work/ferro && make test CL_INC="$HOME"/work/OpenCL-Headers

What it does

  • Generate sentence and multimodal embeddings
    Not tested
  • Run d1-omni typed decisions
    Not tested
  • Chat and text generation with LFM2.5
    Not tested
  • OpenAI-compatible HTTP server with prefix cache
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Starts
  3. 0 of 4 features work
  4. Works offline

Good for

  • compute sentence embeddings from text and media
  • answer typed yes/no, choice and score decisions over a state
  • generate chat text and completions with streaming

An alternative to llama.cpp.

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 16 Nov 2026

Differences the test machine hit

  • README: Mesa rusticl is enough (no Intel compute-runtime needed) / OpenCL headers prerequisite
    In the test: This box has no libOpenCL, so the tool printed '[gpu] libOpenCL not found -> CPU' and ran the CPU path. The GPU DP4A test was SKIPPED (no capable GPU).
  • README: ./ferro-embed --help (implied by the usage text)
    In the test: There is no --version. '--help' prints the usage text to stderr and exits 2, the same code as a missing command.
  • README: Models are plain GGUFs (--model kind is auto-detected)
    In the test: The tiny llama-architecture test GGUF stories260K is rejected: 'init failed: not a causal LFM2 language model (arch lfm2 without a decision head expected)'. Only lfm2, gemma-embedding2 and gemma4 GGUFs load.
  • README: make -j4 (Quick start: 2 minutes)
    In the test: The build worked with g++ 14 in about 26 s; it prints a -Wstringop-overflow warning in mm_preproc.cpp, which is harmless here.

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.