React Bricks is a "no-code" tool for content editors and it is a "code" tool for developers.
We want to give the best experience to everyone:
You need a React developer in your team to set up custom content blocks for your website, matching your corporate image, because content blocks are defined in code as React components.
Content editors don't need to be developers, of course: they have a simple point and click interface with best in class visual editing experience. And they can change only what you allow them to change.
React Bricks is two things at once: it is a headless CMS where the content is persisted and a React library that you use to create your content blocks, which powers all of our starter projects.
While a pure headless CMS doesn't know how the content will be presented in the frontend, as it provides a decoupled editing interface, the React Bricks admin interface (hosted by you, together with the website) leverage the React Bricks library to enable true visual editing over content.
What you see in the Admin interface is exactly what you get in the frontend, keeping all the advantages of a headless CMS (no hassles setting up your server)
Visual tools are usually not flexible (for example Wix, where you cannot define your exact design system) or too flexible (for example WebFlow, which allows your users to change the design tweaking CSS properties).
React Bricks is a Visual tool constrained by your code. The content editor can edit just what you allow them to edit (visual editing where your developers put a visual editing component, change sidebar properties as defined by you on a component-base).
In this way Content editors have all the freedom they want and no more than they need. Flexible so that the design is your pixel-perfect design; but also safe.
You just need a computer (Mac or Windows) with Node.js, Git and a code editor.
In this way you'll be able to launch the CLI (npx create-reactbricks-app) and edit the project code.
If you are on a free plan, you can join our Discord server and ask your questions: we'll answer as soon as possible and you will receive the support o our community.
If you are on a paid plan you can ask for support using the support email address or a custom enterprise channel.
With React Bricks you can use the most performant React frameworks, like Next.js, Gatsby or Remix.
For example, if you use Next.js, with React Bricks you have the same performance you can have with a best-in-class Next.js website, as React Bricks doesn't add any overhead: the bundle is well splitted between the frontend and admin, so that no code from the admin interface ends up in your optimized front-end bundle. Be prepared for top page speed!
We support all the main React frameworks (Next.js, Gatsby, Remix) and all the build/cache strategies: SSG (static site generation), SSR (server-side rendering), ISR (incremental static regeneration).
React Bricks works with any CSS framework and with the main CSS-in-JS frameworks.
Sure: visit the Showcase page!
Feel free to ask us for referrals: we can put you in contact with current customers, so that you can check the advantages React Bricks is bringing them.
Yes, we support SSO for enterprise plans. Let's talk!
React Bricks is a SaaS, so usually data is stored on our databases and it is accessible using our APIs.
For particular enterprise needs, where you have to host the data on your servers for compliance reasons, we can talk about it!
At the moment, no. React Bricks is meant to be a full CMS platform composed of both a React library and SaaS APIs.
Since we often receive requests about embedding the React Bricks editor inside of other apps, we are studying an "embeddable" version of React Bricks. Let's talk!
We are committed to protecting personal data and processing the minimum amount of data needed to perform our services.
Be the first to discover our latest news. No spam, promise.