kolm
sign in Get API key →
brand · the naming stack

Kolmogorov is the company. kolm is the binary.

The same way gcc is the binary of GCC, or git is the binary of Git: the company name carries the academic root, and the CLI name is short enough to type a hundred times a day. The format is .kolm. The open spec is RS-1. Use the right name for the right thing and everything reads cleaner.

The stack.

company
Kolmogorov
The org. Capital K. The thing that signs the registry.
binary
kolm
The CLI. Lowercase, monospaced. kolm compile, kolm serve.
format
.kolm
The artifact. A signed zip: model, LoRA, recipes, recall, receipts.
spec
RS-1
Open. MIT-licensed. Manifest schema, receipt format, K-score math.

Naming rules.

Capital K Kolmogorov: whenever you mean the company, the org, the people, or the registry that signs artifacts. Same convention as Anthropic or Hugging Face.

Lowercase kolm: whenever you mean the CLI tool, a command, or the runtime binary. Render in monospace if your medium supports it. Same convention as gcc, git, npm, kubectl.

Monospace .kolm: whenever you mean the file format or an artifact. Always with the leading dot, always in monospace. Same convention as .deb, .gguf, .safetensors.

RS-1: whenever you mean the open spec. RS stands for recipe spec. Numbered for forward versioning.

Why this naming.

Andrey Kolmogorov asked the underlying question in 1965: what is the smallest specialist program that produces a given behavior? That is precisely what a compiled .kolm answers for a single task. The company name carries the academic root because the math is the moat. The CLI is kolm because we don't expect anyone to type kolmogorov compile a hundred times a day.

What's already taken.

Yes, we know. Kolm is also a Norwegian/Swedish prog-rock band (~5k monthly listeners). Petter Kolm is a quant-finance professor at NYU. Kolmogorov-Arnold Networks (KANs) is a 2024 paper with a thousand-plus citations. None of them sell a compiler. None of them ship a file format. None of them collide on the search-shape that matters: compile a task into a portable signed AI artifact. If you got here looking for one of the others, the rest of the internet still has them.

The brand stack is small on purpose. One company name, one CLI name, one file extension, one open spec. Everything else is product surface that hangs off these four.

Citing us.

In a paper or an article: "Kolmogorov Stack (kolm)" on first reference, "kolm" on subsequent. In a code block, just kolm. In a manifest, .kolm. The RS-1 whitepaper is the canonical reference.

spec RS-1 whitepaper →

The 12-page open spec. Manifest schema, receipt math, K-score formula.

 why The closed-API tax →

The argument for compiling out of variable-cost cloud AI.

 format What's in a .kolm →

The seven components and the receipt chain.

 code github.com/kolmogorov-stack →

The CLI source, the smoke battery, the open spec.