Launch UI ships assembled landing page sections, not just primitives

A copy and paste kit, not a component library

Launch UI describes itself as a landing page kit built with React, shadcn/ui and Tailwind that you can copy and paste into your project, and the README calls it a collection of production-ready website components for Next.js.

The copy and paste part is the design. There is no npm package to install for the components themselves. The source sits in the repository, you take the files you want into your own codebase, and from that point they are your code, edited by your conventions and fixed by your bugs. The repository is MIT licensed, and the licence file is at the top level.

That model sits in the same family as shadcn/ui, and the connection is explicit in the tree. There is a `components.json` file, which is the shadcn configuration, and the dependency list is a list of Radix primitives, `@radix-ui/react-accordion`, `react-dialog`, `react-dropdown-menu`, `react-icons`, `react-navigation-menu` and `react-slot`, plus `class-variance-authority` for variant definitions, `clsx` and `tailwind-merge` for class handling, and `next-themes` for light and dark mode. Every shadcn convention applies, including the `cn` class merging helper.

The difference from shadcn itself is the level of the unit. shadcn gives you the primitives, a dialog or an accordion, with the look and behaviour set by you. Launch UI gives you the assembled marketing section, the hero with its illustration slot, the pricing grid, the FAQ accordion, the call to action. The work you would do is the composition, and that is the work this kit has already done.

Eight sections in the open tier

The component list is split in two, and the open half is what most landing pages actually need.

The included set is Navbar, with static and floating variants, dropdown menus and mobile responsiveness; Hero, with illustration based layouts, glowing effects and mobile app displays; Items, a grid system for feature lists, pricing tables and product displays in default and branded variants; Logos, a static grid for brand and client logos; FAQ, an accordion with expandable panels; Stats, a metrics display with horizontal, tile and grid layouts; CTA, a call to action with box layouts and beam effects; and Footer, with default, minimal and multi-column variants.

What each of these shares is a specific job rather than a generic container. Stats is for big numbers and key metrics. Items is the pricing table as well as the feature list, which is a smart overlap since both are grids of label, description and price. FAQ is the accordion, built on the Radix accordion primitive, so the keyboard and screen reader behaviour comes from the library rather than from custom JavaScript.

The animations are CSS animations and transitions, with the icons from Lucide, and the styles come from Tailwind. Nothing in the list requires a JavaScript animation library, which is worth knowing because that is where a landing page kit usually starts to cost you in bundle size and in hydration.

The README also lists the qualities the kit aims at, such as responsiveness across desktop, tablet and mobile, dark mode with system preference detection, WCAG compliant components, SEO oriented structure, and use of modern Next.js features for loading.

The advanced layouts are in the paid tier

The second half of the catalogue is the commercial proposition, and the split is the most important thing to understand before adopting the repository.

The Pro version at launchuicomponents.com/pricing adds six components: Bento Grid, described as an advanced masonry style grid for arranging features, products or content in a card based layout; Feature, a feature section with flexible illustration placement and mockup displays; Social Proof, with masonry layouts, marquee animations and clickable cards; Tabs, with left, top and bottom alignments; Carousel, with multiple variants and customisable navigation; and Testimonials, with grid, carousel and static displays.

The distinction is not cosmetic. A bento grid, a carousel and a masonry social proof section are the layouts that take real effort to get right, and they are exactly the ones a developer is most likely to spend a day on. The open tier is the grid of sections, the pro tier is the difficult arrangement work.

So the honest evaluation is this. If your page needs a hero, a pricing table, a stats row, a FAQ, a call to action and a footer, the open repository covers it, and you own the code afterwards. If your page needs a bento grid of features with illustrations, or a testimonial carousel, you are looking at the commercial product, and the MIT repository is the free sample of the same design language.

The README also says the kit was made for products that need a professional looking landing page for quality-oriented audiences, and lists developer tools, AI powered applications, SaaS products, mobile apps, startup products and technical products as the use cases.

Next 16 and React 19, with a Tailwind 3 branch kept alive

The version matrix in the package manifest is worth reading, because it is specific and because it has one surprising entry.

The runtime dependencies pin Next.js at 16.3.4, React and React DOM at 19.2.8, with `next-themes` at 0.4.6 for theming, `lucide-react` for icons, `tw-animate-css` for the animation utilities, and the Tailwind 4 stack. The dev dependencies carry Tailwind CSS 4.3.3 with the matching PostCSS plugin, ESLint 9 with `eslint-config-next` at the same 16.3.4 version, and two extra ESLint plugins for import sorting and unused imports. Prettier is there with the Tailwind class sorting plugin, so the class order in your files is machine managed.

The entry that stands out is TypeScript, listed at version 6.0.3. That is a major version ahead of the 5.x line that most projects are on, and it is in devDependencies rather than dependencies, which means it is the compiler you type check with rather than a runtime requirement, but it still dictates the toolchain a contributor needs.

The Tailwind 4 upgrade is handled the way a project with existing users should handle it. The README has a note saying Launch UI v2.0 adds full support for Tailwind v4, React 19 and Next.js 16, and that a version supporting Tailwind 3 is still maintained on a separate branch. So there are two lines of the kit, and the Tailwind 3 one lives on its own branch rather than in the main tree.

That arrangement has a cost worth naming. A project still on Tailwind 3 is depending on a branch rather than a release, and the two lines will not receive the same components at the same time.

Running the kit and the tooling that keeps it tidy

The quick start is three steps, and the scripts show the shape of the project.

npm install

npm run dev

Then you open `http://localhost:3000` to view the site. The dev script is worth a look because it opts into Turbopack.

    "dev": "next dev --turbopack",
    "build": "next build",
    "start": "next start",
    "lint": "eslint ."

So the repository is a complete Next.js application that renders a preview of the sections, not just a folder of snippets. That is the difference between a kit and a template: you can browse the live preview at launchuicomponents.com/preview, read the documentation, and then copy the pieces you want into a project of your own rather than adopting this application.

The top-level layout reinforces the structure. There is an `app/` directory for the Next.js routes, `components/` for the sections themselves, `config/` for site data such as navigation and footer links, `lib/` for helpers, `public/` for static assets and `styles/` for global CSS. The `config/` directory is the one to know about, because it is where a copy of the kit keeps the site wide links and labels, and moving a section into your project means moving its configuration with it.

The quality tooling is already wired. The `lint` script runs ESLint with a flat config in `eslint.config.mjs`, and the import sorting plugin means component files are ordered consistently, which is the sort of thing that matters after you have copied forty files into a codebase that did not have a convention.

Version numbers that do not line up

The release history is regular and the repository is not archived, with the last push on 2026-09-04.

v2.9.0 was published on 2026-04-28, v2.10.0 on 2026-06-24 and v2.10.1 on 2026-09-04, which is a cadence of roughly every two months with a patch release at the end.

The oddity is the manifest. The `package.json` says `"name": "launch-ui"` and `"version": "0.1.0"`, and the package is marked private, so it is not published to a registry at all. The git tags are at v2.10.1 while the version field says 0.1.0.

For a copy and paste kit this is not a real problem, because you are taking the source, not installing a dependency, and the version field is never consulted by your build. It only becomes confusing when you try to describe which version of the kit you copied. The tag is the only meaningful reference, and the README does not explain the discrepancy.

The MIT licence covers the repository contents, which is the part that matters for a kit you intend to ship in a commercial product. There is no CLA, no template restriction, and no requirement to keep the attribution in your user interface, only in the distribution of the source.

For a product site, that combination is the appeal. You get sections that look designed rather than assembled, you own and can edit every line, and there is no vendor relationship after the copy. The cost is that you also own every dependency update, and the sections are opinionated, so a visual identity that is not a purple gradient will need real work rather than a colour change.

Editorial conclusion

Launch UI fits a developer launching a product site who wants a presentable hero, pricing table, FAQ and footer in an afternoon rather than a week, and who is happy to own the copied code afterwards. Skip it if the pages you need are the advanced grid, carousel and testimonial layouts, since those sit behind the paid tier, or if you need to stay on Tailwind 3 without tracking a separate branch. Verify first which sections the MIT licensed repository covers, since the README splits the catalogue between the open tier and the Pro version, and check that the Next.js and React versions match the project you are dropping it into.

Frequently asked questions

Official sources

1. launch-ui/launch-ui on GitHub
2. License: MIT
3. Project website
4. README
5. Releases