# Why MakerKit - A Firebase SaaS Boilerplate for Next.js

> Learn why we built MakerKit - a complete boilerplate for building SaaS applications in no time built with Firebase, Next.js and Tailwind CSS

*Published: 2021-01-12*
*Canonical: https://makerkit.dev/blog/diary/why-makerkit-firebase-nextjs-saas-boilerplate*

---

As a *maker*, I often think about building new projects. Some for
fun, some for profit. As you're reading this post, I'm sure it's easy to relate to this feeling.

Sometimes, I used to think: despite having to code a ton of code in my career,
it never really compounded to anything.

If I did function after function, I'd have a complete codebase.
And by extension, if I had a codebase ready to deploy in a matter of
minutes, **I'd have superpowers**.

## Code is a superpower

Having super-powers: there is no other way to explain the feeling of being
able to deploy a product, with the potential of getting paid, in such a short amount of time.

I built MakerKit with the intention of being able to provide the following
out of the box:

- A landing page seamlessly integrated with the app
- An app that lets users authenticate and pay for the app's value proposition

Of course, MakerKit won't be able to provide you with your value proposition,
but **it can make it plenty easier to get it done**.

Ever dreamt of making a startup in 48 hours? Well, MakerKit can get you from
0 to 0.5 in under half an hour (considering creating a Firebase project and
setting it up).

Can you develop your value proposition's MVP in 47 hours of work? Congratulations! You have a startup.

## Let go of overthinking

I'm not a particularly fast maker: I tend to overthink. Is that button's
color correct? Is that how the menu should look? I'm a developer,
after all.

Overthinking is our favorite sport.

By starting with something that **looks good by default**, I'm able to skip
the overthinking part and get straight to business, focusing on shipping.

## What can you expect from this Saas Starter?

I built MakerKit with two principles:

- the code should be good enough to use as an example for
the code you will be building on top. At the same time, it should not be too
clever: figuring out the whys and hows should not be your concern when
shipping a product

- the starter should be a **solid foundation**, but without making too many
assumptions. Every product will be different and with its own peculiarities.
It's hard for a SaaS to provide an experience that suits most
applications, which is why the data model is light by default

What MakerKit voluntarily leaves out is:

- clever performance improvements: the application is simple, and I prefer
you to see simple code rather than something milliseconds faster

- complex data model: your data model will change heavily as you develop
your application, and if MakerKit stood in your way, it would be a huge
failure for us

For a complete list of the technical details (e.g. the libraries it is built on
top of), please check out the {% a href="/docs/technical-details" %}
Technical
Details
{% /a %} in the documentation.

## Will MakerKit release new kits?

Yes, most likely! These will come in the future, but it's in the plans, and
we look forward to shipping them.