Jan 24

Kinto

“Kinto was started by Mozilla and is an open-source alternative to Parse by Facebook and Firebase by Google. More specifically Kinto is a generic JSON document store with sharing and synchronisation capabilities. They chose to serve out of Netlify because of the simplicity, performance and feature set that includes TLS. Read on to find out why Kinto prioritized HTTPS and which external tools they use to build their site.”

Tools & Frameworks:

  • Github
  • Python
  • Pyramid
  • Pelican
  • Elm
  • Postgresql
  • OAuth2
  • Redis
  • Pusher
  • WebPush

Netlify Features used:

  • Continuous Delivery
  • Inbound webhooks
  • Git Integration
  • Domain Aliases
  • Web UI
  • HTTPS
.
.

Kinto

“Kinto was started by Mozilla and is an open-source alternative to Parse by Facebook and Firebase by Google. More specifically Kinto is a generic JSON document store with sharing and synchronisation capabilities. They chose to serve out of Netlify because of the simplicity, performance and feature set that includes TLS. Read on to find out why Kinto prioritized HTTPS and which external tools they use to build their site.”

A few words with Rémy from Kinto...

Could you tell us a little bit about your project?
Netlify
Kinto is a Database for the web. Just build the UI with a local state then plug Kinto JS and sync your state between devices and users.
Rémy Hubscher
Why did you choose Netlify?
Netlify
Basically what happened is that we were using Github pages with a custom domain kinto-storage.org and we wanted to enable HTTPS. Github pages doesn’t supports yet SSL certificates with custom domains even though Let’s Encrypt has been standing there for a year now. HTTPS is important, even for static sites

SEO: A SEO bonus is given to sites with HTTPS support.
Analytics: You will only see inbound refereres from sites using HTTPS if your own site use HTTPS.
Control: Some WIFI providers will try to inject their ads into your site. HTTPS protects you and your users.
Performance: Modern browsers support HTTP 2.0, only for sites with HTTPS enabled. For some sites HTTP 2 can give significant performance improvements.

Hopefully Netlify supports SSL and HTTP/2.0 as well as the hability to plug Github repository pushes events to trigger a rebuild. What was important for us is that after each merged Pull-Request into the master branch of our kinto-website github repository, the website was rebuilt automatically and published on the domain name. Before we’d heard about Netlify the solution was to use a shared server and to add a script plugged onto a web hook that will rebuild the server version for each push to Github master then we would have to configure a SSL certificate using Let’s encrypt with a procedure for automatic updates every 3 months.”
Rémy Hubscher
What is your favorite thing about the Netlify Platform?
Netlify
Simplicity of setup. Using Netlify was fast, they already had the webhook and automatic setup with Github, also we don’t have the hassle of configuring and upgrading the SSL certificates. It tooks less than one hour to configure our DNS record and switch from Github pages to Netlify with HTTPS supports. Our only regrets is the bad mark that we have on the SSL observatory, but we hope that’s something Netlify can fix for us really soon. Really using Netlify was a blast, intuitive dashboard, nicely explained and exposed complex features.
Rémy Hubscher

All these sites are fast & secure. Join the club.