Freelance developers
GitHub notifications, client threads, Stripe receipts, recruiter spam. STAMP triages all of it without forcing you to leave the keyboard.
J/K to move. R to reply. ⌘+Return to send. The same vim muscle memory you've had for a decade, applied to email.
Get early accessAuto-generated PR mentions and CI failure pings bury the actual question from the actual person paying you.
You can do J/K and R if you're willing to learn three plugins and a config file. Or you could just use a client that ships those defaults.
Twelve cold InMails a day across four addresses. STAMP filters them automatically, and the ones that get through are warm enough to read.
Keyboard
J/K, R, E, S, U, ⌘+K. The same muscle memory you've used in tmux for years, applied to your inbox. No mouse needed for any common action.
Filters
Automated mail goes to its own quiet view. Real human threads stay loud. The headline only counts the threads that actually need a reply.
Private
Classification runs on your Mac. The thread containing your client's auth token is never shipped to a third-party server for sorting.
“It's the first email client where I don't reach for the trackpad once a session. That's all I needed.”
Early access user · Senior contractor, infra
There's a small but loyal cohort of developers who use mutt or aerc because every modern email client is a mouse trap. Apple Mail's 'keyboard support' is a long list of menu shortcuts you have to look up. Gmail's keyboard mode is an afterthought.
STAMP is the first client where the keyboard isn't a feature, it's the architecture. J and K are next and previous. R is reply. ⌘+K is the universal jump. The shortcut sheet is twelve keys and you'll have memorised it before lunch.
What you get on top of terminal mail is the actual modern stuff: rich rendering when you want it, plain rendering when you don't, real attachment handling, and triage that's smarter than 'read or unread'.
The morning is fifteen minutes. You open STAMP. Headline says four threads need attention — two from clients, one invoice question, one from a partner. GitHub digests are folded out of view. Recruiter cold emails are gone.
You handle the four. You snooze the partner thread to 4 p.m. when you said you'd reply. The invoice question gets a one-line reply with a Stripe link auto-pulled from your last conversation. Done.
At 4 p.m. the snoozed thread surfaces itself. You reply from the right domain — the one tied to the client account, not your personal Gmail. The CRM that lives in your inbox stays accurate without effort.
End of week, STAMP shows you a recap: every commitment made by email, every invoice sent, every thread still open. You forward it to your accountant or your partner. The week closes cleanly.
Plain-text rendering toggle. Some threads are better as text. STAMP lets you flip to plain in one keystroke and stays there for the sender if you want.
Code-block-aware reply. If the original email contains a block of code, STAMP preserves indentation and monospace in the reply. Sounds small. It isn't.
Aliases that work. Your hello@ address replies as hello@. Your personal Gmail replies as your personal Gmail. You'll never explain why an email came from the wrong domain again.
Snooze that respects working hours. Snooze to 'tomorrow morning' is 9 a.m. on a weekday — not 7 a.m. on a Sunday because that's exactly 24 hours from now.
Not yet. The macOS app ships first because that's where the triage UX matters most. A CLI for sending and listing is on the roadmap. The keyboard surface in the app is comprehensive enough that most users stop wanting one.
Yes. Compose in markdown, send as rich HTML. Toggle to plain-text mode for clients who prefer it. The choice persists per recipient.
No. Triage is filename and metadata only. Attachment contents are never opened by the classifier. Your client's source stays local and untouched.
STAMP is a paid subscription from $9 a month, locked for life on whichever plan you pick if you join the founding window.
Claim my seat