Kalsa

List your engine

Two ways in. They are different on purpose: one is a promise from us, the other is a place to be found.

Open now

Listed in the catalogue

For engines with a published improvement that passes the rules. Kalsa can recommend you. The Reviewed badge is separate and optional.

  1. Check the rules. An improvement with its source, stars, licence, signs of life, upstream, install source.
  2. Add an entry to catalog/engines.toml, like the one below.
  3. Open a pull request. A reviewer checks the evidence and the install source.

Open a pull request on GitHub

See an entry, as it is in the catalogue today (frink)
[[engine]]
id = "frink"
name = "frink"
repo = "antonellof/frink"
author = "antonellof"
license = "Apache-2.0"
kind = "engine"
hardware = ["apple-m1", "apple-m2", "apple-m3", "apple-m4", "apple-m5"]
summary = "Loads GGUF models in pure Rust, with quantized Metal kernels and lossless speculative decoding."

[[engine.benchmark]]
source = "https://github.com/antonellof/frink/blob/main/benchmarks/RESULTS.md"
machine = "Apple M2 Pro (10c/6p), macOS 26.6.2, Metal"
chip_tag = "apple-m2"
model = "Gemma-3-1B-IT"
quant = "Q8_0"
decode_tok_s = 122.0
baseline = "llama.cpp (build unknown)"
baseline_decode_tok_s = 83.2
Coming soon

Community listing

Community listing opens soon. It is for new forks and experiments that have not built evidence yet. You will list your own engine, on your own, and it will appear in the Community section. Kalsa never recommends a community engine, but it can still earn the Reviewed badge.

  1. Sign in with GitHub or GitLab, using the account that owns the repository you list. A Hugging Face login will not be enough for this.
  2. Describe the engine: the repository, its licence and what it is for.
  3. It will appear in the Community section straight away. No person will review it against the rules.

Questions before you list? Write to help@kalsa.io.

Sign in

Not available yet.

Hugging Face is for everything else: following engines and, later, uploading benchmarks. GitHub or GitLab is needed to list an engine, and it must be the account that owns the repository.

There is no Google sign-in and no password.

The difference, side by side

ListedCommunity Coming soon
Where it appearsThe main catalogue and recommendationsA separate Community section
Rules checked by a personYes, against every ruleNo
Can be recommended by KalsaYes, when the numbers support itNever
“Reviewed” badgePossible: Kalsa checks the code at a commitPossible too: the same check, the same wording
How you applyA pull request on GitHubSign in with GitHub or GitLab, as the owner of the repository

A community entry can later become a listed one by passing the same rules through a pull request. Either way, anyone can ask for a listing to be removed.