Mailgun is a transactional email API service which was owned and supported by Rackspace (acquired in 2012) and then spun off in 2017 as an independent and standalone entity. It is now supported by Sinch since that company's acquisition of Mailgun and Mailjet, through acquiring Pathwire.
$35
per month
Twilio
Score 7.0 out of 10
N/A
Twilio offers a CPaaS and CCaaS solution, with the combination of its programmable Voice, Video, and Messaging APIs, as well as the Twilio Flex cloud contact center. Additional capabilities include Twilio's Elastic SIP Trunking, as well as API for WhatsApp.
$0
per min per participant
Pricing
Sinch Mailgun
Twilio
Editions & Modules
Foundation
$35
per month
Growth
$80
per month
Scale
$90
per month
Flex
Free
Programmable Video
$0.0015
per min per participant
WhatsApp Business API
$0.0042
Per WhatsApp Template message sent
WhatsApp Business API
$0.005
Per WhatsApp session message
Elastic SIP Trunking
$0.007
Per min for termination
Programmable Messaging
$0.0075
per message sent or received
Programmable Voice
$0.0085
per minute to receive a call
Programmable Voice
$0.013
per min to make a call
Elastic SIP Trunking
$0.045
Per min for origination
Twilio Conversations
$0.05
per active user per month
Twilio Authy
$0.09
per authentication
Programmable Wireless
$0.1
per MB
Twilio Flex (Contact Center)
$1
per active user hour (5000 hours free)
Programmable Wireless
$2.00
per SIM card
Twilio SendGrid Email API
$14.95
per month up to 100k emails. (Up to 40k emails free for 30 days)
Twilio SendGrid Marketing Campaigns
$15
per month for 5,000 contacts and 15,000 emails. Your first 2,000 contacts are free
Twilio Flex (Contact Center)
$150
per named user per month (5000 hours free)
Offerings
Pricing Offerings
Sinch Mailgun
Twilio
Free Trial
Yes
Yes
Free/Freemium Version
Yes
Yes
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
Optional
Additional Details
—
1. Pay-as-you-go pricing: Simple usage-based pricing means you don’t get locked into big contracts.
2. Volume discounts: Discounts trigger as your usage grows, so you always get a fair price.
3. Start building today with free trial credit and full API access.
We chose Mailgun over sendgrid and Postmark because we really like their API. We have stuck with them because they have never given us any reason to switch. Their reliability is superb and their API remains excellent. sendgrid and Postmark are both good in their own rites, …
All three solution we evaluated are compatible and integrated in Google Cloud Platform (the cloud solution we use). We went for Sinch Mailgun since we already used Sinch to handle SMSs, and they are from the same Company.
To be honest, the tools are quite similar and again I dont recommend using them as a standalone products, but they power the work we do via CRMs and our marketing campaigns. Mailgun integrates slightly better which it is why it is the preferred choice for our agency, as it …
Those solutions are just not the same, Mailgun is a programmable SMS API with really low cost and is so far compared with Twilio SendGrid but since we are using more Twilio SMS or Whatsapp, [it's not used for] the same purpose. As OneSignal is an all in one solution for being …
Mailgun's pay-as-you-go pricing structure is fantastic, especially if you don't need to send that much email. The pricing, including the free tier, is much more generous than what you can get with some pricier providers, like SendGrid. I mainly just use Mailgun as an SMTP server for web services, and the service has been set-up-and-forget, which is great because I never even have to log onto the Mailgun website and do any work. Mailing list support also looks great for rolling-your-own and not relying on more expensive mailing list services.
I found Twilio to be excellent and very easy to use for a programmer in all aspects related to voice, SMS, and other features utilizing their API. I found the node client to be excellent and helpful. We previously used the Apex client for Salesforce before it was discontinued. Although we try not to use Twilio from Apex anymore, using that client was easier than implementing our own.
No built-in templating features (This was a bit sad after coming from Mandrill which excelled at this)
Dashboard UI (although easy to use) is a bit dated in appearance
Logs are cumbersome compared to Mandrill
Setting up TLD (top level domain) names (things like .online or .church) that are not common require an email to tech support (this is annoying)
Sometimes can be slow in delivery
Shared IP addresses can be SPAM filtered or delayed (requires an email to support to have a new one assigned - Note: this can be mitigated by buying a dedicated one for a monthly fee)
Segment’s email identifier is case-sensitive, which is ridiculous because emails themselves are not case-sensitive. This means that if I send a capitalized email address in an identify call, it will create a duplicate user rather than matching it with the lowercase email. I think this is a technical oversight that should be corrected.
I’d like to see more information about the eventual transition of existing Frontline customers to Twilio Flex
I’d like to see some integrations between Twilio Studio and OpenAI or another open source LLM to provide automated responses, if this hasn’t been done already
I would like to be able to drag and move the actual lines connecting the steps in Twilio Studio, sometimes mine can get pretty messy
I think a Bug Report form would be beneficial for developers
Unless we can get this handled quickly -- less than 1 week -- we will likely switch to another provider who, in my opinion, we'll have to spend close to $3,000 in development time to build a new integration for texting. Our clients need texting and I feel Twilio has failed us miserably.
The time for the initial setup is very quick, since you can start sending (thus developing) from their sandbox in no time. The actual configuration involves, as usual, some DNS changes that may require time but are well explained and documented. Once everything is set up, there are a lot of monitoring tools that you can use to optimize your lists.
Twilio has well documented APIs and examples. There are several tutorials, videos and Q&As regarding their services. So, usability is very good. I must say that advanced knowledge of telephony, API/Programming and error-handling is essential to make good use of Twilio. It's not just plug-and-play unless you are integrated with a system that has all of the programming built for it.
There have been a few minor outages through the years, but nothing more than a few minutes. These small outages are to be expected in any kind of a SaaS product, but Mailgun handles them very well. We designed our software to just retry sending after a while if there is an outage. As far as I know, we have never had to do more than a few retry cycles. This is all automated on our end, so we rarely even notice. Our customers have never noticed any mail sending outages.
The API and the deliverability of emails is excellent. Their API is very responsive and performs perfectly fine. I have no complaints there. Their management interface though (accessed through the web) is pretty slow though. Searching through lists of emails when I'm tracking down a problem for a customer can take 10+ seconds which is annoyingly high for a modern web app.
Twilio executes what it is designed to do: send SMS messages at scale while providing very good deliverability. I believe that Twilio is very good at what we use for adding SMS messages to our comms strategy. We can see those messages get opened and replied to, which is exactly what we are looking to achieve.
You can't seem to get ANY support until you shell out hundreds of dollars per month. I even did this when we could not deliver mail with Mailgun, and the response was slow and inadequate. Nor would they refund my money. I'll never be a customer of Mailgun again.
I have not had to communicate with Twilio support in the last 3 years but my past experience with them has been very positive. They replied to my previous requests promptly and kept me well informed to resolve my inquiries. With their documentation that's available, I hardly imagine why anyone would need to contact support since it's all there in a concise and easy to understand format. It would probably take you longer to type out a support ticket than to just open their doc websites.
To be honest, the tools are quite similar and again I dont recommend using them as a standalone products, but they power the work we do via CRMs and our marketing campaigns. Mailgun integrates slightly better which it is why it is the preferred choice for our agency, as it integrations options seem to be better
We evaluated many fundraising-based text-to-give programs and found the subscriptions prohibitively expensive for our small scale and uncertain first few years of development. While we may be willing to invest that kind of money after discovering how things work, we're happy with Twilio now and have no desire to start over.
Over the past six years, Mailgun has scaled with our growth very easily. We haven't had to make any code changes to handle our larger volume today, and their pricing has scaled naturally with our growth. As far as I know, there is nothing we will need to do in order to grow 10-fold. Mailgun just handles the load really well.
By not investing in our mail server, we have saved huge amount of money and time. For configuration and installation of an email server on Linux-based server, we would have to hire a network administrator.
If email delivery is an issue in a hosting provider, another solution is to switch the hosting. Fortunately with Mailgun, we didn't need to try different hosts and experiment which one works best for emails. We can stick to our existing web hosting provider and would not need to change it just for the sake of improving email deliverability.
The pricing of Mailgun is very cheap and straightforward. First 10K emails are free every month and that's a big advantage for our organization because our volume of emails is rarely more than 10K per month.
