React Bricks was born out of our necessity at the end of 2019.

We were a React-skilled web agency back then, and we needed a CMS that was great for us, like a headless CMS, but that was great also for our customers and their content creators.

We were tired of maintaining WordPress as a headless CMS. The new headless CMSs were not an answer to our customers' need to have a simple editing interface.

In fact, with headless CMSs, not only they were back to gray forms, but they also missed the concept of "page", while navigating abstract structures, like database tables.

We could feel our customers' pain and their pain became also our pain as we had to train and support them on systems that were not intuitive.

What's more, headless CMSs don't give developers a method, just much freedom. So, for every new hire, we needed to explain our way of working to them.

We wanted to change that: we wanted to make content editing fun, with the right level of freedom, but good constraints and a well-defined method. And we wanted a one-stop-shop system, great for enterprise customers, too.

We did it. 😎

React Bricks has a top developer experience, as it is just React. Developers define content blocks as React components, implementing the design system with all the needed good constraints.

And it is extremely easy to use for content editors: if they can use Word or Pages, they can use React Bricks.

Working with top players around the world, like Casavo, Banca Mediolanum or The Weather Channel, we steadily developed features that make React Bricks enterprise-ready, such as fine-grained permissions, collaboration and integration with external data sources.

We are bootstrapped, with no external funding and profitable from the first year.

We are very proud of what we have built and we are working to be very proud of what will come.