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
EvalCore
Snapshot-test AI behavior in CI
EvalCore is a single-binary test runner for LLM apps and agents. Define cases and scorers in YAML, run local targets on every PR, and replay model or judge calls offline for $0. Use REST or shell targets, baselines, trials, model comparisons, and OTel traces.
Hi Product Hunt, I’m @abhishek_manyam. @kuladeep_mantri and I built EvalCore because an AI app can change after a prompt edit, model swap, or dependency update, and the failure often appears after release.
EvalCore makes the eval suite a normal repository artifact: one YAML config, JSONL cases, and one binary. Local shell targets run on each PR. Model and judge calls can be recorded in a SQLite cassette and replayed offline. A suite exits 0 or 1, so CI can block regressions without depending on live model calls.
EvalCore supports deterministic scorers, LLM-as-judge, custom scorers over JSON stdin/stdout, repeated trials, model comparisons, baselines, HTML reports, and OTel/OpenInference agent traces. Targets use HTTP or shell, so your app and custom scoring code can use any language.
The project is Apache-2.0. There is no account, hosted service, or telemetry.
We want feedback from engineers who already run evals in CI: where does your current setup become flaky, expensive, or hard to review? The quickstart takes about five minutes and uses no network. If you try it, tell us what target or scorer is missing.
EvalCore was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #30 on the daily leaderboard. EvalCore is a single-binary test runner for LLM apps and agents. Define cases and scorers in YAML, run local targets on every PR, and replay model or judge calls offline for $0. Use REST or shell targets, baselines, trials, model comparisons, and OTel traces.
On the analytics side, EvalCore competes within Open Source, Developer Tools, Artificial Intelligence and GitHub — topics that collectively have 1.1M followers on Product Hunt. The dashboard above tracks how EvalCore performed against the three products that launched closest to it on the same day.
Who hunted EvalCore?
EvalCore was hunted by abhishek manyam. 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 EvalCore including community comment highlights and product details, visit the product overview.
abhishek manyam
Hi Product Hunt, I’m @abhishek_manyam. @kuladeep_mantri and I built EvalCore because an AI app can change after a prompt edit, model swap, or dependency update, and the failure often appears after release.
EvalCore makes the eval suite a normal repository artifact: one YAML config, JSONL cases, and one binary. Local shell targets run on each PR. Model and judge calls can be recorded in a SQLite cassette and replayed offline. A suite exits 0 or 1, so CI can block regressions without depending on live model calls.
EvalCore supports deterministic scorers, LLM-as-judge, custom scorers over JSON stdin/stdout, repeated trials, model comparisons, baselines, HTML reports, and OTel/OpenInference agent traces. Targets use HTTP or shell, so your app and custom scoring code can use any language.
The project is Apache-2.0. There is no account, hosted service, or telemetry.
We want feedback from engineers who already run evals in CI: where does your current setup become flaky, expensive, or hard to review? The quickstart takes about five minutes and uses no network. If you try it, tell us what target or scorer is missing.
GitHub: https://github.com/eval-core/eva...
Quickstart: https://evalcore.cc/getting-star...