Last week MailChimp announced that they are shutting down the Mandrill Heroku Add-on, giving users until April 27th to migrate to another solution. Many of our customers have sought guidance on how and where to migrate, so we have asked our email providers to create guides for migrating from the Mandrill add-on to their respective services.

Mailgun: Migrating from the Heroku Mandrill Add-on to the Mailgun Add-on

Postmark: Migrating your Mandrill Heroku Add-on to Postmark

SendGrid: Replacing the Mandrill Heroku Add-on with the SendGrid Add-on

SparkPost: Migrating from Mandrill to SparkPost on Heroku

Three months ago we announced that Parse would be opening their Cloud Code product so that their customers would be able to deploy their mobile backends to Heroku. This allowed Parse customers to use a full Node.js environment with Cloud Code. With Parse’s recent announcement, we’re taking that one step further, by allowing you to deploy your own Parse API server to Heroku.

What this means for developers is that you will now be able to run all of your Parse services on Heroku, taking advantage of Heroku’s scalable platform as well as Heroku features like Pipelines, Review Apps, and GitHub Sync. Beyond that, because the Parse Server is now open source, you will also be able to extend and...