Frequently Asked Questions

React Bricks is a CMS where you define content structure using React components (called bricks), and editors compose pages visually within those constraints.

Developers stay fully in control of the code. Editors get a visual interface. AI can generate content that respects your design system.

In a traditional headless CMS, content modeling and frontend development are separate, so you need to map content models to UI through APIs calls and manual rendering of data.

With React Bricks, content structure is defined directly in React components. The UI is the model.

This reduces complexity and ensures that what editors see is exactly what users get.

Visual builders prioritize ease of use, but they often limit developer control or allow too much freedom, making it easy to drift away from the design system.

React Bricks gives developers full control over the code, while editors work visually within safe boundaries defined by the bricks.

This gives content teams the right amount of freedom without risking layout inconsistencies.

React Bricks is designed for teams that need both flexibility and control:

Instead of configuring content models in a separate system, you define editable content directly inside React components.

Each brick defines what content it accepts, how it looks, and how it can be edited.

This creates a shared system for developers, editors, and AI.

AI generates content using your bricks, respecting their structure and constraints.

This means the generated content fits your design system, preserves the layout, and does not require manual cleanup afterward. Of course, the content editors can edit visually anything generated by AI.

Yes, React Bricks exposes both an MCP and REST APIs that can be used by any agent for agentic content creation at scale.

Since bricks are normal React components, with just an added `schema` property, and since documentation is very good, LLMs are able to generate the bricks code from normal React components or from UI screenshots or Figma.

The generated code is still plain React, so developers stay in control and can review, refine, and extend it as needed.

We'll soon release also a SKILL.md file for Claude Code so that bricks generation will be even easier.

Yes. Since content is structured and tied to specific bricks, AI can only modify the fields that developers have exposed.

This helps preserve layout, consistency, and editorial control.

Editors interact with the actual page, not with a separate form or a disconnected preview.

They can click directly on content, edit text and images, and build pages using reusable bricks.

What they see in the editor is what will be published.

No. Editors can only change what developers have decided to make editable.

Structure, styling, and behavior remain controlled by the code, so your design system stays consistent across all pages.

You can get started in minutes using the CLI and a starter project.

The first steps are creating a free account and running a CLI command from your terminal (`pnpm create reactbricks-app@latest`).

Read the Quick start guide and follow the Interactive tutorial to create your first project and define your first editable bricks.

If you are on a free plan, you can join our Discord community and ask your questions.

If you are on a paid plan, you can contact us through our support email or by phone, based on your support plan.

React Bricks is designed for React and TypeScript.

It supports modern React frameworks including Next.js and Astro.

With Next.js, React Bricks also supports the App Router and React Server Components.

Yes. React Bricks can be integrated into an existing React or Next.js project.

You can progressively introduce editable areas without rewriting your whole application.

React Bricks does not add performance overhead to your frontend.

The admin interface is separated from the public site, so admin code is not included in the optimized frontend bundle.

With Next.js and Astro, you can use modern rendering strategies and, with Next.js, also benefit from React Server Components.

React Bricks is ISO/IEC 27001:2022 certified.

We follow strict security best practices and can provide all necessary documentation for security reviews and enterprise procurement processes.

React Bricks follows industry best practices for security and data protection.

We support enterprise requirements including secure API access, role-based permissions, GDPR compliance, encryption in transit, and encryption at rest.

Yes. Visit the Customers page to see companies and digital teams using React Bricks.

If useful, we can also put you in contact with current customers for referrals.

Yes, see our Security & Compliance page for SSO support details.

Contact us to discuss your identity provider and requirements.

React Bricks offers data residency options including EU and US regions.

Content is stored securely and delivered through APIs to your frontend application.

React Bricks is primarily offered as a SaaS platform, so content is usually stored on our infrastructure and accessed through our APIs.

For specific enterprise requirements, including compliance or fallback needs, we can discuss advanced hosting options.

You can define roles and permissions to control who can edit, publish, and access specific areas of your project.

This makes it easier to support safe collaboration across marketing, content, and development teams.

We are committed to protecting personal data and processing the minimum amount of data needed to provide our service.

Our infrastructure is designed with privacy and compliance in mind, including GDPR standards.

You can read our Privacy Policy.