qwicmail
Why qwicmail

Most "transactional email" platforms are newsletter platforms in disguise.

qwicmail is built for the boring, important mail — receipts, login codes, delivery confirmations — that has to land every single time. Three things we do differently.

1

Closed onboarding, by design.

We turn down most signup applications on purpose. Every tenant on qwicmail is verified by a human — business name, use case, sending volume, the lot. There is no self-serve sign-up with a credit card.

The reason is simple: shared sending infrastructure means shared reputation. One sloppy newsletter sender on a shared pool tanks inbox placement for everyone on it. We don't let that happen.

Application flow
  1. 1
    Submit application. Business name, contact, what you'll send, expected volume.
  2. 2
    Human review. A real person looks at your application, typically same day.
  3. 3
    Invite link. Approved? You get a portal invite, set a password + 2FA, complete KYC.
  4. 4
    Warm-up. Daily cap starts at 1k and escalates to 10k then uncapped as your reputation builds.
2

Our own MTA. Our own IPs.

We don't resell another provider. The SMTP engine, the dispatcher, the bounce processor, the suppression service — written in Go, running on our own infrastructure, on IPs we own and announce.

That matters because it means we can fix problems at the level where problems happen — TLS negotiation, MX retries, MTA-STS policy lookup — instead of opening a ticket with an upstream vendor.

What's in the stack
  • SMTP Homegrown engine built on emersion/go-smtp. DKIM-signs every message; opportunistic + enforced TLS where the recipient supports it.
  • DNS MTA-STS policy lookup before every send to compliant recipients (Gmail, Yahoo, iCloud, …).
  • VERP Per-message envelope-from so every bounce routes back to the exact message and the exact tenant.
  • UNSUB RFC 8058 one-click unsubscribe header on every send. Gmail + Apple Mail surface the affordance natively.
3

Humans on call, not a status page.

Bounce rate spikes? IP gets a temporary reputation hit? A senior deliverability engineer picks up the phone. No tier-1 triage, no canned reply that asks you to "check your DNS records."

We charge a premium because deliverability ops is what you're actually paying for. The infrastructure is the table stakes.

What "on call" actually means
  • Direct line to deliverability ops via your portal — no shared inbox.
  • Proactive reputation monitoring — we tell you before Gmail does.
  • A real engineer handles the postmaster-tools dance with mailbox providers.
  • If we make a mistake we tell you about it. Postmortems shared openly.

When qwicmail is the wrong fit

We are not the cheapest. We don't do open self-serve sign-up. We don't do marketing-newsletter A/B testing or behavioural-trigger funnels. If you're shopping for cheapest cost-per-thousand or building a marketing automation stack, you'll be happier elsewhere — and we'll be happier not having you on the platform.