Email and newsletters decision
Spike
A single developer can implement a narrow Spike-like email client with unified inbox, conversational threads, and LLM summaries, but reproducing Spike’s full team features, hosting, native apps, and polished integrations at production scale is a much larger effort.
Visit website↗Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need — the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship.
What a replacement has to do
- Sync a user's existing email accounts into a unified feed, show conversations as chat-like threads, generate AI summaries/drafts from thread context, and send/receive messages via IMAP/SMTP or provider APIs.
What it still won’t have
- Hosted custom email domains and email hosting
- Shared inbox/teamspaces at production scale (collaboration workflows)
- Integrated video & audio calls, collaborative docs, and SSO
- Mobile/desktop native apps and cross-device polished clients
- Spike AI feed throttling, enterprise integrations, and recording features
What remains hard
- Product polish and ongoing maintenance
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 12 seats.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a single-tenant web email client in Node.js (Express) + React (Vite) + Postgres that: 1) connects to Gmail/Outlook/IMAP via OAuth/IMAP and pulls messages into Postgres; 2) normalizes messages into person-based conversational threads and exposes a chat-like UI for reading and composing; 3) uses an LLM (OpenAI or similar) to generate thread summaries and draft replies on demand; 4) sends mail via SMTP or provider API and updates thread state; 5) provides full-text search using Postgres tsvector; 6) includes tests for mail fetch/sync, summary generation, and send flow, plus basic error handling and rate-limiting. Out of scope: multi-tenant billing, hosted custom domains, mobile/desktop native apps, enterprise SSO, real-time video/audio calls, and advanced team/shared-inbox workflows.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 5 cited sources+3
- Price verified on pricing page+3
- 3/3 assessment runs agreed+4
- Evidence score67
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time — so the same evidence always produces the same number.
How scoring works →Cited sources · 5
Every page the run actually retrieved.
- official productSpike — official product page
- official pricingSpike — Pricing
- official docsSpike — Features
- open sourceFoundry376/Mailspring
- open sourcecloudflare/agentic-inbox
Integrity checks
What held up, and what did not.
