One signed Docker image. Every feature compiled in. Free to run. docker pull crowkis/crowkis:latest
← back to the Roost
vs the fieldMarch 17, 2026· 3 min read

Crowkis vs doing nothing: the most expensive cache is no cache

The default strategy — every query goes to the model — has a precise cost. It's on your invoice, itemized as everything.

Doing nothing is a choice with a price tag. Every production LLM workload we've replayed shows the same shape: a long tail of novel questions and a fat head of repeats — the same intents, rephrased endlessly, each one purchased fresh at full price and full latency. The head is commonly a third to two-thirds of all traffic. That's the doing-nothing tax, compounding monthly.

In plain words: You're already paying for a cache — you're just paying the model provider to be one, at a markup of several thousand x per hit.

The tax has a latency component too, and it's arguably crueler: your users wait seconds for answers your system produced yesterday. Speed is a feature users feel on every interaction; paying premium prices to be slow at repetition is a strange position to defend in a roadmap review.

what repeated traffic costs without crowkis

Every paraphrase is a fresh bill — unless the cache understands meaning.

Crowkis exists to make the head of the distribution nearly free: semantic hits in under a millisecond, gated for safety, with the dashboard pricing the savings in real time. The tail still goes to the model — that's what models are for — but the repeats stop billing.

The bottom line

Community edition is free, deployment is five minutes, and the worst case is a pass-through that cost you an afternoon. The status quo charges more than that every day. Few infrastructure decisions are this asymmetric.