wouldit.work

Developer tools

Parse: Facebook acquired it, then shut the hosted service down

Parse was a mobile backend-as-a-service that Facebook acquired in 2013. In January 2016 it announced a one-year wind-down, open-sourced Parse Server, and retired the hosted service on January 28, 2017.

Product
Parse
Founder
Ilya Sukhar and Kevin Lacker
Launched
n/a
Model
Freemium hosted backend, later open-source self-hosting

Published · 3 min read · 3 sources

Key takeaways

  • Facebook acquired Parse, a mobile backend-as-a-service, on April 25, 2013; TechCrunch reported the deal was worth $85 million, which neither company confirmed.
  • On January 28, 2016 Parse said it would wind down the hosted service and retire it on January 28, 2017.
  • The company released a MongoDB migration tool and open-sourced Parse Server so apps could keep running without the hosted platform.

What it is

Parse was a mobile backend-as-a-service: cloud data storage, identity, push notifications, and custom server code, so app developers did not have to run their own backend (TechCrunch). It was founded by a small group that included CEO Ilya Sukhar and co-founder Kevin Lacker, and was often compared to "the Heroku of mobile" (TechCrunch, TechCrunch).

Timeline

  • Around 2011: TechCrunch's 2013 acquisition story said Parse "was founded about two years ago" by former Googlers and Y Combinator alumni (TechCrunch).
  • April 25, 2013: Facebook acquired Parse as "its first paid B2B service." TechCrunch wrote that it had "heard" the deal was worth $85 million (and later that this excluded retention); "neither company is commenting on the size of the deal, except that Facebook said it's not 'material.'" Parse had raised $7 million. Sukhar said he chose Facebook over other suitors as a better cultural fit. The hosted product used a freemium model, with a free tier of up to 1 million requests or pushes a month.
  • January 28, 2016: Lacker announced that Parse was "winding down the Parse service, and Parse will be fully retired after a year-long period ending on January 28, 2017." Facebook would release a database migration tool for MongoDB and "the open source Parse Server," so apps could keep using most of the API on their own Node.js servers (TechCrunch). TechCrunch wrote that this would affect "the devs behind the 600,000 apps built on the platform."
  • January 28, 2017: The hosted service was scheduled to go away, a year after the announcement (TechCrunch).

Why it worked

  • It sold time. Mobile teams could ship data, login, and push without becoming infrastructure companies (TechCrunch).
  • A free tier pulled in developers. The 1 million request-or-push allowance made it easy to start, then pay if an app grew.
  • The shutdown, at least, left an exit ramp. A year of hosted operation, a migration tool, and an open-source server was more than many acquired developer tools have offered (TechCrunch).

What to learn

  1. If your infrastructure is a feature of a much larger company, assume it can be deprioritized. TechCrunch noted that Amazon, Google, and Microsoft already offered similar tools by 2016, and that Facebook "probably looked at it and decided it wasn't worth its effort anymore" (TechCrunch).
  2. Prefer backends you can export or self-host. Parse Server existed because the official API was being turned off (TechCrunch).
  3. A one-year sunset is still a painful rewrite for a production app, even when it is "responsible" by platform standards (TechCrunch).
  4. Acquisition culture fit is not the same as long-term product commitment. Sukhar picked Facebook for excitement and fit in 2013; the hosted service was gone four years later (TechCrunch, TechCrunch).

Risks and what didn't work

  • The $85 million price was reported, not confirmed. TechCrunch said it had heard that figure and that neither company would comment beyond Facebook calling the deal not "material."
  • The 600,000 apps figure is from TechCrunch's 2016 report and is not independently verified here.
  • Self-hosting was a different product. As TechCrunch noted, people used Parse specifically to avoid running servers; Parse Server pushed that work back onto them (TechCrunch).
  • Platform trust. Developers who had built on Parse had to spend a year migrating, which is the usual warning about betting a product on someone else's core-adjacent service (TechCrunch).

FAQ

Short answers drawn from the sections above.

What is Parse?

Parse was a mobile backend-as-a-service: cloud data storage, identity, push notifications, and custom server code, so app developers did not have to run their own backend (TechCrunch). It was founded by a small group that included CEO Ilya Sukhar and co-founder Kevin Lacker, and was often compared to "the Heroku of mobile" (TechCrunch, TechCrunch).

Why did Parse work?

  • It sold time. Mobile teams could ship data, login, and push without becoming infrastructure companies (TechCrunch).
  • A free tier pulled in developers. The 1 million request-or-push allowance made it easy to start, then pay if an app grew.
  • The shutdown, at least, left an exit ramp. A year of hosted operation, a migration tool, and an open-source server was more than many acquired developer tools have offered (TechCrunch).

What can indie builders learn from Parse?

  1. If your infrastructure is a feature of a much larger company, assume it can be deprioritized. TechCrunch noted that Amazon, Google, and Microsoft already offered similar tools by 2016, and that Facebook "probably looked at it and decided it wasn't worth its effort anymore" (TechCrunch).
  2. Prefer backends you can export or self-host. Parse Server existed because the official API was being turned off (TechCrunch).
  3. A one-year sunset is still a painful rewrite for a production app, even when it is "responsible" by platform standards (TechCrunch).
  4. Acquisition culture fit is not the same as long-term product commitment. Sukhar picked Facebook for excitement and fit in 2013; the hosted service was gone four years later (TechCrunch, TechCrunch).

What didn't work for Parse, and what are the risks?

  • The $85 million price was reported, not confirmed. TechCrunch said it had heard that figure and that neither company would comment beyond Facebook calling the deal not "material."
  • The 600,000 apps figure is from TechCrunch's 2016 report and is not independently verified here.
  • Self-hosting was a different product. As TechCrunch noted, people used Parse specifically to avoid running servers; Parse Server pushed that work back onto them (TechCrunch).
  • Platform trust. Developers who had built on Parse had to spend a year migrating, which is the usual warning about betting a product on someone else's core-adjacent service (TechCrunch).

Sources

Every link cited above, in order of first use.

  1. 1.Parse (parseplatform.org)
  2. 2.TechCrunch (techcrunch.com)
  3. 3.TechCrunch (techcrunch.com)

Related case studies

More in Developer tools →