A second opinion on your AI stack, from the engineer who mapped all of it.
Send what you are building. Get back a written, layer-by-layer review (what to keep, what to swap, what it will cost and where it will break) from the maintainer of a 112-tool index that publishes when not to use each one.
112 tools mapped · re-verified every six months · no vendor money
What a review is not: it never changes where a tool sits in the index, a ranking or a comparison verdict, and vendors cannot book one about their own product. You are paying for judgement about your system: the index stays free and neutral. How the index is kept.
A decision document, not a call you have to take notes on.
Every review is written down, dated and yours to keep. Each recommendation carries the trade-off behind it, so the reasoning survives the person who read it.
pgvector on your existing Postgres. At 2M chunks with tenant filters, a dedicated vector DB buys you an extra system to run, not recall.
Direct OpenAI calls → a gateway. You have three providers in the roadmap and no fallback today; one outage takes the product down.
An eval set before the next prompt change. You cannot tell whether last week's prompt edit helped, and neither can anyone else.
Three steps, no meetings required.
- 01
Tell us what you are building
A paragraph, rough traffic and the tools you run or are weighing. A diagram helps; nothing confidential is needed.
- 02
Every layer gets checked
Inference, routing, retrieval, agents, guardrails, evals: each against the same use/skip criteria the index publishes.
- 03
You get a document you can act on
Keep, swap or add, with the trade-off behind each call, a cost band for your traffic, and the risk most likely to bite first.
Pick a depth. All three are free right now.
Early access: the first reviews shape the format, so they cost nothing in exchange for honest feedback. Prices will be published here before that changes.
Stack Review
You have a stack, or a plan for one, and want a second opinion.
Freeduring early access
3 working days
- Written review of your current or planned AI stack, layer by layer
- What to keep, what to swap, and what you are missing
- Cost band for your traffic, and the biggest risk in it
- Every recommendation tied to its trade-off, not a vendor
- Recommended
Architecture Session
You are about to commit to a design and want it pressure-tested live.
Freeduring early access
Within a week
- Everything in Stack Review
- 60-minute live call on your system with the maintainer
- Decision record (ADR) you can commit to your repo
- A follow-up review two weeks later
Advisory
You are shipping AI to production and want an engineer on call.
Freeduring early access
Replies within 1 working day
- Async access for architecture and tooling questions
- Monthly review of what changed in your stack and in the market
- Eval, cost and reliability check-ins
- Cancel any month
The review uses the same rulebook the index publishes.
You can read the criteria before you book. Every tool's use-when and skip-when, every comparison verdict and every correction are public.
- tools mapped across 10 sections
- 112tools mapped across 10 sections
- head-to-head comparisons with a verdict
- 11head-to-head comparisons with a verdict
- essays on the decisions behind a stack
- 11essays on the decisions behind a stack
- maximum age of any fact, or the build fails
- 6 momaximum age of any fact, or the build fails
Reviewed by Kunj Shah · kunjshah.in
Before you book.
Will a review change where a tool sits in the index?
No. Reviews sell judgement about your system, never placement. Rankings, layers and comparison verdicts are not for sale, and vendors cannot book a review of their own product.
Why is it free right now?
Early access. The first reviews shape the format, so they cost nothing in exchange for honest feedback. Prices will be published on this page before that changes; nothing you book now is charged retroactively.
Who does the review?
Kunj Shah, who writes and verifies the index. Not a contractor, not a template.
What do you need from me?
A short description of what you are building, rough traffic, and the tools you run or are considering. A diagram helps but is not required. Nothing confidential is needed for a useful review.
Do you recommend tools you earn money from?
No. There are no affiliate links in reviews and no paid relationships with the vendors in the index.
Start with four answers.
What you are building, rough traffic, the tools in play, and what worries you most. That is enough for a useful first pass.
GitHub issues are public. Leave out anything you would not post publicly, or use another channel.
Free during early access
Ship the stack you would choose with all the facts.
Describe what you are building. You get back a written review of every layer: what to keep, what to swap, what it will cost and where it will break.