Notes from the nest · 980 posts
Engineering notes written by the people building Crowkis. Comparisons, use cases, economics, internals, security, operations, and nothing written just to rank.
Agents re-ask, re-plan, and re-fetch with industrial enthusiasm. Multiply by a fleet and you get the most cacheable traffic in existence, if the cache understands agents.
CINFO returns server, cache, savings, security, db, and license sections in one call, the fastest read on what the cache is doing right now.
A v0.2.1 bug let the HNSW index go cold under heavy write-and-flush churn, semantic search silently stopped finding neighbours. Here's the soak test that reproduces it and proves v0.2.2 fixed it.
Building ecommerce assistants on LangChain.js? Add a semantic cache so the same product and policy questions across shoppers stop costing full price.
Building email drafting tools on Ollama? Add a semantic cache so similar drafts requested over and over stop costing full price.
Building knowledge base assistants on Semantic Kernel? Add a semantic cache so the same lookups across a team all day stop costing full price.
Building devops copilots on LangChain? Add a semantic cache so the same runbook and incident questions stop costing full price.
Durable, per-user memory for LangChain agents that survives restarts and consolidates contradictions, self-hosted, zero egress.
A hard TTL turns a one-second-expired answer into a full model call. CSTALE serves the cached answer past its TTL with a stale flag, so you choose freshness versus latency per request.
One container, a PVC, real health probes, hard memory bounds, graceful shutdown. Everything your cluster expects from a tenant that's read the manual.
Every cache vendor promises a hit rate. Crowkis Replay computes yours, on your real queries, before you spend anything. The pitch is a number with your name on it.
Building healthcare Q&A assistants on LangChain.js? Add a semantic cache so recurring policy and triage questions stop costing full price.
Building code review bots on Ollama? Add a semantic cache so the same review patterns across pull requests stop costing full price.
Building research assistants on Semantic Kernel? Add a semantic cache so overlapping literature and summary questions stop costing full price.
Building API documentation bots on LangChain? Add a semantic cache so the same endpoint questions from every developer stop costing full price.
Add a semantic cache to LangGraph so repeated and reworded questions are served for free, no rewrite, self-hosted.
Durability isn't a checkbox, it's a sequence of writes in the right order with checksums at every step. Here's the boring machinery that makes restarts uneventful.
Building legal document assistants on LangChain.js? Add a semantic cache so the same clauses and questions across matters stop costing full price.
Building data analysis agents on Ollama? Add a semantic cache so repeated tool calls and the same analytical questions stop costing full price.
Building contract analysis tools on Semantic Kernel? Add a semantic cache so the same clause questions across documents stop costing full price.