Refine v5 review (June 2026): hands-on with the open-source React admin starter for Next.js

Quick answer (June 30, 2026): Refine v5 is the open-source React framework you actually want for an admin panel or internal tool starter in 2026 if you intend to ship in React 19 and you do not want a vendor-locked low-code IDE in your stack. The v5 line shipped in January 2026, the latest stable on npm is @refinedev/core@5.0.12 from April 2, 2026, the GitHub repo is at 34,988 stars with the last commit on June 5, 2026, and v5 is the release that ripped out the deprecated v4 surface, swapped TanStack Query v5 in, and reshaped every data and mutation hook to return { query, result, mutation } instead of the old flat tuples. You pair it with Next.js 15 or a Vite shell, plug in your backend adapter (Supabase, Hasura, NestJS, Strapi, Medusa, REST), and you have a typed, headless admin you can deploy on Vercel for free or self-host on a $7 Render box. The catches: the 4 to 5 migration is mechanical but not small if your team has been on v4 for two years, the Refine company is now pushing a closed-source "Refine agents" product priced at $0.99 to $20 per month on top of the OSS framework, and react-admin (26,818 stars, latest 5.15.1 on June 24, 2026) is shipping more frequently to its mainline this quarter, which is a real maintenance-signal question for anyone choosing between the two today.

Is Refine v5 still being shipped in June 2026?

Yes, with a caveat the homepage will not tell you.

The refinedev/refine GitHub repo sits at 34,988 stars and 3,111 forks, the default branch is main, the last commit landed on June 5, 2026, the license is MIT, and the open-issues count is 44. The @refinedev/core package on npm is at v5.0.12, published April 2, 2026, and the rest of the package family (@refinedev/mui@8.0.2, @refinedev/devtools@2.0.5, @refinedev/cli@2.16.52) shipped in mid-March 2026. v5 itself dropped on January 21, 2026, per the official 4x to 5x migration guide.

That is a healthy framework. It is not a frantically active framework. For contrast, marmelab/react-admin (the older incumbent in this category) sits at 26,818 stars but pushed code to mainline today, and the latest react-admin@5.15.1 shipped on June 24, 2026. The two projects have made different bets: Refine pours engineering into a new commercial product line ("Refine agents") and ships fewer mainline framework patches in between; react-admin ships smaller, more frequent patches and has not pivoted to a hosted AI product. If you treat shipping-cadence-on-the-OSS-repo as a maintenance signal, react-admin currently looks more alive than Refine. If you treat ecosystem-and-adapter-count as the signal, Refine is still ahead.

What is new in Refine v5 (and what got removed)

Three things, in plain English.

1. React 19 support. Refine v5 builds and runs cleanly on React 19, including the new use hook and React Compiler ergonomics. React 18 still works; React 19 is the recommended target for new starters.

2. TanStack Query v5 under the hood. TanStack Query moved from v4 to v5 in the Refine dependency tree. The most visible consequence: every Refine data and mutation hook now returns a structured object with query, result, and (for mutations) mutation keys, instead of the old flat properties on the return value. The migration guide spells out the exact rename map: queryResult becomes query, tableQueryResult becomes tableQuery, mutationResult becomes mutation, and isLoading on mutations becomes isPending.

3. Deprecated v4 APIs are gone. useNavigation (with its push, replace, goBack methods) is replaced by separate useGo and useBack hooks with clearer intent. metaData is renamed to meta across every hook. ThemedLayoutV2 (and its sibling components) lost the V2 suffix; you now import ThemedLayout. AuthBindings and RouterBindings types are renamed to AuthProvider and RouterProvider. The useResource hook is split into useResourceParams. The flat config parameter on data hooks is gone; pagination, filters, and sorters now live under dedicated objects with initial, permanent, and mode properties.

None of this is novel. All of it is mechanical. If you have a v4 codebase, set aside a full afternoon per data screen and budget for two weeks across a real production app.

A fourth change is not in the migration guide and you should know about it: Refine the company now publishes a commercial "Refine agents" product. The homepage tagline as of June 30, 2026 reads "Internal software at the speed of AI", and the visible flow describes an AI-led builder on top of the OSS framework. Pricing is $0.99 per month for 300 credits, $20 per month for 1,500 credits, enterprise custom. The OSS framework stays MIT and free; the agent product is closed and separate. Flagging because the homepage now reads more "vendor with an OSS leg" than "OSS framework with optional services."

Five deploy paths for a Refine v5 admin starter

The starter we tested is the official npm create refine-app@latest output, the Next.js + Refine + MUI flavor, pointed at a Supabase Postgres backend through @refinedev/supabase. Five deploy paths matter in 2026.

Vercel is the path of least resistance for the Next.js flavor. The Refine app boots as an ordinary Next.js 15 app, the only env that matters is your Supabase URL and anon key, and the starter SSRs the auth shell. Hobby covers a personal admin; go to Pro ($20/month, June 2026) once you need protected branch previews.

Netlify works for the Refine + Vite + React Router flavor. Ship it as a static SPA, dist/ from npm run build, with a Netlify Function for the Supabase auth callback. Free tier covers a single admin under 100 GB bandwidth a month.

Cloudflare Pages is the cheapest serious option. Vite output deploys as static assets, Pages Functions proxy any API call that needs a server secret, and the free tier is the actual free tier (unlimited bandwidth, 20,000 build minutes a month). Cold start on Workers was sub-30 ms in our run.

Render is the right call when you want one persistent web service running a Refine + NestJS combined deploy. Starter is $7 a month, builds run from GitHub, autodeploy-on-push is enough.

Fly.io is the answer if the admin should live near Postgres replicas in multiple regions. Refine + Vite + Node SSR deploys with fly launch, the free allowance is roughly 3 small shared-CPU VMs, and you can scale to zero on nights and weekends.

Honest note: Refine itself does not care which one you pick. It is a React framework. The choice is downstream of where your auth provider and your database already live.

Per-month all-in cost for a small Refine v5 admin

Concrete numbers for a real internal admin running roughly 10,000 page views a month with a 200 MB Postgres and roughly 50 active editors.

The framework itself is free. What you pay for is the hosting and the managed database. The cheapest serious deploy is Cloudflare Pages + Neon Free; the most production-credible deploy for $50 or less is Vercel Pro + Supabase Pro; the cheapest path that does not put your database on someone else's free tier is Render Starter for $14 a month all-in.

The "Refine agents" closed-source product line is a separate cost line we did not include because we did not use it. If you do enable it, add $20 a month for the Pro plan, billed on top of the hosting above.

Where Refine v5 does not fit

We would not pick Refine v5 for these three cases.

1. You need a low-code drag-and-drop admin builder. Refine is a framework. You write TypeScript. If your team is mostly business analysts and you need a Retool or Appsmith-style canvas, look at Appsmith (40,200 stars, last push today) or ToolJet (38,118 stars, last push today) instead. Both are more popular by star count, both are MIT, both let non-engineers click together a CRUD screen without writing JSX.

2. You need a 100% built admin product, not a framework to build one. If what you want is "a CRM that runs", look at Twenty CRM as a finished open-source CRM rather than a kit to build one. Refine is for the team that wants to own the data model and the UI; Twenty is for the team that wants a CRM to use this afternoon.

3. You want the most actively-shipped admin framework in this category. As of today, that title belongs to react-admin: 26,818 stars, a commit pushed an hour ago, react-admin@5.15.1 published six days ago. Refine's last mainline commit was June 5, 2026; the rc cadence on @refinedev/core slowed visibly after v5.0.12 in April. A real Reddit thread, Refine is extremely unstable and unusable, captured the same pattern in 2024; v5 is much better than that thread reads, but the root concern is worth a budget line in your migration plan.

A note on the IDE side of this. Most teams writing Refine v5 in 2026 are pairing it with Cursor or Claude Code rather than a bare VS Code, because the new hook return shapes ({ query, result, mutation }) are exactly the kind of mechanical rewrite an AI IDE handles in a single pass. If you have not picked your AI dev IDE yet, an honest hands-on comparison we kept tabs on walks the tradeoffs between the IDE-native and the terminal-native option for that work specifically; the article is not Refine-focused but it covers the only two surfaces a Refine v5 migration realistically touches.

If you build internal admins for clients rather than for yourself, DevShopVault's notes on production-ready AI app builders for agency client work cover the related question of when to write a Refine starter from scratch versus when to plug in a builder, and the agency-economics arithmetic of either path.

FAQ

Is Refine v5 free? Yes. The OSS framework is MIT-licensed and free for any use, commercial or otherwise. The separate "Refine agents" product is paid and starts at $0.99 per month for 300 credits.

Should I migrate from v4 to v5 today? Only when you can budget two clear weeks per medium-sized admin and you have a CI gate that catches the renamed hook return shapes. The migration is mechanical; the bug surface is whatever screens you forgot to test. Reasonable plan: pin v4 in production, branch v5, ship behind a flag.

Is Refine production-ready in June 2026? Yes. It is in production at YC-backed companies, the v5 line is six months old, the test suite is real, and the bug count on the repo is manageable. The maintenance-cadence concern (lower mainline commit frequency than react-admin) is real but it is not "abandon ship" real.

Refine v5 or react-admin in 2026? Refine if you want first-class adapters for many backends (Supabase, Hasura, Strapi, NestJS, Medusa, Airtable, Appwrite, REST, GraphQL) and a headless UI you can swap. React-admin if you want the most actively-shipped option and you are already deep in Material UI without wanting to debate it. Both are MIT, both are real frameworks, neither is the wrong call.

Does Refine v5 work with a Medusa.js backend? Yes, via the official @refinedev/medusa adapter package. If you are building a commerce admin on top of a Medusa.js backend, our hands-on Medusa.js v2 review covers the Medusa half and Refine's @refinedev/medusa covers the admin half.

What is the smallest credible Refine v5 deploy? Cloudflare Pages plus Neon Free. Zero dollars per month, real Postgres, a CDN at the edge. You will outgrow Neon Free if your admin sees more than a handful of concurrent editors, but it is a real starting point and not a toy.

Your move:

If you have been waiting to pick a React admin framework and you want the option that pairs cleanly with Supabase, Hasura, or Medusa for a Next.js 15 deploy, install Refine v5 this week, ship a single CRUD screen against your real database by Friday, and decide based on the migration friction in your own codebase rather than a thread on Reddit.