Building the Honest Alternative: Where WriteAmp Came From
I'm going to tell you where WriteAmp actually came from, and the first thing you need to know is that I didn't invent this category, and I've never pretended I did. The core of what WriteAmp does descends from an open-source project called KeyType, and that project is MIT licensed, which is a specific legal gift that made my whole thing possible. I owe it a real debt, and the honest thing is to say so plainly and explain what actually happened.
This is the story of how you build on open source without pretending you built it all yourself, and why the license at the bottom of it matters more than the features on top.
The lineage, told straight
Here is the simple version. KeyType is an open-source project that does system-wide autocomplete for the Mac, ghost text and Tab-to-accept, and it's MIT licensed, which means anyone can use its code, modify it, and build on it, as long as they keep the license notice. I took the core of that project and built WriteAmp on top of it. Not a fork that I renamed and called mine, a foundation that I built on and extended, and I've kept the attribution public since day one.
The MIT license is the part I want to dwell on, because it's the load-bearing wall of the whole open-source ecosystem. It gives permission, freely, to take code and make it yours, to sell the result, to build a business on it, with almost no strings attached beyond keeping the credit. That is a remarkable thing to give the world, and the people who release code under MIT are the reason a solo developer like me can build a serious tool without starting from nothing.
MIT licensed does not mean "anyone can take this and pretend they wrote it." It means anyone can use this, and the deal is that you keep the license and the credit honest. The line between building on something and stealing it is attribution, and attribution is not optional.
What I actually built on top
Here is the part I'm proudest of, and it's also the part that answers the question "so is WriteAmp just KeyType with a new name?" The foundation is the lineage, but the building is years of work on top of it. The modules that make suggestions feel right, the filtering that decides when to stay quiet, the encrypted local history, the language support, the per-app compatibility work, the benchmarks, the updates, the signing and notarization I wrote about in the trust-stack post all of that's the part that turns a promising open-source core into a product you can hand to a non-technical person and say "this will just work."
- The core autocomplete engine and module graph
- MIT licensed, attribution kept
- The idea that local, Tab-to-accept autocomplete is worth building
- The filter that knows when to stay quiet
- Encrypted local history you can read and wipe
- Language support, per-app compatibility, benchmarks, updates
- Signing, notarization, and the boring trust stack
That distinction matters, and not just for my conscience. It matters because "open-source with a real product built on top" is a different thing from "closed clone," and the difference is visible in how the two behave. A clone takes the idea and hides the source. Building on open source takes the code, credits it, and adds the layer of work that turns code into a product. I wrote about the open-source options and what a paid app adds, and this post is the personal version of that argument.
Why I made it paid
Here is the honest question that follows, and I'm not going to dodge it. If the core is open source and MIT licensed, why is WriteAmp a paid product instead of another free fork? The answer is the layer I just described. The foundation was free, the building was not. The compatibility work, the support, the maintenance, the thousand small battles with apps that don't cooperate, that's the part that takes years and doesn't happen on weekends. I'd rather be honest that a product needs revenue to sustain that work than pretend it happens by magic. The open-source post makes the case in detail, and the short version is that free is what the foundation costs, and $29 is what the building costs, and both are fair.
The honest close
I built WriteAmp on the shoulders of an open-source project, and the least I can do is say so clearly, keep the license honest, and give back to the ecosystem that made it possible. That is the deal with MIT, and it's the deal I signed when I built on it. The category is better because KeyType existed, and WriteAmp is better because I didn't have to start from nothing.
The trial is free for 30 days if you want to see what the building looks like on top of the foundation. The source lineage is public if you want to check the attribution yourself, because you should be able to verify the things I'm telling you. Open source built the foundation, and the honest thing is to say so, build well on top, and keep the credit where it belongs.
Sources
- KeyType on GitHub: the MIT-licensed open-source project WriteAmp's core derives from
On macOS 26+ Macs, Apple Intelligence mode stays free even after the trial ends — you always keep a working path to suggestions.
Written by Amit Ashwini, who builds WriteAmp and runs its marketing. More: why the Tab key beats the chat box · mini, midi, and max compared · benchmark methodology.