
Beste UI
Production-ready sections, pieces and primitives for shadcn/ui and Tailwind CSS.
Install one with a command, and the code is yours.
· · ·
Install
One command, no package to add, no provider to wrap your app in:
The files land in your project. Edit them, delete half of them, rename the props. There is no upgrade path to fight later, because there is nothing to upgrade.
Works the same for every free item in this repository, by name:
What is in here
The distinction matters when you compose them. A block is a section you drop on a page. A piece is an asset that belongs inside one. A component is a primitive you build with.
Blocks by category
Plus navbar, FAQ, settings, fitness, devtools and terminal sections. .
Built for agents, not just for people
Every page in this repository is readable by a model, and the registry is addressable by one:
- MCP server. Point your editor at
https://ui.beste.co/api/mcpand it can search the catalogue, read a section's source, and hand you the install command. . - Markdown content negotiation. Send
Accept: text/markdownto any page and you get markdown instead of HTML. llms.txt. A machine-readable index of the whole catalogue at and .- Semantic search. Describe the UI you want in a sentence rather than guessing at a name.
Theming
Sections read from CSS variables, so they inherit whatever theme you already have. The site ships 96 of them and a font picker, and the preview updates live so you can see a section in your palette before installing it.
Nothing is hardcoded to a brand colour. If your --primary changes, every
installed section follows.
Running it locally
No environment variables, no database, no account system. Everything you can see in this repository, you can run.
Repository layout
Each item carries its own metadata and README, which is what the site, the search index and the MCP server all read. Adding a section means adding a directory, not editing a manifest.
What is here, and what is not
This repository holds every free item in the catalogue, the site that renders them, and the registry that serves them.
The Pro catalogue (over a thousand more sections), accounts, plans and the Base UI variant of the registry live on . Links in this build point there rather than pretending those pages are missing.
This repository is generated
It is built automatically from a private source repository and synced on every release. Manual edits here will be overwritten.
That does not make contributions unwelcome, it just changes the path they take. See .
Security
Found something? Please do not open a public issue. See .
License
MIT. Use them at work, in client projects, in things you sell. See .
Also from us: beste.co
Every section here is drawn by hand, one at a time. The same ones are the building material for , a website builder.
The difference is not how much craft goes into them, it is what you walk away with. Here you take the source, and it is yours to change. There you take a site that is live on a domain, built from these same sections, without standing up a repository first.
· ·