Skip to main content


Welcome! ๐Ÿ‘‹

Webiny is a JavaScript serverless application framework with a built-in CMS. We created Webiny specifically to help developers architect, build and deploy solutions on top of the serverless infrastructure, like AWS Lambda, DynamoDB, S3, and others. Support for other cloud vendors besides AWS is coming.

We believe that serverless is the future of development. There are many tools that help you deploy and monitor an app on top of the serverless infrastructure. Those tools do that well. But when it comes to architecting and coding an application your set of options is very limited. This is where Webiny comes in.

You can read more about Webiny and our philosophy below, but in case you want to immediately give Webiny a try, just follow the installation tutorial.

Our Mission

Create the foundation for building serverless solutions.

Webiny Overview

With Webiny you can build:

  • Full-stack applications
  • Websites
  • GraphQL APIs
  • Microservices

...all on top of the serverless infrastructure.


Webiny is built using a modern development toolchain that makes the experience for developers much more enjoyable. Technologies Webiny uses:


To learn more, please take a look at the

Tools and Libraries key topic.


Webiny comes with 2 products which are both installed when you setup your instance.

Serverless Application Framework

This is the core of Webiny. It's a framework created specifically for building serverless solutions. The framework handles the deployment workflow, code bundling, project organization, and provides a ready-made architecture. It also includes an ACL module, GraphQL API and a Admin Panel SPA app.

The goal of the framework is to provide a ready-made solution that you can use in a matter of minutes. Developers should no longer deal with the complexities that come with using serverless infrastructure.

Cloud support

At the moment Webiny only runs on the AWS cloud. If you wish to help us add support for another cloud provider, please see

this issue.

Serverless CMS

You might find it odd having a CMS as part of a framework. Our team spent more than 12 years building client-based solutions and many of the projects required some sort of a content management feature. In an ideal world we wanted to have a framework and a CMS combo, so we created one.

Webiny Serverless CMS is created with our framework. It's the best real-life example of what you can build with it and it provides you with many samples and references for your own apps.

The Serverless CMS is completely optional. It's installed by default, but if not needed you can easily remove it.

It's not a library

Serverless CMS is not a library that you can embed in other applications. It's a standalone application.

Our Philosophy

Webiny is created with 3 main goals in mind:

  • provide a customizable solution
  • have an amazing developer experience
  • have less abstraction, more clarity

Webiny at its core doesn't do much. Over 90% of Webiny's code is actually inside plugins. From how the Webiny CLI deploys your build, to how the API checks the user permissions, to the Webiny logo in side the Admin panel. Those are all plugins. This approach allowed us to build a platform that is flexible in every meaning of the word. You can completely replace existing plugins, turn them on or off or expand on them, customizing Webiny to fully fit your needs. An added benefit of this approach is that your plugins live outside the Webiny's core codebase, making upgrades much easier.

Another great thing about the plugin system is that it's unified across the board. It doesn't matter if you're changing the CLI functionality, adding new GraphQL resolvers or a new button in the UI, the approach is always the same. This makes it easy for anyone to pickup and understand how the whole system works.

Webiny believes in having a great developer experience. From first installing your project to deploying it and seeing it live all that's needed are 2 commands. Webiny handles all the heavy lifting under the hood, but in a transparent way, not hiding anything, or making it hard to understand. Less abstraction means better understanding of the system.


We welcome anyone who wishes to be a part of our project and help us achieve our mission. If you're looking at code contributions, check

this link, for documentation contribution check this one. If you want to have a chat with the dev team, you'll find us on our community slack.

Staying Informed

Our project and documentation is constantly improving and changing. Anything important we post to our

blog and our newsletter.

Additionally, you can find useful information on our Twitter handle


Something Missing?

If something is missing in the documentation, or you've found a part that's confusing, please report an

issue to our docs repository.

For any other questions of feedback, please reach out via our

community slack.