[Launched] First Open Source Headless CMS Running on AWS Serverless To Cut Hosting Bill by 60%-80% by@webiny

[Launched] First Open Source Headless CMS Running on AWS Serverless To Cut Hosting Bill by 60%-80%

Webiny Serverless Framework HackerNoon profile picture

Webiny Serverless Framework

#OpenSource #React #NodeJs #GraphQL #Headless #Serverless

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?!

It's the first Headless CMS which runs on top of AWS serverless infrastructure. It's open-source and you host it on your own AWS cloud. You can use your favourite frontend development library, like GatsbyJs, Next.js and others to build your sites.

We just launched Webiny on Product Hunt and if you like what we're building here - please show us some love ❤️😻.

So, What Can It Do?

You'll find all your standard features like in most other solutions, but also a bit more. Here is a quick overview of some of its features:

Powerful content modelling interface with focus on UX — not only you model your content, but also build the interface for how the input forms will look like to your content editors. Place fields inside a grid layout and split it into multiple columns and rows. Organize and build the main menu, so it's easy and intuitive to find and access the content.


Content localization — a simple and intuitive way to input and serve content in multiple languages. We keep the interface for editors clean and easy to use, no matter if you have 1 language or 20 languages. 

✅ GraphQL API —  The API is at the core of every headless CMS. If you get the API wrong, the whole product has a poor experience. This is why we spent a significant part of our effort on ensuring developers have a great experience using our API. The API also comes with a built-in GraphQL playground, so it’s super simple to inspect your schema and test your queries. 


✅ Environments and aliases — With a single click copy your existing data into a new environment. Modify it and update it without affecting your production site. Finally, remap the alias to switch the new environment into production. With this approach, you get instant rollback feature as well as there is no need to update and re-deploy your code to any of your devices when you make changes.

✅ Customizable and extendable platform with a microservices architecture — Having a headless CMS is great, but what if it only gets you halfway? What if you need to build custom code, add logic with specific rules that are outside the scope of the headless CMS. This is where Webiny shines. Using the Serverless Web Development Framework you can build any type of logic your project requires and deploy it alongside the headless CMS as a separate microservice. 

There is much more in there. For a full set of features check out the product landing page and the documentation.

But there are already existing solutions like Contentful, Strapi, GraphCMS and others, how do you differ?


Webiny vs a SaaS Headless CMS (i.e. Contentful, GraphCMS …)
When it comes to the SaaS offerings in the headless CMS space, it’s a pretty crowded market. 

The advantage of a SaaS solution (although they also refer to themselves sometimes as “serverless”) is that they internally have a team of people to manage the infrastructure for you. So you don’t need to worry about the scale and maintenance factor. 

The tradeoff you’re making by choosing SaaS is that you’re basically working with a product that you have no control over. You cannot modify the product to fit your requirements and you can’t use it to build other custom modules on top. Not to mention the fact that they have all of your data.

When you compare that to Webiny Serverless Headless CMS, which is open-source, you get the ability to fully extend and customize the system to fit your needs. Because Webiny runs in your own AWS cloud on top of the serverless infrastructure, you don’t need to manage the infrastructure to have a great scale and be able to handle peak demands. 

Webiny vs an OpenSource Headless CMS (i.e. Strapi)

With the open-source offering, developers get the full control and ownership of the system, but the TCO (total cost of ownership) of such a system in many cases can be higher than a SaaS product.

The reason is that you need to hire several devops and network engineers to manage, scale and operate the infrastructure for you. This is because all the current open-source solutions are designed to run on top of a traditional virtual machine or container infrastructure. 

In addition to the human-cost, you often have to over-provision the infrastructure and pay for the parts you are not utilizing, to be able to handle peak demands. 

In essence with open-source, you trade the scalability for customization but at a higher cost factor.

When it comes to Webiny again, being serverless brings you the scale, but at a zero cost increase, and at the same time you don’t lose any of the open-source benefits and you stop paying for resources you are not using.

Webiny vs 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 in Netlify CMS, a feature like content modelling is done code and configuration files. There is no multi-language support, no environments and aliases. Managing users and permissions is very rudimentary.

If you have even a slightly more advanced use-case, with Netlify CMS you might have a hard time getting it done.

Unlike Netlify CMS, Webiny is designed for both simple tasks as well as a complex one. Webiny provides you with all the features you will need to successfully deliver your project.

Get Started

To get started with Webiny Serverless Headless CMS head over to our get started tutorial: https://docs.webiny.com/docs/get-started/quick-start

Support Our Project

If you love what we’re building here, we would appreciate if you would show us your support by either contributing or starring(★) our repository. This is what keeps us going!

Please tweet and share this news if you liked what we had to share.