Auth Overview

MakerKit uses Firebase to manage authentication within your application.

By default, every kit comes with the following built-in authentication methods:

  • Email/Password - we added, by default, the traditional way of signing in
  • Social - we also added by default both Google and Facebook sign-in methods

You're free to add (or remove) ant of the methods supported by Firebase's Authentication: we will see how.

This documentation will help you with:

  • Setup - setting up your Firebase project
  • SSR - using SSR to persist your users' authentication, adding new providers
  • Customization - an overview of how MakerKit works so that you can adapt it to your own application's needs


We set up MakerKit to persist the user's session on all the website's pages using SSR.

SSR allows for seamless integration between the pages of your website. For example, your pricing page could prompt your users to upgrade to the new plan rather than what it shows to non-subscribers of your service.

Many websites use persistent sessions in different ways:

  • personalized content
  • pre-filled forms
  • and a lot more

While it sounds great, there is a downside: by server-side rendering the page (SSR), we lose the possibility to statically generate the page (SSG), which is faster.

Should you use SSR or SSG?

Ultimately, it comes down to what your needs and preferences are.

MakerKit does not use SSR by default but adding it is very simple.