Automation and integrations decision
Robotomail
A capable developer can build a useful subset (programmatic mailboxes, send/receive via providers, webhooks, threading) in about a week, but matching Robotomail's full managed deliverability, custom-domain automation, and production-grade MX handling is operationally heavy and costly to replicate.
Visit website↗Built by John Joubert, who ships 3 products in this index
$19/mo
$228/yr
Read off the official pricing page.
$100one-off40 h to build
$50/mo4 h/mo upkeep
On cash alone, building overtakes the subscription at 4 seats.
No open-source build does this yet
Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.
What a replacement has to do
- Create mailbox via API, send outbound mail through a delivery provider, accept inbound mail (MX) and parse/store messages, notify agents via webhooks / SSE, basic threading via In-Reply-To and Subject matching.
What it still won’t have
- Managed deliverability engineering and IP reputation tuning
- Automatic, production-grade DKIM/SPF/DMARC issuance and verification for custom domains
- Dedicated IPs, prioritized support, and service SLA
- Effortless inbox onboarding via /skill page and turnkey agent self-onboarding
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 4 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 minimal Robotomail replacement: use Node.js + Express, Postgres, and S3-compatible storage; deploy on a single small cloud VM and an object storage bucket. Implement: (1) API endpoint to create/manage mailboxes and issue API keys (store mailboxes in Postgres), (2) send endpoint that composes MIME and forwards to a transactional provider (Resend or SMTP) and records delivery status, (3) inbound handler that accepts relayed inbound messages (or integrates with a relay) parses MIME and stores body and attachments in S3, (4) real-time notifications via webhooks and an SSE /events endpoint with HMAC-signed payloads and retry logic, (5) basic threading by using In-Reply-To/References headers and subject normalization, (6) CLI with send and messages commands. Out of scope: building a full SMTP MX mail server cluster, automated DNS provisioning for custom domains, advanced deliverability tuning and dedicated IPs. Include input validation, retries, logging, unit tests for core API handlers, and integration tests for send/receive flows.
How we checked
How the score was reached
- Partly verdict base52
- 3 cited sources+3
- Price verified on pricing page+3
- 3/3 assessment runs agreed+4
- Evidence score62
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 · 3
Every page the run actually retrieved.
- official productRobotomail — official product
- official pricingRobotomail Pricing
- official docsRobotomail Docs
Integrity checks
What held up, and what did not.
