Use cases

One platform, many ways to route mail.

Whether it's a single personal domain or two hundred client domains, the job is the same: get mail to the right inbox, authenticated, and prove where it went. Here are the most common ways people use JoltMx.

Personal

A professional address on your own domain

Send and receive as you@yourname.com instead of a free webmail address - while still reading everything in the inbox you already use.

  • Forward you@ straight to Gmail or Outlook
  • Reply as your domain over authenticated SMTP
Create your first alias →

Domain collectors

Mail for every side project and parked brand

You own domains for ideas you might build and brands you might use. Each one occasionally gets real mail - but none of them justifies a paid mailbox.

  • One catch-all rule covers a whole domain
  • Add domains without per-mailbox costs
Set up a catch-all →

Privacy

A unique address for every signup

Give each service its own address - netflix@, bank@, shop@ - so you can see who leaked your details and cut off spam at the source.

  • Catch-all means new addresses just work
  • Block a leaking sender at the route
How routing rules work →

Small business

Role addresses without buying seats

hello@, support@, and sales@ should reach the right person - not sit in a mailbox nobody pays attention to.

  • Point each role address at the right inbox
  • Fan one address out to the whole team
Forward to a team →

Agencies

Manage client domains without running mail

Clients want addresses on their own domains. You want routing control and delivery visibility - not to become the mail operator for every account you manage.

  • Forward client mail to verified destinations
  • Explain exactly where a message went
See who it's for →

Product teams

Inbound mail without the SMTP plumbing

Your product needs to receive mail on a custom domain and hand it to a helpdesk, queue, or workflow. JoltMx owns the SMTP edge so your team doesn't run mail servers.

  • Route support@ to your helpdesk inbox
  • Every message kept as a raw .eml for debugging
See the pipeline →

Two-way

Reply as your domain, not just receive

Forwarding gets mail in. Authenticated SMTP submission lets you send and reply as your alias, properly DKIM-signed so it lands in the inbox.

  • Add JoltMx as the SMTP server in any client
  • SPF-aligned and DKIM-signed automatically
Send from your alias →

Continuity

Keep old domains reachable after a move

Rebranded, merged, or retired a domain? Mail still arrives for years. Forward it somewhere current instead of letting it bounce into a void.

  • Catch-all forwards every legacy address
  • No mailbox to maintain for a dead domain
Add a domain →

Deliverability

Authenticated forwarding you can audit

Forwarding usually breaks SPF and lands mail in spam. JoltMx checks SPF, DKIM, and DMARC on every message and applies SRS so forwarded mail stays trusted.

  • Per-message auth results and delivery timeline
  • Sender filtering and Spamhaus screening
SPF, DKIM & DMARC →

Don't see your use case?

If you need inbound mail on a domain routed somewhere sensible, JoltMx almost certainly fits. Tell us what you're trying to do.

Free during beta

Start routing mail in minutes.

Point your MX records at JoltMx. Add a domain. Create your first rule. Done.

No credit card required  ·  Free tier stays free