Hi, I'm Elo Lin 👋
Founder · Indie Developer · I build tools because the existing ones let me down.
Every project here started the same way: a tool I relied on was slow, clunky, buggy,
or quietly broke at the worst moment — so I rebuilt it the way it should have worked.
Software that's fast, that just works, and that makes the day a little easier.
🧭 Why I build
I have a low tolerance for tools that fight back.
The app that takes five clicks for a one-second job. The CLI that crashes on the input it should obviously handle. The "smart" assistant that forgets everything the moment you close it. The dashboard that can't filter the one thing you actually need. These small frictions add up — they steal hours, and worse, they steal focus.
So I build the fix. My work lives at the intersection of three ideas:
🛠 Fix the broken workflow — when a tool is unreliable or awkward, I'd rather rebuild it than route around it forever. Reliability is a feature.
⚡ Make it fast & effortless — a tool should disappear into the task. Sub-second response, sane defaults, one command instead of ten.
🌱 Make daily life easier — automate the repetitive, remember the tedious, hand back the time. The best tool is the one you stop thinking about.
The recurring principles: local-first (your data stays on your machine), single-binary (no setup tax), and zero telemetry (no one's watching). Tools should serve you — not the other way around.
Replies