Compare/qmd vs Waydev

AI tool comparison

qmd vs Waydev

Which one should you ship with? Here is the side-by-side panel verdict, pricing read, reviewer split, and community vote comparison.

Q

Developer Tools

qmd

Local doc search engine with BM25 + vectors + LLM re-ranking — by Shopify's CEO

Mixed

50%

Panel ship

Community

Free

Entry

qmd is a lightweight local search engine built by Tobi Luetke, CEO of Shopify, for indexing and querying personal knowledge bases, documentation, and meeting notes — entirely offline. It combines three retrieval approaches in a single pipeline: BM25 full-text search for exact keyword matches, vector semantic search via ONNX-based embeddings, and LLM re-ranking using GGUF models through node-llama-cpp. All three stages run locally with no cloud dependency. The tool ships in multiple deployment modes: a CLI for ad-hoc queries, a Node.js library for programmatic use, an HTTP service for local API access, and — most useful for AI workflows — a native MCP server that lets Claude Code, Cursor, and similar editors query your local knowledge base directly during coding sessions. The hybrid retrieval approach means it handles both "find the exact error message from last week's standup notes" and "what was our decision about the auth architecture" equally well. What makes this notable beyond its technical approach is provenance: Luetke shipped it as a personal tool he actually uses, not a startup product. The GitHub history shows active iteration and he's been talking about it on X. It's a credible signal of where pragmatic AI-augmented knowledge management is heading for technical users who prefer local-first tools.

W

Developer Tools

Waydev

Measure ROI of every AI coding tool — Copilot vs Cursor vs Claude Code unified

Mixed

50%

Panel ship

Community

Paid

Entry

Waydev has relaunched as the measurement layer for AI-written code, letting engineering teams track which AI agent wrote which code, tokens consumed per PR, cost-per-shipped-line, and acceptance rates — with a unified comparison dashboard across GitHub Copilot, Cursor, Claude Code, and other AI coding tools. Founded in 2017 and backed by Y Combinator (W21), Waydev spent nine years building engineering analytics infrastructure. The pivot to AI SDLC measurement uses that existing integration surface (GitHub, GitLab, Jira, Linear) to add agent attribution metadata on top of existing flow metrics. The result is the first tool that can answer 'our team spent $4,200 on AI coding tools last month — which $1,000 was actually worth it?' With enterprise engineering budgets now routinely including five-figure monthly AI tooling costs and no standardized way to measure output quality by tool, Waydev's timing is sharp. The YC pedigree and existing customer relationships mean this isn't starting from zero — they're adding a new measurement layer to existing installed base.

Decision
qmd
Waydev
Panel verdict
Mixed · 2 ship / 2 skip
Mixed · 2 ship / 2 skip
Community
No community votes yet
No community votes yet
Pricing
Free, open source (MIT)
Contact for pricing / Enterprise
Best for
Local doc search engine with BM25 + vectors + LLM re-ranking — by Shopify's CEO
Measure ROI of every AI coding tool — Copilot vs Cursor vs Claude Code unified
Category
Developer Tools
Developer Tools

Reviewer scorecard

Builder
80/100 · ship

Hybrid BM25 + vector + LLM re-rank is the right architecture for personal knowledge search — each layer catches what the others miss. The MCP server mode is genuinely useful: being able to ask Claude Code 'what did we decide about X last month' against my own notes changes the workflow. MIT licensed and from someone who ships real products.

80/100 · ship

The 'which AI tool actually shipped good code' question is one every eng manager is asking. Waydev's existing Git integration means the attribution layer isn't a cold-start problem — if you're already using it for velocity metrics, the AI measurement upgrade is an obvious yes.

Skeptic
45/100 · skip

This is a well-executed weekend project, not a production tool. It requires GGUF models and manual embedding setup — a meaningful friction barrier for non-technical users. The 'built by a CEO' narrative drives GitHub stars more than the technical differentiation. Obsidian with a local AI plugin gets you here with better UX.

45/100 · skip

Measuring AI contribution by tokens or accepted suggestions is a proxy for value, not value itself. Code quality, bug rates, and time-to-review are better signals, and those are already available in existing tools. Enterprise pricing with no numbers on the website signals this is expensive; wait for a published case study with real ROI data.

Futurist
80/100 · ship

The pattern here — local hybrid retrieval as an MCP server feeding into AI coding agents — will be ubiquitous in two years. Today it's a technical power-user tool; tomorrow it's how everyone's AI assistant knows the institutional context behind the code. qmd is an early, clean implementation of that pattern.

80/100 · ship

As AI coding tools proliferate, the meta-layer question becomes 'which tool compound returns the best for which task type and team composition?' Waydev is building the dataset that will eventually answer that — and the company that owns that benchmark data owns significant influence over enterprise AI tool purchasing decisions.

Creator
45/100 · skip

I manage a lot of notes, references, and creative briefs, but the setup friction here — GGUF models, CLI configuration — makes this inaccessible for most creators. The concept is great; the UX needs a front-end before it reaches beyond developers.

45/100 · skip

For creative technologists who switch tools constantly by feel, a measurement dashboard adds overhead that slows down experimentation. The ROI framing is enterprise-first; indie builders will be better served by just trying tools and shipping.

Weekly AI Tool Verdicts

Get the next comparison in your inbox

New AI tools ship daily. We compare them before you waste an afternoon.

Bookmarks

Loading bookmarks...

No bookmarks yet

Bookmark tools to save them for later