Hello World
We built a blog. Here's why, and what to expect.
We shipped three products before we shipped a blog. That should tell you something about our priorities.
But we kept running into the same problem: we'd solve something gnarly — a licensing edge case, a cross-platform build nightmare, an SSH agent architecture that shouldn't work but does — and there was nowhere to put the story. Twitter gets the hot take. The blog gets the autopsy.
What goes here
Expect posts when we have something worth saying. Not on a calendar. Not to feed an algorithm.
The kinds of things we'll write about:
- Build logs — how we shipped a feature, what broke, what we learned
- Architecture decisions — why we chose Rust, why we went offline-first, why we hate phone-home licensing
- Problems we solved — the stuff that took two days to debug and three lines to fix
- Opinions — on AI tooling, developer experience, privacy, and the state of shipping software in 2026
What doesn't go here
Product announcements with marketing copy. Filler posts to "stay consistent." Anything that starts with "we're excited to announce."
The format
Short when the idea is short. Long when the problem is interesting. Code when code helps. No fluff.
If you want to know when we post, there's a subscribe box at the bottom of the blog page. We'll email you when something new drops. That's it — no drip campaigns, no upsells, no "weekly digest" padding.
We build what's missing. Now we write about it too.