Transcribed with LymeScribe just before posting this: "I realize it's a little bit late in the day to be posting on Hacker News. However, I've been looking at this frog for a good two weeks now, and F it, I'm just going to ship it. I've posted on Hacker News now like three or four times with little to no results. So if a tree falls in the woods..." (I censored the F word, but it transcribed just fine.)

TL;DR: LymeScribe is local speech to text for Mac and Windows: dictate into any app, or drop in a recording and get a transcript with speaker labels, and nothing goes to a server you don't own. On a machine that can handle it, it all runs right there. On anything that can't, or anywhere you'd rather keep transcription in one place, one computer does the work for the rest of the network. Offices care about the second one, because the audio and the transcripts never leave hardware they control.

This whole thing started as a command line program I built to transcribe and label speakers in audio files sitting on my computer, mostly voice notes using Whisper on my gaming PC. A few friends started asking me to run their meeting recordings through it, which I was happy to do until it got frequent enough to be a chore. So I built them an app that they could drag a file onto themselves, with my gaming PC doing the actual work and sending the results back to their clipboard.

That drag and drop piece is still in the app. Since then I added real time dictation, which uses the same local models. When I started thinking about actually selling this thing, I found the market was more crowded than I expected, which was humbling for about a day. What kept me going is that none of the others let one machine do the work for everyone else... that and there's just something sort of cool about owning and using my own transcription software. So, here we are.

An older machine can handle its own dictation on the small English models. I found that out when I tried the app on a ten year old iMac expecting it to fail, and deleted the code I'd written to keep machines like it out. Speaker labels are the part that still wants real hardware, and that's where pointing that old machine at a stronger one on the network earns its keep. One license covers the house.

It's local by design, and you can test that yourself: unplug the Ethernet mid dictation and it keeps going. Works on a plane. The free client never talks to me at all. Unlocking hosting means one activation call, and after that the license is verified locally against a signed document, so an activated install keeps working with no internet and would keep working if my licensing server went away. AI assisted summaries and translation are experimental. They ship turned off, and you can turn them on if you dare. They only talk to an endpoint you choose, your own key or a local model.

The client is free on Mac and Windows. Hosting is a one time $39 unlock with a 7 day trial that starts the first time you host a transcription. It's a perpetual license: you own this major version, point updates are free, and if there's ever a next major version it's a discounted upgrade rather than a new purchase. I'm tired of renting everything, aren't you?

Two things worth knowing before you download. The Windows installer is signed, but the certificate is new enough that Chrome and SmartScreen may still warn you about it. And the paid unlock is US only for now, while I work out the international side.

Feedback welcome, especially from anyone who has fought text injection on Windows. There's also a heavier server for offices, administered through a web app that handles keys, transcription history, logs, etc.

Frog reference: "There's a saying: if you have to eat a frog, it's best you don't spend a whole lot of time looking at it. And if you have to eat two, don't start with the small one."

Randy Pausch - Time Management - https://www.youtube.com/watch?v=oTugjssqOT0

SaaS Onboarding Benchmarks Report 2026 (real data from 464 products)