Serverless Headless CMS by Webiny

Go serverless with Webiny and save 60-80% on hosting costs

Stop paying for stuff you don't use. A big chunk of your server resources aren't utilized. With Webiny adopt serverless and save 60-80% on your cloud hosting bill and on infrastructure operations costs. Forget worrying about flash crowds and uptime.
Would you recommend this product?
16 Reviews5.0/5
Hey ProductHunt! I'm thrilled to announce the launch of Webiny Headless CMS. So why you need another Headless CMS? For a change, with this one, you won't worry about scaling, installing, configuring and managing infrastructure. On top of it, Webiny cuts your cloud hosting bill by anywhere between 60% and 80%! You will stop paying for resources you do not use. Now, who doesn't want all that?! Here is a quick overview of some of the features: ✅ Powerful content modelling UI ✅ GraphQL API ✅ Multi-language support ✅ 100% Javascript ✅ Microservices architecture ✅ Support for multiple environments and aliases ... and much more. How is this different than Strapi? Well, Strapi runs on the "traditional" infrastructure, such as virtual machines and similar. That infrastructure is hard to maintain and scale without hiring a big team of expert engineers. Since Webiny runs on serverless infrastructure such as AWS Lambda, it can scale to handle millions of requests out of the box. No need for any performance, devops or network engineers. The other beautiful thing is that with serverless you pay per request. You don't need to heavily over-provision your infrastructure ahead of peak demand events, such as Black Friday and similar. How is this different than Contentful or GraphCMS? Webiny is open-source and you host it yourself. This means you own and have full control over your data. On top of that, you can build custom apps and change any part of the system. Unlike Contentful or GraphCMS where they are a black-box SaaS product which you can't modify. How is this different than Netlify CMS: Netlify CMS is a great solution but it lacks many of the features you'll find in Webiny. Netlify CMS caters for more simple sites. For example, a feature like content modeling is done in code and configuration files. There is no multi-language support, no environments and aliases. Managing users and permissions is very rudimentary. The whole Webiny team is here to answer any of your questions. We hope you give Webiny a try and let us know what you think.
@svenalhamad This looks pretty fantastic. I've been keeping tabs on Webiny for a while now and sort of waiting for the CMS to be released. I think Webiny has a huge potential for growth. I remember early on as a core developer of WordPress — what put WP on the edge. Feel the same here. Makes me super excited to give it a try. If y'all ever need help, holler at
@mrahmadawais Also, if you do give Webiny a spin, let me know your comments. I'm sure we could learn a lot.
@svenalhamad I've used Netlify CMS, but have no experience with the other services you mentioned. I haven't taken a look at your website yet, but reading the comments on PH I've gotten the impression that your product would let me have something like 'my own Netlify CMS' that is going to run on AWS, correct?
@anna_0x In essence yes. So Webiny is deployed to your own AWS account and it runs on top of services like AWS Lambda, Api Gateway and S3. The database we support today is MongoDB Atlas, which is also a fully managed service that is deployed to the same AWS region as other services.
Never made any experiences with Strapi, Contentful, GraphCMS oder Netlify before. Heard of them but never used them. It might be your product that I'll take a look at betimes. It looks great!
@xreeel Thanks Marvin! If you do spend some time with it. Let me know what you think and how we can make it better for the whole community!
I've been an early adopter of Webiny and love this product. It's already well built and very promising. The idea of a headless, self-hosted serverless CMS is going to meet the needs of so many organisations and individuals who need a solution for their distributed architecture.
@endymion1818 Thank you Ben for the kind words and also for sticking with us through many iterations and changes we had to make!
Never really played around with a serverless setup. Is this targeted for apps and smaller projects? Or also to (ultimately) replace bigger content-driven projects. E. g. we run a more or less classic WordPress Project with more and more vuejs components being added onto it. The main advantage of going serverless in such a case would be security and page speed, right?
@nils_dannemann Hi Nils, let me try and address your questions: 1. With Webiny you can build both large and small websites as well as web applications. It will easily cater for both use-cases. Webiny admin, the backend UI, is designed so you can add many modules to it, and still keep all the things neatly organized for your users. The project structure that Webiny uses is also created in a way that developers can structure their code in several different ways depending on the requirements of their project. 2. The main advantages of going serverless would be significant cost reductions in cloud infrastructure, as you will stop paying for resources you don't use. On top of that, there is zero maintenance, so your team will be able to focus on more important stuff than updating server versions. Lastly, you'll get pretty much unlimited scale as serverless scales it's resources in milliseconds, so your sites can handle any demand. More info on that is available here:
@svenalhamad Thanks for the detailed answer! Much appreciated. I'll give it a shot for my next side project! Looks great. Well done!
Very happy to see this. The need for a solid, headless and serverless cms has been evident for some time now. Great to see someone finally deliver. I'll be checking this out for possible uses right away.
@eliasisrael Thank you Eli! Feel free to reach out to us if you have any questions.