HN Showcase
Back to browse
Inbox.camp, AWS WorkMail Replacement

Inbox.camp, AWS WorkMail Replacement

by heythisischris·Apr 1, 2026·4 points·4 comments
Visit ProjectView on HN

AI Analysis

●●SolidSolve My ProblemShip It

WorkMail sunset replacement keeping mail in your S3 — Zoho doesn't do that.

Strengths
  • •Stalwart Mail Server in Rust handles IMAP/SMTP/JMAP with AGPL license.
  • •Cross-account IAM role is fully revocable — delete it, we lose access.
  • •Auto-configures MX, SPF, DKIM, DMARC in Route 53 without CloudFormation debugging.
Weaknesses
  • •Launching Summer 2026 means no production validation yet.
  • •Email hosting is crowded — Proton, Zoho, FastMail already established.
Category
SaaS
Target Audience

AWS users migrating from WorkMail, small businesses

Similar To

AWS WorkMail · Zoho Mail · Stalwart Mail Server

Post Description

I've been running client email on WorkMail for a few years. When AWS announced the sunset (March 2027), they suggested switching to Zoho, Kopano, and Zoom Mail- none of which keep your data in your own AWS account.

So I'm building a replacement. inbox.camp sits on top of your existing SES, S3, and Route 53. Mail storage stays in your S3 bucket, sending/receiving goes through your SES, DNS is auto-configured in your Route 53. We're the thin client- IMAP, SMTP, and a web interface.

Stack: Hono + HTMX on Lambda for the web UI, Stalwart Mail Server (Rust, AGPL) for IMAP/SMTP/JMAP, client's own SES/S3/Route 53 for infrastructure. Cross-account IAM role for connectivity, fully revocable. Launching this summer. Happy to talk architecture, answer questions, or hear why this is a terrible idea.

Similar Projects