Router

Router.so is an open-source, headless form handling and lead routing platform designed for marketing-minded developers who need a flexible, self-hostable solution for managing form submissions and lead distribution. It is an open source template in the shadcn.io collection of 215.

Router.so is made by Routerso, an independent developer; shadcn.io lists it but did not make it. Routerso has 1 template in the collection, and the author's page lists them.

The listing tags Router.so with Next.js, React, Tailwind and Drizzle ORM. Those are its categories, not a dependency list: the exact packages and versions are in the repository's package.json.

Yes. The Router.so page embeds its live demo from router.so, and links to it so you can open the real deployment before you clone.

The Router.so listing was last updated on October 8, 2025. That date is the listing's, not the repository's: check the repository's commits for recent activity.

Clone the repository (git clone https://github.com/routerso/router), then follow the README. The Router.so page shows the usual steps and a terminal block with the commands to copy.

Install dependencies with npm install or pnpm install, then run npm run dev. The README in the Router.so repository says which package manager and environment variables it needs.

No. Router.so is cloned from its own GitHub repository, so shadcn.io isn't involved. Browsing the page and its live demo need no account either; Pro adds the premium templates, the blocks and the MCP server.

Router.so is tagged Next.js, so it deploys wherever a Next.js app does, such as Vercel, a Node.js server or a container. Its README may add steps for its own services.

The Router.so listing doesn't record a license. Check the LICENSE file in its repository (https://github.com/routerso/router), and ask the author if there isn't one.

That depends on Router.so's license in its repository, which shadcn.io does not set. Read the LICENSE file before you use it in a client or paid project, and ask the author if it is unclear.

Attribution follows Router.so's license. Many permissive licenses ask you to keep the copyright notice and license text in your copy; its LICENSE file says exactly what.

No. The Pro license covers shadcn.io's own Pro code, blocks and premium templates. Router.so is the author's project, under the terms in its repository.

Routerso supports Router.so, through its GitHub repository: read the docs, open an issue or look for discussions. shadcn.io does not maintain it.

Yes. Once you clone it, Router.so is your own code: change the theme, add pages and connect your backend. It uses shadcn/ui, so you can also add more components the same way.

Yes. Components are free with a free account and the blocks are in Pro; both are copied into your project with the shadcn CLI. Check that Router.so uses Tailwind CSS and the shadcn/ui setup (a components.json) before you add them, and pick the base library your project already uses.

Yes, with Pro. The shadcn.io MCP server's search_templates tool finds templates by what they are, and returns each one's repository and live demo, so your editor can set up Router.so for you. Your files stay on your machine.

The collection has 21 other open source Drizzle ORM templates like Router.so, shown at the foot of its page with the ones sharing most categories first. All of them are at /template/category/drizzle-orm.

Routerso has no other templates in the collection.

Yes. The 14 premium templates (Solaris, Reframe Labs, Spherule and Max and more) are built by shadcn.io and come with every Pro plan, if you want maintained code with a design file.