Refine

Data providers for REST, GraphQL, and Supabase Connectors map existing endpoints onto Refine hooks for listing, showing, creating, editing, and deleting records, so teams keep the backends they already operate.[1][2]

Auto-generated CRUD interfaces List, detail, create, and edit views scaffold from the data model, and every generated view stays open to hand customization rather than locking teams into generated markup.[1][2]

Authentication with named provider tutorials The docs cover general authentication plus dedicated Auth0 and Azure AD login paths, alongside Web3 wallet sign-in for teams that need it.[1]

ACL, RBAC, and ABAC authorization Fine-grained access control follows widely used authorization models out of the box, which matters for enterprise admin tooling with role-sensitive data.[1][2]

UI kit freedom across five integrations Projects can render with Ant Design, Material UI, Mantine, shadcn/ui, or fully headless markup, so the admin interface can match an existing design system.[1][2]

Realtime updates, audit logs, and multitenancy Dedicated guides address live data, change auditing, and multi-tenant isolation for operational applications.[1]

AI-assisted scaffolding with code export The hosted builder analyzes a backend into a blueprint, generates the app in a Web IDE, and hands over plain React code with one-click export instead of a black-box runtime.[1]

Deploy on standard React targets or Docker Applications follow Vite, Next.js, or Remix deployment guides, the project publishes official Dockerfiles for each, and the paid Pro tier adds Netlify hosting.[1][2]

React teams on existing APIs Data providers, CRUD generation, and table/form hooks remove boilerplate while the team keeps its own backend and design system.[1][2]

Compliance-driven organizations Documented own-infrastructure publishing plus Okta, Azure AD, Amazon Cognito, and Google Cloud Identity support fit deployments with identity and hosting requirements.[1]

Teams that insist on owning code One-click export of plain React code avoids adding another proprietary runtime to the stack, which the project states as an explicit enterprise goal.[1]

Non-technical teams Refine is a developer framework, so teams without React developers will ship faster with a low-code builder such as Budibase or Appsmith.[1]

Teams with no data source The workflow starts from APIs or backends you already operate, so a team with no backend and no appetite to build one gains less from the core framework.[1]

Non-React shops Everything in the documented workflow targets React rendering, so Vue, Angular, or server-rendered shops would fight the framework instead of riding it.[1]