React Bricks

React Bricks is a visual headless CMS for React, with starters for Next.js and Astro. Its homepage sums the idea up in three verbs: define your CMS in React, create with AI, edit visually. It is written for developers who want to keep a real React codebase and a design system, and for the content editors and marketing teams who then build pages on top of it. The company behind it is F2 .net engineering srl, per the footer, which carries a 2019-2026 copyright range.

What you build and how

Blocks made from React components. Developers build reusable content blocks, called bricks, with React and TypeScript. The company says its "fully typed library" lets them stay in the code editor and define what content can be edited, with complete control over structure, styling and validation. The homepage describes the step as turning React components into visual content blocks in minutes. Constraints live in code, so the design system stays intact.

Inline visual editing. The company says React Bricks combines headless CMS architecture with true inline visual editing. Editors work on the page itself and see the final layout while they work, which the company contrasts with filling in forms and side panels in a typical headless CMS. What editors can change is limited to the fields and controls developers expose, so editors compose pages from approved bricks and cannot break the layout. In practice, editors click on text to edit it and click on images to replace them, "Just like using a word processor," and change layout options, colors or content variations through sidebar controls, but only within the options developers allow.

AI page generation. React Bricks says AI can generate full pages using your own components, so every result follows your structure, layout and brand. The homepage promises no broken layouts and no off-brand content, calls the approach built for agentic AI workflows at scale, and offers an AI demo and enterprise early access. The same components that editors use power the AI-generated pages.

Architecture. A company blog post explains the model it calls a Universal CMS. Developers create their own set of content bricks in their repository, using library components for things like Text, Image and Repeater. The backend APIs do not know how bricks look in code. They store a JSON representation of each page as an array of blocks, each with the name of its brick and the properties editors filled in. The content management interface lives inside the frontend project, in the same repository as the bricks and pages, so the website and the admin can be hosted on the platform you prefer. Inside a brick's JSX, developers use React Bricks' visual editing components, such as Text, RichText, Image and Repeater, and decide what can be edited visually and which rich text styles each text allows. The features page adds that it works with any CSS framework and lets you host the frontend wherever you prefer, including the visual editing admin interface.

Platform features. The features page calls React Bricks a complete CMS platform, with Digital Asset Management, Localization, Collaboration, Scheduled Publishing, Advanced SEO, AI content generation, A/B testing, form management and email marketing. The feature menu also lists components, image optimization, and flexibility and extensibility. The enterprise section of the menu names security and compliance, A/B testing marked New, content versioning, roles and permissions, an approval workflow, multiple environments, enterprise support and a self-hosted version.

Use cases. The homepage names four: enterprise teams (scalable and secure), marketing teams (create high-performing sites with visual editing and full design control, and launch campaigns faster without relying on developers), composable commerce (flexible e-commerce experiences on your existing stack, integrated with a headless architecture) and digital agencies (reusable components and visual editing across clients). Starting a project means the React Bricks CLI with Next.js or Astro, and the site points to a quick start, an interactive tutorial, documentation, how-to guides, a 1-hour workshop and a changelog.

The evidence from the pages

The site publishes no prices on these pages; the navigation links a Pricing page, and the buttons offer Try for free, Live demo and Contact sales, while the company blog invites readers to "create a free account."

What the pages do claim:

• "Built for governance and compliance, ISO 27001 certified." The homepage also links an ISO 27001 Certificate and an ISMS Policy from its footer.
• The features page lists a self-hosted version under enterprise features, and the architecture post describes hosting the site and the admin where you prefer.
• The company blog, in a post by the CEO, says React Bricks launched its first official version in March 2020 and is in version 4. It lists enterprise features including localization, Digital Asset Management, scheduled publishing, approval workflows, Single Sign-On (SSO), granular permissions, integration with external data sources, real-time collaboration, content versioning, page templates and automatic backup of content and assets to the customer's S3 storage.
• The same post says that as of October 2024 React Bricks served over 10,000 users worldwide, powering websites for The Weather Channel and Deel, with a client base that includes major banks in Italy and France.
• The homepage case study names Yulife, which it says uses React Bricks to give its team autonomy while keeping full control over design and code.
• Stefan Nagey of Deel is quoted: "With React Bricks, our team can move faster without losing control. Developers define the system. Editors build pages safely."
• The footer marks the product Patent Pending, and the homepage banner promotes a recording of the latest workshop.
• Community and support links include a Discord server, a Code of Conduct and a System status page.

The company's framing of its own category is worth knowing: it calls React Bricks a Universal CMS, where developers decide how much freedom to grant editors and the bricks sit between a fixed headless form and an open canvas.

Who it suits and who it does not

React Bricks suits a team that already builds in React or Next.js, or Astro, and wants marketers to own page building without a developer in every edit. Agencies that reuse one component library across client sites are named on the homepage, and enterprise teams get a feature list aimed at governance. A developer who wants an escape hatch into code has it, because the editor is built from real components in a repository the team controls.

The caveat is that it is not a no-code product, and the company says so: the site argues it does not turn a website into a no-code project. Someone has to write the bricks in React and TypeScript before an editor can compose a page, so a solo founder without React skills, or a team on another stack, will need a developer first. The self-hosted version is listed among enterprise features, so a small team should expect the hosted setup by default.