Kinto is a minimalist JSON storage service with synchronisation and sharing abilities. It is meant to be easy to use and easy to self-host.

Kinto is used at Mozilla and released under the Apache v2 licence.

Why use Kinto?

We believe data belongs to the users, and not to the application authors. When writing applications, data should be made available to any device, connected or offline, and everything should be in sync.

Rather than spending a non-trivial amount of time and expertise on implementing all that (and then maintaining it!), you could use Kinto, that does all that for you:

  • Expose your data over an HTTP interface, unlike databases like PostgreSQL
  • Use simple HTTP requests rather than SQL
  • Use Kinto.js to easily implement offline first clients
  • Choose the database you want from those that Kinto supports, and use a unified API to access its data
  • Manage your data using the handy admin UI
  • Easily set up live push notifications for live updates of your application
  • Make it possible to share data between users (using fine-grained permissions)
  • Take advantage of schema validation if you need it
  • Track changes on your application data

Use cases

  • A generic Web database for frontend applications.
  • Build collaborative applications with fine-grained permissions.
  • Store encrypted data at a location you control.
  • Synchronise application data between different devices.


At Mozilla, Kinto is used in Firefox for global synchronization of frequently changed settings like blocklists, and the Web Extensions storage.sync API; as well as in Firefox for Android for A/B testing and delivering extra assets like fonts or hyphenation dictionnaries.

Key features

https://thenounproject.com/search/?q=syncing&i=31170 Synchronisation https://thenounproject.com/search/?q=permissions&i=23303 Fined grained permissions
https://thenounproject.com/search/?q=quality+control&i=170795 JSON Schema validation https://thenounproject.com/search/?q=community&i=189189 Universal and multi clients
https://thenounproject.com/search/?q=free&i=669 Open Source and Self-hostable https://thenounproject.com/search/?q=community&i=189189 Designed in the open



JavaScript HTTP API client Python HTTP API client
https://thenounproject.com/search/?q=offline&i=90580 Offline-first JavaScript client control panel by Gregor Črešnar from the Noun Project Web Admin UI
restore by Francesco Terzini from the Noun Project History of changes and authorship https://thenounproject.com/search/?q=refresh&i=110628 Live Push notifications
https://thenounproject.com/search/?q=attachment&i=169265 File attachments on records approved by Gregor Črešnar from the Noun Project Digital signature and workflows
https://commons.wikimedia.org/wiki/File:React.js_logo.svg Kinto+React boilerplate https://thenounproject.com/search/?q=tutorial&i=24313 Example applications

Coming soon

(See our roadmap)


Bi-directional synchronisation of records is a very hard topic.

Kinto takes some shortcuts by only providing the basics for concurrency control and polling for changes, and not trying to resolve conflicts automatically.

Basically, each object has a revision number which is guaranteed to be incremented after each modification. Unless the history plugin is activated, Kinto does not keep old revisions of objects.

Clients can retrieve the list of changes that occurred on a collection of records since a specified revision. Kinto can also use it to avoid accidental updates of objects.



Kinto synchronisation was designed and built by the Mozilla Firefox Sync team.


Kinto can execute some code when a particular event occurs. For example, when a record is created or updated in a particular collection.

It can send a notification to clients using WebSockets or fill a queue of messages in Redis or execute any custom code of your choice, like for sending emails or pinging a third-party.

See our tutorials for more in-depth information on these topics.