Who It's For

Between a shared inbox and running your own mail server.

JoltMx is for people who need inbound mail on their domains without the cost or maintenance of full mailbox infrastructure for every project, brand, or client.

Start free See how it works

People with too many domains

You own domains for side projects, parked brands, and experiments. Each one needs a forwarding address, not a separate paid inbox.

Use aliases and catch-all rules without spinning up mailbox accounts.
Keep contact, support, and purchase receipts flowing into the inboxes you already check.

Agencies and client domain wranglers

Clients want addresses on their domains. You need forwarding and delivery visibility without becoming the operator of a mail platform for every account.

Forward client-domain mail to verified destinations your team already uses.
Keep enough delivery and auth visibility to explain where a message went when someone asks.

Products that need inbound mail without the plumbing

Accept inbound mail on a custom domain, route it somewhere useful, and keep a trace of what happened. JoltMx handles the SMTP layer so your team does not have to.

Support, inbound, jobs, and contact addresses can route wherever your workflow already lives.
Authentication checks and message timelines stay available when you need to debug delivery or abuse issues.
What they usually need

Common requirements. Edge cases are where the pain starts.

JoltMx fits when you need routing, verified destinations, and enough message visibility to debug delivery issues.

01

Keep dormant domains reachable

Parked and low-volume domains still receive important mail. JoltMx gives them a forwarding path without provisioning mailboxes.

02

Route role addresses cleanly

Forward `hello@`, `support@`, or catch-all traffic to verified destinations.

03

Manage client domains without owning mailbox support

Keep client-facing addresses working without running a separate mailbox product per customer.

04

See what happened when delivery gets weird

The message timeline shows where a message was accepted, filtered, routed, and forwarded.

A good fit if

Email routing without infrastructure ownership.

  • You need inbound mail on your domains, but most messages should end up in inboxes or systems you already use.
  • You care about aliases, catch-all rules, sender controls, and verified forwarding destinations more than mailbox hosting features.
  • You want to inspect authentication results and delivery history when something looks wrong.
  • You need something sane for project domains, client domains, or operational addresses without building your own mail handling stack.
Probably not a fit if

You actually need full mailbox hosting, calendars, and collaboration tools.

  • You want each user to have a dedicated hosted mailbox with the normal office-suite extras.
  • You need outbound campaign tooling, newsletter management, or full transactional email sending as the primary product.
  • You are looking for a general-purpose collaboration suite rather than a focused inbound routing layer.
  • You are happy to run and support your own mail server estate and do not need a managed forwarding layer.
Free during beta

Start routing mail in minutes.

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

Get started for free Talk to us

No credit card required  ·  Free tier stays free