A Mailjet Alternative That Keeps The Record Of What You Sent

Any other route to getting your application mail delivered. That covers rival platforms such as Postmark, SendGrid and Amazon SES, and Mailgun, which sits under the same parent company as Mailjet does. It also covers managed services like this one, where somebody runs the sending for you rather than handing you an account and a link to the documentation.

Mailjet sells you a platform and a plan tier, and the platform is capable. We sell you the work that has to happen around a platform like it. The sending domain, the authentication records, the warmup schedule, the DMARC policy and the monthly delivery numbers are ours to get right and ours to explain when they slip. Nobody on your side logs into anything, and nobody on your side has to find out what happened to a single message.

Anything past your plan limit is billed per additional thousand emails, and unused credits expire at the end of the billing cycle rather than rolling forward. Email validations and previews are metered per plan. Removing the Mailjet logo starts at Essential. A dedicated IP is tied to plans of 100,000 and above, on request, and phone and chat support starts at fifty thousand. Each of those is priced reasonably for what it is. With us the work sits inside the one figure rather than beside it.

This is the row the page turns on. Mailjet lists activity logs among the things its Custom plan adds, and Custom has no published price, so the honest reading is that a full searchable history is a conversation rather than a checkbox. We keep your delivery history and answer questions against it as part of the service. When somebody says a receipt never arrived, the answer is a sentence from us rather than a hunt on your side.

In our view most senders under a few hundred thousand messages a month do not, because a dedicated IP without enough volume behind it warms slowly and can perform worse than a well run shared pool. Mailjet reaches a similar conclusion from the other direction and attaches dedicated IPs to plans of 100,000 and above, on request, so at ordinary transactional volume the question does not really arise. We make that call on your actual volume rather than on a plan tier.

Yes. The new sending path gets built and tested alongside the one you are running, and the application only switches once messages are landing. Your Mailjet account stays open until you are satisfied, and the free plan means keeping it costs nothing while you decide. Nothing is turned off before the replacement is demonstrably working.

Yes. Warming governs how fast volume climbs on the new domain, not whether mail goes out at all. Expect two to three weeks to reach full volume, and expect to be told where you are in that ramp rather than left to work it out.

Then this is a repair job rather than a setup job, and it runs longer. We audit what is actually published, correct the records, file delisting requests anywhere the domain has been flagged, and clear out the addresses driving the bounces. Where damage built up across years, expect several weeks before the numbers settle. Moving to better software does not fix this on its own, which is worth saying plainly.

It replaces it for application mail. We own that sending path end to end. If your marketing team is working in Mailjet’s editor and wants to stay there for campaigns, that is a reasonable arrangement and we have no argument with it. What goes away is the part where nobody owns whether the receipts land, or can say what became of one that did not.

Yes. Anything built in Mailjet gets rebuilt on the new path, MJML templates included, and every one is sent and read during setup rather than assumed to render. The ones that break are usually the oldest, the ones nobody has opened since the year they were written.

It comes across with you. Suppression data is worth real money in reputation terms, because a domain that starts fresh and mails addresses it already knew were dead spends the warmup it just paid for.

No, though they are the common case. Anything able to send down an authenticated path can be routed. Teams arriving from Mailjet have usually built the sending themselves against the API, and the work on our side is much the same either way.

Records go up within a day or two of getting DNS access, and templates are normally done inside that same week. Warming decides the real timeline, so the honest answer is two to three weeks.

Thirty days’ notice ends it and everything is portable. The DNS records sat on your own domain throughout, because they were always yours. Templates, suppression list and sending history come back in a standard format, and we will tell you what to point the application at next so the mail does not simply stop. If the honest answer is going back to Mailjet on a bigger plan, we will say so.

Sixty dollars a month with 25,000 delivered emails included, and the deliverability work sitting with us instead of with whoever on your side has a free hour that week.