React-Admin review (2026): the open-source admin panel for a Next.js SaaS

Quick answer (July 2026)

React-Admin is the most popular open-source way to add a CRUD admin panel to a React app, and in 2026 it is still a fast, mature choice if you already have a REST or GraphQL API and are happy on Material UI. The catch a lot of reviews skip: the core is free and MIT-licensed, but the features a real SaaS admin needs first, role-based access control, an audit log, and realtime updates, live in the paid Enterprise Edition, which starts at 145 euros per month in 2026. For a greenfield Next.js SaaS that wants its own design system and RBAC on day one, React-Admin is often not the default pick, and this review says where Refine or AdminJS fit better.

We priced and mounted three of these before: React-Admin, Refine, and AdminJS. This is the single-tool, hands-on take on React-Admin.

What is React-Admin?

React-Admin is a frontend framework for building single-page admin applications on top of REST or GraphQL APIs, built by Marmelab on React and Material Design. It is MIT-licensed, has about 26,900 GitHub stars as of July 2026 (react-admin on GitHub), and connects to any backend through a "data provider" adapter. There are more than 45 published adapters (REST, GraphQL, Supabase, and others), and you can write your own.

The mental model matters: React-Admin is UI-only. You bring the API; React-Admin renders the list views, filters, forms, and detail pages against it. That is the opposite of a tool like AdminJS, which auto-generates an admin straight from your ORM models. React-Admin gives you more control over the API contract and less magic.

React-Admin in a Next.js App Router app

This is the part founders trip on. React-Admin is a client-side SPA. In a Next.js App Router project you mount it inside a client component, typically a dynamic import with server-side rendering disabled, so your /admin route renders in the browser, not on the server.

For an internal admin area that is usually fine; nobody needs an SEO-friendly, server-rendered dashboard behind a login. But be clear-eyed about it: you are embedding a Material UI SPA inside your Next.js app, not writing App Router server components. If your team picked Next.js specifically for server rendering and React Server Components, the admin panel will not use any of that. Refine can render inside your existing Next.js pages more naturally because it is headless; React-Admin comes with its own MUI shell.

What is free, and what the Enterprise Edition costs

Here is the honest economics, which the template roundups tend to gloss over. The open-source core is genuinely free and covers a lot: list and edit views, filtering, sorting, pagination, forms, optimistic UI, and the data-provider ecosystem. The things a production SaaS admin reaches for next are in the paid Enterprise Edition.

The Enterprise Edition is about 20 private modules plus support, priced per developer and billed annually in 2026: Team at 145 euros per month for up to 2 developers, Business at 290 euros per month for up to 10, and Corporate from 590 euros per month for unlimited developers (Enterprise pricing, 2026). None of that is unreasonable for a funded team. It is a real line item for a solo founder who assumed "open source admin panel" meant RBAC and an audit trail were included. They are not.

Where React-Admin wins

• Fastest path to a polished CRUD admin over an existing API. If you already expose REST or GraphQL, you can have a filterable, sortable, paginated admin in an afternoon.
• Maturity and breadth. Ten years of production use, a deep component set, and some of the best docs in the category. At 26,900 stars it is the most battle-tested option here.
• Material UI out of the box. If your team already ships on MUI, the look is consistent for free and the datagrid is excellent.
• You own the API contract. Because it is UI-only, React-Admin never dictates your backend or schema.

Where React-Admin loses

• Material UI lock-in. If you want Tailwind and shadcn/ui, or any non-MUI design system, you are fighting the framework. Refine is headless and lets you bring your own UI; that is the cleaner choice when the admin has to match a custom brand.
• RBAC, audit log, and realtime are paywalled. For many SaaS admins these are table stakes, and here they are an Enterprise line item. AdminJS ships access control in its MIT core; weigh that if budget is tight.
• It is UI-only. You still build and host the API and the data provider. If you want an admin generated directly from your database models with the least glue, AdminJS bolts onto a Node ORM (Prisma, TypeORM, Mongoose) with far less code.
• No server rendering. In Next.js it is a client SPA. Fine for internal tools, but it does not use the App Router features you may have chosen Next.js for.

The curator call versus Refine and AdminJS

Short version, since we already published the full three-way admin-panel comparison and a hands-on Refine v5 review:

• Pick React-Admin when you have a REST or GraphQL API, want a batteries-included MUI admin fast, and can either live in the free core or budget for the Enterprise Edition when you need RBAC, audit, or realtime.
• Pick Refine when you want a headless framework and your own design system (Tailwind, shadcn, Ant, or MUI), and more control over the shell.
• Pick AdminJS when you want an admin auto-generated from your Node ORM models with the least code and a fully MIT feature set, including access control.

Curator verdict

React-Admin earns its popularity: it is mature, fast to stand up, and the MUI datagrid is genuinely good. But "most popular" is not "default for a Next.js SaaS." If your admin has to match a custom design system, or you need RBAC and an audit log without a new annual invoice, start with Refine or AdminJS instead. If you already have a REST or GraphQL API, live on Material UI, and treat the admin as an internal client-side tool, React-Admin is still one of the safest picks on the board in 2026.