This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
kremis
Every LLM claim traced to real data — or rejected
LLM claims validated against real data — never invented. Kremis ingests EAV signals, builds a deterministic graph, classifies every response: FACT (direct edge), INFERENCE (derived path), or UNKNOWN (not in data). No confidence scores. No probabilistic gaps. Built in pure Rust (no async, no floats in core), with ACID persistence via redb, HTTP API, CLI, and MCP bridge for Claude/Cursor. Apache 2.0. v0.17.8 — alpha, functional, tested. 354 tests passing.
I built Kremis because RAG retrieves the right documents but the LLM still invents details. I needed a way to check each claim against real data — not with similarity scores, but with a binary answer: is this in my data or not?
The core loop:
1. Ingest signals as EAV triples (entity, attribute, value)
2. Kremis builds a weighted graph from co-occurrence
3. Query → every result tagged as FACT, INFERENCE, or UNKNOWN
No embeddings in core. No floating-point. Same input, same output.
What's working today:
- kremis-core (pure Rust, no async, no network)
- HTTP API (axum) + CLI (clap)
- MCP bridge — 9 tools, works in Claude Desktop and Cursor
- ACID persistence via redb
- Docker image
The main friction is EAV ingestion: you structure your data as signals before querying. Is that too rigid? I'd like to hear.
Demo in the repo (Python, stdlib only):
python examples/demo_honesty.py
Docs: https://kremis.mintlify.app
Background story: https://dev.to/tykolt/i-spent-mo...
About kremis on Product Hunt
“Every LLM claim traced to real data — or rejected”
kremis was submitted on Product Hunt and earned 3 upvotes and 1 comments, placing #104 on the daily leaderboard. LLM claims validated against real data — never invented. Kremis ingests EAV signals, builds a deterministic graph, classifies every response: FACT (direct edge), INFERENCE (derived path), or UNKNOWN (not in data). No confidence scores. No probabilistic gaps. Built in pure Rust (no async, no floats in core), with ACID persistence via redb, HTTP API, CLI, and MCP bridge for Claude/Cursor. Apache 2.0. v0.17.8 — alpha, functional, tested. 354 tests passing.
On the analytics side, kremis competes within Open Source, Developer Tools and Artificial Intelligence — topics that collectively have 1M followers on Product Hunt. The dashboard above tracks how kremis performed against the three products that launched closest to it on the same day.
Who hunted kremis?
kremis was hunted by TyKolt. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of kremis including community comment highlights and product details, visit the product overview.
TyKolt