iCloud + Gmail
Your @icloud.com address. Your @gmail.com. Maybe a Workspace domain too. STAMP collapses them into one calm queue and handles aliasing without asking.
Run both providers like first-class citizens. Triage them once. Reply from the right address. Stop opening two apps for one job.
Get early accessApple's mail UX nudges you toward iCloud. The reality is most people use it for one thing: Apple receipts. STAMP makes it visible without making it loud.
Gmail's mailto handlers and iCloud's reply behaviour don't compose. Replies leave from the wrong account. Threads break. STAMP fixes that.
Apple Mail for iCloud, Gmail web for Gmail. That's two windows, two muscle memories, one bad day. STAMP is one of each.
iCloud
STAMP speaks iCloud's quirks: aliases, app-specific passwords, Hide My Email. Connect once and it just works.
Gmail
OAuth login, native API. Labels, send-as aliases, threading — all preserved correctly. No 'IMAP-mode Gmail' weirdness.
Aliases
iCloud thread? Reply from iCloud. Gmail thread? Gmail. Hide My Email alias? STAMP replies through the alias and the recipient sees the right thing.
“My iCloud was a graveyard. STAMP made it part of my actual workflow without making it loud.”
Early access user · Independent designer
If you've used a Mac for more than three years you have an iCloud Mail address. You probably also have at least one Gmail. The cohort of people running iCloud-as-personal and Gmail-as-work is enormous, and almost nobody handles both well.
Apple Mail handles iCloud beautifully and Gmail acceptably, but it's a flat-list app with no triage layer. Gmail web doesn't speak iCloud at all. Mimestream is excellent for Gmail and ignores iCloud entirely. Spark is fine but doesn't have STAMP's triage UX.
STAMP treats both providers as first-class. Both authenticate cleanly. Both round-trip labels and folders correctly. Both expose aliases including iCloud's Hide My Email. The unified queue is real — same shortcut, same view, same keyboard surface.
iCloud's Hide My Email is one of the best privacy features Apple has shipped. It's also routinely broken in third-party clients. Replies sometimes leave from your real iCloud address, defeating the whole point. STAMP detects Hide My Email aliases and replies through the alias correctly. Your privacy stays intact.
Gmail's send-as aliases work similarly. If you've added a custom domain as a send-as in Gmail, STAMP exposes it and replies from it when the original thread landed there. The cognitive load of 'which alias am I in' goes to zero.
Subscriber-level practical effect: a freelancer with a personal Gmail, a Workspace domain, and an iCloud address can run all three from one window and never reply from the wrong one.
One headline. One queue. One search. One shortcut surface. STAMP doesn't show you 'iCloud inbox' and 'Gmail inbox' as two side-by-side panes. It shows you the seven threads that need you today across both, ranked by signal.
Per-account view is one keystroke away if you ever need it. ⌘+K, type 'icloud', hit return. You're filtered. Hit escape. You're back to unified.
Triage is unified too. A VIP rule applied to a sender works whether they email your iCloud or your Gmail. Snooze a thread on iCloud, it surfaces in the unified queue. Tags applied at the unified level apply to the underlying provider correctly.
Yes. STAMP supports iCloud's app-specific password flow as well as direct OAuth where available. If you have 2FA on your Apple ID, you'll generate an app-specific password during setup — the standard Apple flow.
Yes. STAMP detects Hide My Email aliases and replies through them so the recipient never sees your real iCloud address. The privacy guarantee Apple provides survives intact.
Yes. Any send-as alias you've configured in Gmail web shows up in STAMP automatically. STAMP picks the right one based on the originating thread.
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