The TailAdmin free Next.js template ships a homepage field pointing at the paid demo, and a feature table its own changelog contradicts

The declared homepage is the Pro demo, and the free demo is listed second

The repository's declared homepage address is nextjs-demo.tailadmin.com. The demos section of the readme lists that address second and labels it the Pro version demo, while the free version demo is nextjs-free-demo.tailadmin.com, listed first. So the one address a tool, a package index or a search listing would pick up from the repository metadata leads to the paid product rather than to the code in the repository. The same section then points at a pricing page and at a Figma file marked as the community edition, and the quick links above it mix the two tiers as well, carrying a pro version link next to the download and documentation links. Anyone arriving from the homepage field alone has no way to tell from that address which of the two demos they are looking at.

The free tier's changelog adds the dashboards the comparison table reserves for Pro

The feature comparison gives the free version one unique dashboard, thirty or more dashboard components and fifty or more UI elements. The changelog for the same repository says otherwise. Version 2.3.0, dated April 28 2026, adds an AI dashboard with token usage and revenue tracking, a sales dashboard with retention and multi-channel analytics, and a finance dashboard with cashflow and balance management, plus six new layout variations. Version 2.3.1 adds an AI settings page for models, keys and token limits, a maps page, a vector maps page, a radar charts page and a radial progress charts page. Version 2.4.0 adds internationalization and a calendar year view. A reader sizing the free tier from the comparison table is working from a count the repository's own release notes have moved past.

The Pro row announces seven dashboards and then names ten

One bullet in the comparison table reads seven unique dashboards, followed by a colon and a list: Ecommerce, Analytics, Marketing, CRM, Stocks, SaaS, Logistics, AI, Sales and Finance, with a note that more are coming. That is ten names under a heading of seven. The free row above it uses the same structure with a single name, one unique dashboard, so the two rows are meant to be read the same way, which makes the arithmetic in the second row visible rather than a matter of interpretation. The component counts follow the same gap: fifty or more elements in the free tier against five hundred or more in Pro. Both rows are marketing copy for a paid tier linked from the same page, and neither carries a date.

Three Next.js 16 upgrade lines, and a breaking-changes list that stops mid-word

The version history mentions the Next.js upgrade four times. Version 2.0.0 in February 2025 records a migration from Next.js 14 to Next.js 16, skipping 15 entirely. Version 2.0.2 in March 2025 records an upgrade to Next.js 16.x for concerns around a named advisory, CVE-2025-29927. Version 2.1.0 in November 2025 records an update to Next.js 16.x again. Version 2.2.3 in March 2026 is the only entry with a specific number, an upgrade to version 16.1.6. The manifest now asks for next at ^16.3.4, so the most precise version named anywhere in the history is four minor releases behind what the dependency range covers. The breaking-changes list under version 2.0.0 also stops partway through the line about chart components, after the words Chart compon.

One vector map package, and three separate answers to its peer dependency

Two packages carry the vector maps, @react-jvectormap/core at ^1.0.4 and @react-jvectormap/world at ^1.1.2, and neither is happy about React 19 on its own. Three mitigations appear for that single problem. The manifest has an overrides block covering both packages, rewriting their React and React DOM peer ranges to accept anything from 16.8 upward including 19. The changelog records where the block came from, an entry for version 2.0.2 noting that vectormap overrides were included to prevent peer dependency errors during installation. And the installation section tells readers to use the --legacy-peer-deps flag if a peer dependency error turns up anyway. The overrides are the narrow fix, the flag is the blunt one, and both are documented for the same failure.

The changelog names three map libraries and the manifest names a fourth

Version 2.3.1 describes a maps page built with MapLibre GL, Leaflet and iframe styles. Version 2.4.0 then records an updated maplibre-gl implementation with react-map-gl. None of those three packages appears in the dependency list. What the manifest holds instead is the jvectormap pair, plus a hand-written declaration file named jsvectormap.d.ts sitting at the repository root rather than inside a types folder, which is what a project carries when a dependency ships no types of its own. The changelog also mentions AmCharts 5 geodata powering a vector maps page, and amcharts is not in the dependency list either. Four libraries named in the release notes, none of them declared, against one pair that is declared and no name in the notes.

Version 2.4.0 exists as a field in a private manifest

The manifest marks the package private and gives it version 2.4.0, and the changelog's newest entry is version 2.4.0 dated September 13 2026, two days before the most recent push. There are no GitHub releases behind that number and no tag to point at, so 2.4.0 exists as a string in a manifest and a heading in a markdown file. For a template that people copy rather than install, that is workable: what a user gets is the source tree, not a package. It does mean there is no artifact to diff against, so a change a project makes to the template cannot be isolated later by version, and it means the changelog is the only record of what changed and when. The template's own scripts are correspondingly few: dev, build, start and lint.

Node 20 as the floor, a Windows path note, and five sibling ports

The single prerequisite is Node.js 20.x or later, and installation is three commands:

git clone https://github.com/TailAdmin/free-nextjs-admin-dashboard.git

npm install
# or
yarn install

npm run dev
# or
yarn dev

One aside sits under the clone step: Windows users are told to place the repository near the root of the drive if they hit problems cloning. The project also exists in four other frameworks, with separate repositories for the React, Vue, Angular and Laravel versions, all under the same organisation, so the page inventory is ported rather than designed once. That matters for expectations: a feature added here, such as the internationalization support in version 2.4.0, arrives in the other ports on its own schedule, and nothing in this repository tracks when.

Editorial conclusion

This template suits someone who wants a Next.js and Tailwind 4 admin interface to start from rather than to study: the components, the dark mode and the page inventory are all present in the free repository under the MIT license, and the changelog shows the pages being added at a fast clip through 2026. Two things should be checked before building on it. The free-versus-Pro table in the readme is behind the changelog, so do not treat its counts as current, and note that the same table's Pro row names ten dashboards after announcing seven. And read the map and vector-map sections against the manifest before assuming either library is installed, because the changelog names three map libraries while the dependency list names a different one entirely, with a hand-written type declaration sitting at the repository root to go with it.

Frequently asked questions

Official sources

1. Issues
2. License: MIT
3. Project website
4. README
5. TailAdmin/free-nextjs-admin-dashboard on GitHub