[eikaramba]

IMHO these are the 3 open source backend/platform -as-a-service solutions you need to have a eye one:

1) Directus (in my view the best offering of features)

2) Supabase (if you want more performance. the admin ui however can only be used for internal access)

3) Appwrite (works good and has its own advantages. however in my case i would rather go with 1&2)

-Strapi is out since v4 (too many really big showstopers. i was a fanboy since v3 but directus just brings more to the table and is way mature)

-feathers.js (more lightweight, but unfortunately lost its momentum. better alternatives are nowadays available)

[codegeek]

I am a bit confused. How is Strapi (a headless CMS) comparable to Firebase/Supabase/Appwrite ? Aren't they apples and oranges ?

[resoluteteeth]

All these platforms expose a kind of data repository with multiple users that is designed to be used as an app backend. The permissions in a "headless CMS" will by default be designed under the assumption that people will be writing articles that will all be shared between/accessible to all users whereas Firebase/Supabase/Appwrite will assume that each user has their own private data, but a lot of the details are in how you configure them for your use case and perhaps they aren't really that different when you think about it.

[manigandham]

Fundamentally they're all relational db + data management UI + (automatic) API endpoints.

[christyjacob4]

yeap exactly... CMS's are meant for a different audience altogether

[aaaaaaaaata]

Depends what kind of app you're building, really.

[jpcapdevila]

I'm developing an alternative using SQLite, focused on JavaScript developers productivity.

https://javascriptdb.com

[christyjacob4]

Isn't Directus a CMS? Doesn't seem to be a backend/platform -as-a-service

[rglover]

Check out Joystick. It's full-stack JS, lightweight, and has a soft learning curve: https://github.com/cheatcode/joystick.