Building the back end of your product requires a lot of effort. However, BaaS and headless CMS will ease that for you: Amplication, Subapase, and Appwrite.

Saurav Jain

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

This post compares headless content management systems and Back-end-as-a-Service (BaaS), highlighting their differences, focus, customization options, and cost. It also provides an overview of three open-source BaaS solutions: Amplication, Appwrite, and Supabase.

Amplication vs Supabase vs Appwrite, free BaaS comparison

What is a headless content management system (headless CMS)?

What are the differences between headless CMS and BaaS?

What are some open-source BaaS solutions?

Hung Vu has done an amazing job comparing diff BaaS providers, you can read and see which one is best for you :)

This was really informative. A great write up of the three.
I’ve shared it to the new NoSQL Database squad on daily dev <a href="https://app.daily.dev/squads/nosqldatabases/KPQLmxO0KKeYCxoHc57wKEBProegXCD89OLQ1mV68Kw" target="_blank" rel="noopener nofollow">https://app.daily.dev/squads/nosqldatabases/KPQLmxO0KKeYCxoHc57wKEBProegXCD89OLQ1mV68Kw</a>

I believe that Firebase can also be considered a Backend-as-a-Service (BaaS) option, just like Supabase. Although Supabase is my personal favorite, Firebase offers a straightforward and simple implementation process that many developers find appealing.