At this point, Parse is open source, too. Why an open source clone if you can have the original?
Parse is now open source in the sense of "here's a bunch of code we're throwing over the wall on our way out". Presumably (after the 1-year deadline) it's not going to be maintained or further developed by the original Parse team, who are now working for Facebook and will likely be reassigned to other roles.
Who is going to maintain the Parse source after that? A bunch of people that were using Parse specifically because they did not want to write their own backends to begin with?
EDIT: Hi folks, I was obviously talking about Parse, not Kinto. Kinto seems to have more features than Parse Server for now ! Looks like an awesome replacement.
What do you mean by "cloud code"?
Anyway yeah, we're expecting help from the community to bring what's missing :)
For cloud code, it's not true that parse-server doesn't support it - you can write cloud code directly in the node server.
For a full rundown on what's compatible, check out the migration guide: https://parse.com/docs/server/guide#migrating
The core functionality is there, and I highly recommend trying out the official Parse open source solution first, as it will be the easiest for most apps that want to migrate.
I may be way off base here, but there is no indication that this open source release from Parse is in any way a derivative of their commercial product... at this point whichever reimplementation of the Parse API gains the most developer mind share will survive as the winner. (Of course, Parse the company has a lot of inertia behind their own.)
It's not entirely satisfying, but that just proves we could integrate with many hosting platforms.
https://github.com/GoogleCloudPlatform/python-docs-samples/p...
If there's interest I'll try to flesh it out more.