Disclosure. We build a product in this category, so we have an interest in how this question gets answered. That's exactly why the numbers below are counted rather than asserted, the method is stated, and every quote carries its author, platform and date.
If you've thought about building your own meeting capture instead of paying for one, you're in a large group. We wanted to know how large, and what happens to those projects afterwards. So we counted.
The honest summary: building is common, cheap to start, and decays fast. None of that makes it the wrong call. It does mean the decision deserves better inputs than a Show HN title.
Key Takeaways
- In the 90 days to 2026-08-15, 162 new GitHub repos matched meeting transcription, local notetaking or agent memory. Median: 3 stars.
- 113 of the 162 sat at five stars or fewer, 30 at zero, and 58 had already gone a full month without a push — inside the same window they were created in.
- Across 118 dated items on five platforms we found 109 build artifacts and 9 product evaluations. On GitHub and dev.to, the evaluation count was zero.
- The people building say why, plainly, and export lock-in is the trigger more often than price.
What did we count, and how?#
We swept five platforms for items published between 2026-05-17 and 2026-08-15, then hand-checked every date before including anything. Titles proved unreliable — several posts carrying "2026" turned out to predate the window by a year — so dates came from platform APIs rather than page scraping.
The GitHub layer is a repo-creation query against meeting transcription, local notetaking, and agent memory and context. It returned 162 repositories created inside the window. Star counts and last-push timestamps were read at the same time, on 2026-08-15.
The five-platform layer is narrower and hand-picked: 118 dated items. Each was classified as either a build artifact (someone shipping a thing they made) or a product evaluation (someone comparing products). That classification is a judgment call, and it's the one number here we'd expect a careful reader to argue with.
Two limits worth stating up front. Reddit isn't in this data at all — it was unreachable from the environment that ran the sweep, and r/selfhosted and r/LocalLLaMA are exactly where the abandonment conversation would sit. And a star count measures attention, not usefulness. A tool with three stars can still be the right tool for the person who wrote it.
What does the star distribution actually show?#
Concentration at the bottom. Of 162 repos created in the window, 113 had five stars or fewer and 30 had none at all, measured on 2026-08-15. The median was 3.
Seventy percent of the window's output sat at five stars or fewer. That's the shape of a category where the marginal cost of starting has fallen close to zero, and the cost of finishing hasn't moved at all.
Is the build side growing or decaying?#
Both, at the same time. Creation held steady through the window — 23 repos in May, 62 in June, 62 in July, and 15 in the first half of August. Meanwhile 58 of the 162 had already gone a full month without a push, inside the same window in which they were created.
August looks like a collapse and isn't — it's half a month. Read the first three columns as the trend and the fourth as a partial count.
The decay figure is the one that should change a decision. A month of silence inside a 90-day window means a third of these projects were abandoned before they were old enough to be maintained. Not abandoned after a hard year of upkeep. Abandoned during the build.
The written side shows the same shape. Across the window, 403 dev.to posts matched the topic keywords, with a median of 0 reactions and 342 of the 403 carrying no comments at all. The build guide is written far more often than it's read.
Where does the writing actually happen?#
Overwhelmingly on the build side, and the split differs sharply by platform. Across 118 dated, hand-checked items we found 109 build artifacts and 9 product evaluations.
On GitHub and dev.to the evaluation count isn't low. It's zero. Nobody in that window used either platform to compare products in this category. The comparison content that does exist on dev.to is vendor-authored and falls outside the window.
That asymmetry matters when you're researching a decision. If you search this category, you'll mostly find people describing what they built, because that's what gets written. You won't find many people describing what happened six months later.
Why do people build, when the products exist?#
Export lock-in, more often than price. The clearest case in the window came from someone whose existing workflow broke: "Granola are cracking down on their auth and I can no longer pull my meeting notes out and put them in Obsidian (my plugin is gonna have to be deprecated)" (tomelliot, Hacker News, 2026-07-16).
The principle underneath it got stated in one line, by someone who says they aren't a developer at all: "If I can't read it without you, it's not really mine" (dthcst, Hacker News, 2026-07-29). The same comment opens "I got tired of my stuff living on someone else's server, so I ended up building my own local memory thing. Not a developer at all, just stubborn."
Some build because the products fail on fundamentals rather than on features. "I did a survey of many and they all (that I could find) skip the fundamentals" (blopker, Hacker News, 2026-06-14), in a comment that goes on to list crash recovery among the gaps.
And some build because switching tools threatens something they've already assembled. One commenter listed the wiki, feature plans, retrospectives and skills built up around their existing setup. The barrier to trying anything new was "will I maintain my edge" (starcalleryisss, Hacker News, 2026-07-07).
Price appears too, and it's specific rather than general: "I can't stand monthly rent forever" (stevenicr, Hacker News, 2026-07-28).
What does the hostility in these threads target?#
Builders, mostly, which is not what you'd expect. The sharpest replies in this corpus land on the person who shipped the weekend project rather than on vendors or subscriptions. The trigger is the framing rather than the code.
On a Show HN presenting an open-source alternative built in a weekend: "This is by far the least interesting/worst kind of project emerging lately. 'I didn't want to pay trivial money for a product, so I paid nontrivial money to have an AI make a version that's worse in every way that matters' Who cares?" (vitally3643, Hacker News, 2026-07-27).
In the same thread, from a different angle: "I will never understand that thinking. You didn't like that a service you need asks to be paid, so you paid an LLM to create a free competitor that you now advertise online. Do you not see the race to the bottom you're contributing to? $24 doesn't sound outrageous at all." (dgellow, Hacker News, 2026-07-27).
We're quoting these because they're the market's own reaction, not because we share them. A vendor repeating this as an argument for buying would be borrowing hostility aimed at exactly the people most worth listening to. The useful signal is narrower: what draws fire is the weekend framing rather than the building.
Builders themselves are often the most realistic voices in the room. One maintainer of a local transcription app wrote: "The next gen of models will prob one shot my app anyway" (marshalla, Hacker News, 2026-07-29).
Does anyone switch, in either direction?#
Yes, both ways, and neither is common enough in this window to call a trend. The fullest arc came in a single sentence: "I found MacWhisper to be great. I built and used my own solution for a couple of years before settling on MacWhisper" (schappim, Hacker News, 2026-07-16).
Note the timescale. Two years of running his own, then a switch. That reads as a long working solution being retired for a better one, rather than a weekend experiment ending in disappointment.
The reverse direction is at least as well attested. Several commenters in the window reported surveying existing products and finding the survey itself was what pushed them to start building. Nobody in this corpus wrote up their own abandonment, which is a gap in the evidence rather than a sign it doesn't happen — abandonment doesn't produce a post.
How should you actually decide?#
Use the counts as a prior, not a verdict. Three questions separate the builds that survive from the 58 that went quiet.
- Is capture the whole job, or the first step? Local transcription is a solved weekend problem. Getting back into a year of it is not, and that's where homemade systems and bought ones both tend to stop.
- What breaks when you stop maintaining it? The failure modes practitioners name — diarization, mic and system audio as separate lanes, crash recovery — are ongoing work, not one-time work.
- What's the actual trigger? If it's export lock-in, building solves it permanently. If it's the monthly cost, check the number against your own hourly rate before starting.
If you're building because you want to own the file, you're in the strongest position in this data. That's the motive with the clearest statement and the best survival odds, because the goal is reachable in a weekend and stays reached.
Frequently Asked Questions#
How many people are building their own meeting tools?
More than the star counts suggest. In the 90 days to 2026-08-15 we counted 162 new GitHub repos matching meeting transcription, local notetaking or agent memory, plus 403 dev.to posts on the same topics. Attention is concentrated at the bottom: median 3 stars, median 0 reactions.
Do these projects get maintained?
Often not. 58 of the 162 repos had gone a full month without a push inside the same 90-day window they were created in, measured 2026-08-15. That's abandonment during the build rather than after a long maintenance burden.
Is it cheaper to build than to buy?
Depends on what you count. The stated triggers in the window were export lock-in and subscription fatigue — "I can't stand monthly rent forever" (stevenicr, Hacker News, 2026-07-28). The recurring counter-argument is that a weekend of your time plus model costs isn't free either.
What breaks in homemade meeting capture?
Practitioners name the same set repeatedly: diarization, mic and system audio bleeding into one lane, crash recovery, and hallucinated filler in silence. One builder surveying existing tools said they "all (that I could find) skip the fundamentals" (blopker, Hacker News, 2026-06-14).
Why is there so little product comparison content?
Because almost nobody writes it. Across 118 dated items we found 9 product evaluations against 109 build artifacts, and on GitHub and dev.to the evaluation count was zero. The category's public writing is dominated by people documenting what they made.
What this changes#
The build-versus-buy argument in this category usually gets fought with anecdotes. Now there are counts: 162 repos, median 3 stars, 113 at five or fewer, 58 stale inside the window, 109 build artifacts against 9 evaluations.
None of that says don't build. It says the distribution is heavily weighted toward projects that stop. The writing you'll find while researching is skewed toward beginnings rather than outcomes. And the motive you start with predicts a lot.
We'll re-run this count and publish the delta. The interesting number is how many of the 162 are still getting pushes in six months.
Sources#
All Hacker News items retrieved and date-verified via the Algolia API on 2026-08-15.
- tomelliot, "Ask HN: Best meeting transcription daemon for macOS?", Hacker News, 2026-07-16. https://news.ycombinator.com/item?id=48936123
- schappim, comment on the same thread, Hacker News, 2026-07-16. https://news.ycombinator.com/item?id=48941504
- marshalla, comment on the same thread, Hacker News, 2026-07-29. https://news.ycombinator.com/item?id=49101488
- dthcst, comment on "Show HN: Echologue – the private AI voice journal I built for myself", Hacker News, 2026-07-29. https://news.ycombinator.com/item?id=49096901
- blopker, comment on "Show HN: Trace – Offline Mac meeting transcripts you can flag mid-call", Hacker News, 2026-06-14. https://news.ycombinator.com/item?id=48533220
- vitally3643, comment on "Show HN: Descript wanted $24/mo, I built an open-source alternative in a weekend", Hacker News, 2026-07-27. https://news.ycombinator.com/item?id=49073386
- dgellow, comment on the same thread, Hacker News, 2026-07-27. https://news.ycombinator.com/item?id=49072256
- stevenicr, comment on the same thread, Hacker News, 2026-07-28. https://news.ycombinator.com/item?id=49079604
- starcalleryisss, comment on "Show HN: Rowboat – Open-source, local-first alternative to Claude Desktop", Hacker News, 2026-07-07. https://news.ycombinator.com/item?id=48824783
- Original analysis, 2026-08-15. GitHub repo-creation query for meeting transcription, local notetaking, and agent memory and context, restricted to repos created 2026-05-17 to 2026-08-15: 162 results, with stars and last-push timestamps read on 2026-08-15. Separately, 118 dated items across Hacker News, GitHub, dev.to, YouTube and Medium, hand-classified as build artifact or product evaluation. Reddit is absent from the dataset and was not sampled.