We have a difficult announcement to make. Beginning today, we’re winding down the Parse service, and Parse will be fully retired after a year-long period ending Jan. 28, 2017. We’re proud that we’ve been able to help so many of you build great mobile apps, but we need to focus our resources elsewhere.
We understand that this won’t be an easy transition, and we’re working hard to make this process as easy as possible. We are committed to maintaining the back-end service during the sunset period, and we are providing several tools to help migrate applications to other services.
First, we’re releasing a database migration tool that lets you migrate data from your Parse app to any MongoDB database. During this migration, the Parse application-programming interface will continue to operate as usual based on your new database, so this can happen without downtime. Second, we’re releasing the open source Parse Server, which lets you run most of the Parse API from your own Node.js server. Once you have your data in your own database, Parse Server lets you keep your application running without major changes in the client-side code. For more details, check out our migration guide here.
We know that many of you have come to rely on Parse, and we are striving to make this transition as straightforward as possible. We enjoyed working with each of you, and we have deep admiration for the things you’ve built. Thank you for using Parse.
Moving forward, we want to dedicate more resources to high-impact products and services in areas like analytics, monetization, discovery and authentication. As a result, we’ve made the difficult decision to wind down support for Parse. We’re proud of what we’ve accomplished together with the Parse community, and we thank them for their support.
Readers: Are you as surprised as we were?