Validate new CMS
In my research for an idea to build I came across Strapi " https://strapi.io/ " which is basically an app that automates the backend so users can focus on their customer facing page.
I belive there might be away in creating an AWS version of this service and offer it as a SAAS.
My question is : would you use an automated and hosted backend ( with your own provided domain) where you only have to take care of the frontend.
You would be able to customize your backend by declaring entities and their relationships using some sort of forms.
Hi Ademi - have some thoughts, but was also wanted to clarify a couple points.
As an open source project (under MIT license), you shouldn't have any problem hosting this on AWS and offering it as a service.
Note: some open source software has recently starting instituting different licenses to prevent AWS, Google etc.. from simply providing paid versions of the software. Strapi is still MIT, but something you'll want to keep in mind. See: https://techcrunch.com/2019/02/21/redis-labs-changes-its-open-source-license-again
**A couple of points: **
Strapi is pretty simple to install. It has a very simple set of dependencies. The Node+SQLite version being the simplest. They also have pre-baked docker images ready to go, so IMO there isn't a lot of value in doing this for someone else given that it's reasonably easy to do (for developers).
On the flip side, if you are targeting non-technical folks or just want to alleviate them of the install/maintenance of the Strapi deployment, then you are now competing with a huge list of headless CMS providers in the space (Contentful, Sanity.io, StoryBlok, GraphCMS and Cosmicjs to name a few).
It's doable, but this is a fiercely competitive space.
With respect to this:
With respect to this:
Good luck, happy to provide more insight as well. I've personally tested almost all these headless CMS options, and use 2 different ones in production now, so I have some context in the space.
Hi Johnny,
Thanks to your reply, all of the point you've raised are valid. The last thing I would want is to be put in the same category as AWS and GCP. I guess sometimes it takes a new set of eyes to call me out on my BS.
The value is to provide a server-less hosting service. Where customers pay only for what they use in terms of memory and what their website use in terms of bandwidth. The idea would be to abstract all the headache of the managed serverless services a cloud provider.
I still think their might be good potential in this, and customers would end up paying less for better services in terms of availability and security.
However, I'm going to abandon the idea on the premise that I don't enjoy the web Devops maintenance and the huge responsibilities that comes with it. To be frank, I've been trying to launch a personal website for the last few months, but never got to finish it because of how boring and predictable it is to create a website.
Thanks again, I guess the searching phase of my journey hasn't finished yet.
My intent was definitely not to discourage you... just wanted to clarify and make sure I understood your idea. To your point, if you aren't interested/passionate about the idea, it'll be hard to stay motivated during the tough times.