1. Their stacks are mostly open source, so you can truly self host with no cost at all if and when you need to.
2. They're building on top of Postgres so you get the full power of a SQL database. Plus they both have realtime solutions ready to go.
1. Their stacks are mostly open source, so you can truly self host with no cost at all if and when you need to.
2. They're building on top of Postgres so you get the full power of a SQL database. Plus they both have realtime solutions ready to go.
My goal with StaticBackend is to go more in dept in features like sending emails, Stripe payments. Features that a SaaS / web app typically need in the backend.
I'll not stop at Database and WebSocket. I'd like to go further based on demand. I'm building more a backend teamate for frontend developers.
I recognize that my choice of using a Document database instead of an RDBMS can be argued. But one as to make choices.
Thanks for your comment.
As an example, look at low-code for inspiration to determine what features people need which aren't being filled by existing solutions. Hopefully that reduces the need to compete via feature checklist.