[wyck]

The toolset looks like you made it for your own workflow and not actual users, meaning it's very rigid and tied to specifics instead of allowing for flexibility, I have a hard time actually understanding what this is for. The main feature of it being serverless isn't a selling point for me. I don't use Graphql/DynamoDB or any of the tools you describe outside Lambda. It would be simply too much work to start with all your tooling, that would be considerable technical debt especially compared to the ocean of options available with headless CMS's.

[paveldenisjuk]

Webiny is definitely not for everyone; it does have specific technologies engraved in the offering, like nodejs, React and GraphQL. That, however, doesn't mean you can't build a REST API with it. Webiny is first of all a development framework, to help you develop apps for serverless infrastructure. It's very flexible, and we're already working on more things that will make it even more adaptable to different technologies. Then on top of that we built the Headless CMS, the Page Builder, etc. to showcase the possibilities of both the framework and serverless services, as many developers are still hesitating to use them.

The features we built into our apps and framework are directly taken from our own experience (we used to run a digital agency for 10 years), user feedback and many hours of calls with other agencies and enterprises. We do love user feedback as we can't possibly foresee all the possible use-cases - and that's how we improve our platform.

If you don't use GraphQL or DynamoDB - that's perfectly fine. There will always be problems that are easier to solve without bringing a full featured framework into the mix. We also like to spawn a Lambda or two with some simple code for simple solutions. But for larger projects, we offer project organization, workflows, infrastructure organization, system of plugins, and ready-made apps which can really save you a lot of development time.

Regarding other CMS's - yes there are many. But not many that are open-source and running in a serverless environment. SaaS solutions are not acceptable for every type of customer, especially not enterprises. They want to have their data in their own private cloud.