Gregistry
Browse
A small, personal shadcn registry

Components I built,
ready for yours.

A handful of shadcn-compatible blocks and components I use across my own projects. Add one to yours with a single command — the source lands in your repo, yours to edit and own.

Browse components
4 components · MIT · free forever
~/your-appzsh
➜ ~/your-app $ npx shadcn add hero-centered-mock
✓ checking registry · gregistry.dev
✓ resolving hero-centered-mock
✓ adding 3 files · 2 peers
+ components/heroes/hero-centered-mock.tsx
+ components/ui/button.tsx
+ components/ui/input.tsx
✓ done in 1.4s
➜ ~/your-app $ ▊
One install command
Add a component with `npx shadcn add` — peer deps come along.
Source you own
TSX lands in your repo. Edit, restyle, fork — it's just code.
shadcn-compatible
Drops into any shadcn project. Same conventions, same aliases.
Free & MIT
No accounts, no quotas. Take whatever's useful and run.
How it works

Browse · Install · Own.

Same flow as any shadcn registry. Find a component, add it with one command, and the source lives in your repo from then on.

1Browse

Pick a component

Scroll the showcase below. Toggle preview / source. Each item lists its peer deps so you know what comes with it.

// what you get
name: "hero-centered-mock"
type: "block"
peers: ["button", "input"]
2Install

One shadcn command

The standard shadcn CLI fetches the component from this registry and writes the files into your project. No config to wire up.

$ npx shadcn add ...→ files
peers resolved automatically
writes to components/
3Own

It's your code now

No package, no abstraction. The TSX is in your repo — edit it, restyle it, delete what you don't need.

+ components/heroes/hero-centered-mock.tsx
+ components/ui/button.tsx
✓ yours to edit
The collection

4 components, ready to install.

Toggle between the rendered preview and the source you'll actually own. Copy the install command on the right.

Hero 1
hero-1 · block · 8.4 KB
See what's new in v2.4.0

Supercharged
component registry

Build, version, and ship your own shadcn-compatible components from one place. Install across every project with a single command — your design system, distributed.

Continue with GitHub
4,210 components published this week
Search components…
Todo 4
···
#5
2026 KPI report
finance
#40
Improve Lighthouse score
enhancement
#33
Send email when user subscribes
featureMarketing spring
#36
Update landing page sponsors & testimonials
enhancement
In Progress 4
···
#8
Write 2026 roadmap
#10
January 2026 Newsletter
marketingMarketing springMar 31
#41
Blog article on how we designed our website
marketingMarketing spring
#26
chore: code improvement
enhancementCrush bugs sprint
In Review 3
···
#42
Video storyboard
videoMarketing springJan 17
#9
Responsive menu has too much padding
#23bugCrush bugs sprint
#13
Improve "Button" component
#28enhancement
Done 6
···
#14
Video for VueJS Amsterdam
videoFeb 9
#39
Improve documentation
documentation
#20
Update icons library
design
#18
Update GitHub readme
marketing
#38
Release new website
feature
#19
Create design system
design
peers: lucide-react
Open standalone preview →
License
MIT
Type
block
Peer deps
lucide-react
FAQ

Questions, answered.

What is this, exactly?
A small, personal collection of shadcn-compatible components I built for my own projects. The registry is public so anyone can install the same components into theirs — no accounts, no signup.
Do I need shadcn/ui to use it?
It works best inside a shadcn project, since some components depend on shadcn primitives like `button` and `input`. The source is plain React + Tailwind, so you can adapt it to other setups with a bit of work.
How do I install a component?
Run `npx shadcn@latest add https://gregistry.dev/r/<name>.json` — the .tsx files land in your repo. Each component above shows its exact install command.
Why a registry instead of a package?
Because you get the source, not a black-box dependency. The TSX is in your repo after install — edit it, fork it, restyle it, delete what you don't use. That's the whole shadcn philosophy.
Will more components be added?
Yes — I add new ones as I build them for my own work. No schedule, no roadmap. If you want something specific, open an issue on GitHub.
Is it free?
Yes. MIT licensed, public, no accounts. Take whatever you find useful.
Get started

Three commands to your first block.

1STEP
Init shadcn
Skip if your project already uses shadcn. Otherwise this wires up your aliases.
$ npx shadcn@latest init
2STEP
Pick a component
Each one shows its install command and peer deps before you commit.
$ scroll up to the showcase
3STEP
Add it
Files land in your repo. Edit freely — they're yours now.
$ npx shadcn@latest add https://gregistry.dev/r/hero-1.json