Mailgun (YC W11) is being acquired by Rackspace
blog.mailgun.net
blog.mailgun.net
I really hope my beloved mailgun remains competitive and independently available and doesn't get assimilated like slicehost -- mailgun is a not-so-well kept secret that needs to stay as is.
I had a play with Mailgun a while back (and others, Mailgun felt nicest to me) but there was a feature that seemed to be missing from them all.
How do you handle rules between outgoing emails?
For example, say there's an email that gets sent out on a user action, but you only want to send it out once a day. It feels to me like I should be able to set rules within Mailgun to say, only send out this email every x minutes, or, don't allow it to go out if another type of email has gone out before etc.
Is there a way of dealing with that? At the moment we have to put all those rules into our app, and it seems like something the app shouldn't have to deal with.
Take for example the A/B testing of pricing. I'd like to offer some customers an infinite free trial while others only get a month free after which time they have to upgrade. The email flow for each of these types of customers would be quite different over the first couple of months. Different actions would trigger different emails at different times. That logic is not really something you want deep in your app (as I say, that's more marketing logic than app logic).
Looking through the other links provided in the sibling posts I'm starting to think the right way of doing this is using an event tracking system (Mixpanel type idea, but maybe storing that information internally). Then you have a rules engine outside of the app to send out the emails. It then becomes trivial to segment as in my a/b testing example, or to not send out more than one of a certain type of email a day etc.
Thanks for all the thoughts on it though - it's helped to push me in the right direction.
One main reason the application is the best place to manage these rules is that it's rarely just the email content that dictates the engagement pipeline. Whether a user has interacted with a component, or logged in, etc, are all app-side variables which may affect whether or not you wish to send a given email.
That said, one method some of our customers use at PostageApp to simplify some of the logic is to pass a UID to the API based on the unique parameter sets - e.g. recipient + template + hour - and rely on the engine to discard the duplicate API calls.
IronWorker (our product from Iron.io) has scheduling capabilities and can be combined easily with SendGrid/Mailgun to provide any type of rules engine.
In it's most simple form, you can use it like cron in the cloud.
My guess is they'll integrate both products after which Mailgun and SendGrid will become largely equivalent services.
Congrats to Ev, Taylor, and the rest of the team!
Edit: The link appears to be fixed now.
This is not such a great news for customers. Sorry.
[From Dow Jones, from their interview with Pat Matthews, SVP of Corporate Development (my boss)], "Mr. Matthews said the acquisition is not an "acqui-hire" (a deal in which a start-up is acquired purely for its talent), and that Mailgun's team will continue to work in San Francisco, where Rackspace has an office. However, they will report initially to corporate development and remain autonomous for awhile so they're not integrated too quickly into Rackspace, a mistake that Rackspace has made in the past, he said."
Gold.
CloudKick and Anso Labs seem to have fallen off the map as well. I'd be curious to hear what former Jungle Disk users felt changed with the acquisition.
That doesn't mean Rackspace is going to join the club of companies killing great startups but the last few times I saw acquisitions, things were not very sweet.
Hope mailgun will do even better under Racksapce. I wish them all the best.
Not to be rude or anything, congrats! But from the website itself it sounds like "woohoo, we can send email". Atleast the features page lists 99% standard-mail features like "can send mail, can do SPF, can do DKIM, can filter mails"..
I guess that's not why they were aquired, so what is the real value of the company?
That feature alone made us switch from SendGrid, and the more reasonable price point for our stage just sweetened the pot.
Anyhow, i have been downvoted for a serious question. Sorry i did upset people with a question....
But I go disagree about the marketing copy. It says on the front page "Email for developers. Mailgun is a set of powerful APIs that allow you to send, receive, track and store email effortlessly." To me this conveys exactly the information I need about the service. I'm just disappointed they didn't play with the railgun analogy more, but still there is a reasonably cute mail gun gadget ;)
There is a lot of information on mailgun, both on HN and on the web. They've made no secret of the problem space they were going after.
So Rackspace felt like they were worth acquiring, the product and customers are supported so its not a strict acquihire exit, and while the questions about sendgrid are good here (which are proxies for "What is Rackspace's strategy as a services provider really?") there clearly was enough to Mailgun to make this worthwhile. That you don't "get it" is ok but instead of the snarky "Soo they just send email?" kind of thing why not dig into their product and ask specifically about it? If it seems un-remarkable then talking about how you implement the same features and qualifying the scale of that would be helpful too.
Deliverability is a huge important issue for most people, if I send an email and it doesn't arrive then I'm in a bad spot. I used a similar service to Mailgun (http://postmarkapp.com) and the amount I paid per month (when I was sending emails) meant if I spent more than 1 hour of my time configuring and managing a mail server every month I would be losing money.
This is an especially big issue for people that are using virtual servers or not that great server providers, ones that recycle IPs, if I'm correct in my understanding of mail deliverability, if an IP has sent spam before it's almost guaranteed to be blocked by most spam protection companies, that sort of thing isn't good.
If you're just sending in bulk, go with SendGrid, but if you want to do anything mildly interesting with email-as-an-interface, Mailgun cannot be beat. I'm honestly surprised it has taken other mail providers to offer these same features.
They have webhooks built in that can call your application when mail is delivered, bounced, opened, clicked, etc. That's huge for me. I allow my clients to send out emails to their users — now I can use that information to show my clients who has opened which emails ... I can also alert users if their email has become blocked or had a bounced email.
They give you a ton of functionality out of the box that would take a lot of time and effort to recreate on your own.
I don't want to focus on figuring out email - I just want to send them and have them get to the users that want them.
I use MailGun for email for the same reason that I use FreshBooks for invoicing my clients — because I want to spend my time building my business rather than focusing on solving a problem that someone else has already done a great job of solving.