QMailing
QMailing — Create mailboxes, not accounts
Solo dev, ~5 years backend. For a while now I've been building QMailing in my spare time.
The itch: every project, client, or random side thing meant another email account. Gmail here, Outlook there, some alias service I signed up for in 2019 and forgot about. Constant tab-juggling, logins, verification dances.
I wanted mailboxes, not accounts. So that's what I built:
Spin up support@ or sales@ in 3 seconds, no new account
Reply from any of them in one click — one inbox, dozens of faces
Group mailboxes by client/project (color-coded, because search breaks past ~5)
EU-hosted, no body scanning, no phone on signup
Bring your own domain — those mailboxes don't count toward your plan limit
A couple of things I'm proud of as a dev:
Full REST API (scoped tokens, webhooks, RFC-7807 errors) — email exposed like a real product
An MCP server on day one, so an AI agent can read, triage and send through scoped, revocable tokens. This is the part I think is underrated — your inbox becomes something your agent can actually operate.
Stuff I'm still chewing on and would love input from this crowd:
Is "email for agents" a real wedge, or too early to lead with?
Free-tier economics on email storage are brutal — curious how others model lifetime storage caps.
Free forever for hobby use, no card. Would genuinely love feedback — especially the harsh kind.
Live at qmailing.com
1 Comment
The product is interesting, but I would be careful about leading with “email for agents” too early.
That angle is probably real, but it may be too early for the first buyer to understand quickly. “Mailboxes, not accounts” is much clearer because it starts from an existing pain: too many inboxes, identities, clients, aliases, and login flows.
The agent angle feels stronger as the expansion layer:
First sell: one inbox for many project/client mailboxes
Then expand: API/MCP lets agents triage and act across those mailboxes safely
That way the buyer does not need to believe in agentic email before understanding the product.
For first users, I’d probably target solo operators and small agencies managing multiple client/project identities, not broad privacy-email users. They already feel the pain and can justify paying faster.
Happy to put a tighter version in writing if useful. The useful part would be mapping the positioning, first buyer segment, free-tier limits, and whether the agent wedge should be headline or secondary.