Hi HN, I’m Sarah. I built InboxNest because I run several small projects and their support email had become a mess of aliases, forwarding rules, providers, and separate inboxes. It technically worked, but I was checking too many places and mixing customer conversations with unrelated email.

Most support tools I looked at felt designed for teams with ticket queues, assignments, SLAs, and a lot of configuration. I’m a solo operator. I wanted one place to answer customer email for every project without turning support into another system I had to manage.

InboxNest lets you create branded addresses across multiple domains and manage them from one inbox. Replies go out from the same address that received the message. If a domain doesn’t already use email, InboxNest can receive its support mail directly through MX records. If it already uses Google, Microsoft, or another provider, you can forward only the support addresses you want and leave the rest of the domain’s email alone.

It also includes a customizable website contact widget and a hosted contact page. Messages submitted through either become regular email conversations in the inbox, and the customer receives replies by email.

The application is built with php, mysql, nginx, Alpine, Tailwind, and Postmark. The inbox UI was actually the straightforward part. Most of the work went into the mail plumbing and trying to prevent one customer from damaging deliverability for everyone else.

Connected domains use DKIM and custom Return-Paths. Postmark webhooks are authenticated, idempotent, and recoverable after failed processing. Outbound sending has separate limits at the address, domain, and account levels. Hard bounces suppress the recipient for that domain, and spam complaints or unusual sending can automatically pause outbound mail without stopping incoming messages.

I’ve deliberately kept the scope narrow. InboxNest is for one-to-one customer conversations. It doesn’t send newsletters, purchased lists, cold outreach, or marketing campaigns, and I’m not trying to turn it into an enterprise help desk.

I’d especially appreciate feedback on three things:

1. Is the choice between direct MX and forwarding understandable? 2. Is the value clear for someone managing several products or businesses? 3. What about connecting a domain to a new service would make you hesitate or decide not to continue?