[verdict][generated prompt][source: hey.com]
Can I vibecode HEY?
// the value is the network, the data or the infrastructure
You can build an email client, but replacing HEY means running a trustworthy email service: deliverability, spam filtering, abuse handling, storage, mobile apps, and reputation.
confidence: high
what it is: Opinionated paid email service with screening, bundles, and privacy defaults
Buildability index · an editorial game
- Price 8.25 $/month weight: plus 1
- Time not realistically solo weight: minus 3
- Category email no weight
- Moat infrastructure scale · brand and trust weight: minus 3
- Confidence high weight: plus 1
- What you lose 6 items weight: minus 3
- Site hey.com (si apre in una nuova scheda) no weight
It is not close. The prompt below rebuilds a piece, not the product.
Gioco editoriale: il verdetto dice se un agente può, l’indice se conviene.
What you build
Build a personal mail client on top of IMAP/SMTP or a hosted mailbox; do not try to replace the global email service layer casually.
what you need
- existing email provider or mailbox
- IMAP/SMTP APIs
- spam filtering if hosting
- domain/DNS if custom email
Valuable no: the UI is cloneable, but email infrastructure is not an afternoon project.
The prompt
The verdict is NOT REALLY, and the prompt stays anyway: it does not replace the app, it rebuilds the part that really is code. The rest is the moat.
Build me an email client with HEY's screening and bundling ideas, running on
top of a mailbox I already pay for (Fastmail, Gmail, anything with IMAP).
Requirements:
- A local web app: Node + Express + better-sqlite3, binds to localhost;
imapflow for reading, nodemailer for sending, creds in .env.
- The screener: mail from first-time senders lands in a screening view where I
approve or block; decisions persist in SQLite and apply to all future mail.
- Bundles: approved senders get a category; newsletters render in a batched
feed view, receipts in a paper-trail list; only approved humans hit the
inbox.
- Reply-later: mark a thread and it sits in a persistent to-answer stack until
cleared.
- Write decisions back as IMAP folders and labels so my phone's mail app
roughly mirrors the sorting.
- Strip remote images in the reading pane by default.
- No accounts of its own, no telemetry; mail stays at my provider.
- Out of scope: running an SMTP server, custom domains, and mobile apps. Do not
replace the mail service itself; deliverability and spam reputation are the
product and cannot be rebuilt solo.
- README: per-provider app-password setup, and a warning that Gmail OAuth is a
project of its own, use an app password or Fastmail to keep this a weekend.Prompt generated from the data on this page, not reviewed by hand yet. In English on purpose — it is the language coding agents work best in.
What you lose
- email deliverability
- spam/abuse systems
- storage reliability
- mobile apps
- identity/reputation
- support
Why people still pay
They pay because email is infrastructure; deliverability and trust are the product.
moat: Infrastructure scale Brand and trust what a moat is
deliverability/compliance/infrastructure
Who has already built it
Starting from here is still vibecoding: the prompt is for when you want it exactly your way.
- Mail-in-a-Box (opens in a new tab) — Open-source personal mail server stack; useful prior art but deliverability remains the mo (alive)
Do you agree?
The vote balance
Ancora nessun voto: il tuo è il primo.
Nessun voto ancora — il primo pesa.
