When comparing Kinto vs Loopback, the Slant community recommends Loopback for most people. In the question“What are the best open source Parse alternatives?” Loopback is ranked 6th while Kinto is ranked 8th. The most important reason people chose Loopback is:
Easily and quickly get going.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Open Source
Kinto is released under Apache v2, which is one of the most flexible licenses.
Pro Good for sensitive data
Since Kinto is a self-hosted solution, it can be used to store sensitive data (emails, financial data etc...) safely, since only the developer has access to the backend.
Pro Fined-grained permissions
Allows to share individual or collection of records for read or write operations.
Pro Push notification support
Pro File attachments on records
Using the kinto-attachment plugin, the server can attach files to records (hosted by server or Amazon S3)
Pro Backed by Mozilla
Mozilla uses it in production to synchronize security settings for Firefox. This means that the product should have adequate support for an extended period of time due to Mozillas use of it.
Pro Easy to get a project up and running
Easily and quickly get going.
Cons
Con No hosted version
In order to use kinto you have to download it and host it on your own server infrastructure. While it does help you avoid outsourcing your data to a third-party, it also adds the overhead of having to maintain a backend for your app.
Con Not as usable as Parse
Parse had several SDKs available which made it a breeze to integrate it with any platform that you wanted.
Con Strong-PM process manager
It's not required to run a loopback app and can be a pain to deal with.