Thanks for the article Thomas. I also implemented Stripe in a Rails project recently using the official gem and it was a breeze 👌
I'm curious, what do you think about using Supabase + Stripe instead of Aista? And how about Strapi + Stripe plug-in? I was looking at your product and I find it to be a more enterprise level CMS, CRUD generator and integrator of sorts 🤔
Thank you Max. It depends upon what you're creating. If you're happy with GraphQL and Postgrest, go for SupaBase by all means, if you need more, such as business logic in your backend (to avoid scattering business logic in your frontend - Sigh!) then SupaBase (and others such as Hasura) can't help you much.
I suspect it's about your requirement for "horizontally integrated solutions" that would be the trigger here in the end. As to your observation about Magic being more enterprise level, I'd have to agree upon that ... ;)
Thanks for the article Thomas. I also implemented Stripe in a Rails project recently using the official gem and it was a breeze 👌
I'm curious, what do you think about using Supabase + Stripe instead of Aista? And how about Strapi + Stripe plug-in? I was looking at your product and I find it to be a more enterprise level CMS, CRUD generator and integrator of sorts 🤔
Thanks for the answer, Thomas. I think I understand the charm of Aista a bit better now 🙂
Thank you Max. It depends upon what you're creating. If you're happy with GraphQL and Postgrest, go for SupaBase by all means, if you need more, such as business logic in your backend (to avoid scattering business logic in your frontend - Sigh!) then SupaBase (and others such as Hasura) can't help you much.
I suspect it's about your requirement for "horizontally integrated solutions" that would be the trigger here in the end. As to your observation about Magic being more enterprise level, I'd have to agree upon that ... ;)
Psst ... ^_^