r/serverless • • Jun 05 '20

Serverless Headless CMS - OpenSource & SelfHosted

We've been working for past 6 months on our serverless headless CMS and just launched it today on Product Hunt.

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?! I'm sure serverless isn't something I need to explain to this group here :)

Here are some of its features:
✅ Powerful content modelling UI
✅ GraphQL API
✅ Multi-language support
✅ 100% Javascript
✅ Microservices architecture
✅ Support for multiple environments and aliases
... and much more. For a full set of features check out the product landing page

How do we differ from Strapi: 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. No need to heavily over-provision your infrastructure ahead of peak demand events, such as Black Friday and similar. Stop paying for stuff you don't use*.

How do we differ from Contentful and 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 do we differ from 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 modelling is done code and configuration files. There is no multi-language support, no environments and aliases. Managing users and permissions is very rudimentary.

----

I would love to hear your feedback on what you think about the product and how we potentially improve it for the whole community. Also happy to answer any questions.

32 Upvotes

7 comments sorted by

2

u/sirmandude Jun 05 '20

This looks great. Any plans for a REST api for those who are lazy and don’t want to learn graphql? Do you have scheduled posts?

2

u/SvenA999 Jun 05 '20

We don't have REST at the moment, but it's something that can be implemented via our plugin system. If you're interested let me know and I'll point you in the right direction. Although learning GQL is easy :)

As for scheduled posts, we do have a revision system with support for draft posts so you can prepare them in advance. But the schedule feature is not there yet. It's a good idea, so we might explore it in the future.

3

u/cazzer548 Jun 05 '20

Being lazy is a great reason to learn GraphQL :)

1

u/brett0 Jun 05 '20

GraphQL is effectively REST under the covers, so you could make the REST requests yourself, but why, when the GraphQL clients are amazing and do all the heavy lifting for you :)

2

u/niggo372 Jun 06 '20

I guess because GraphQL does require a bit more setup work, defining your schemas and such. It's absolutely worth it, but definitely more work than just writing some REST endpoints.

1

u/brett0 Jun 05 '20

Which databases does it support?

Also, typo on your landing page (suing/using):

The beauty of suing a headless CMS is that your content becomes device and channel agnostic.

1

u/SvenA999 Jun 08 '20

At the moment Webiny supports MongoDB, but we already have support for DynamoDB on our roadmap. Over time we might explore adding RDS support as well. In which one are you interested in?

p.s. thanks for reporting the typo - will fix it right away :)