# RepCN Repository builder open-source tool > Source: > Published: 2026-07-14 16:17:26+00:00 Convert React code into a deployed project with a shareable URL Hello and welcome to the new blog Our last blog was about building iHateReading and earning from a content platform. While running iHateReading, I've personally needed so many tools, and luckily, in the age of AI, I can quickly build tools for internal work. First, let me explain with an example: running any platform needs tools for different types of work, tools for writing, tools for content management, tools for user management, tools for assets creation, tools for research, etc. Each tool has a purpose to serve and mainly reduce the execution time if done manually; one good example is creating banner images for each blog. I write almost every day, and I need to put a cool, catchy title on almost every blog. Each blog banner image creation is a process with tasks; if you are an engineer, you can understand the pain!! But I found that I've had to stumble upon Canvas or other tools mainly for creating banners. I've figured out that making assets is not important; having examples of assets, just like canvas templates, is a more accurate solution to my problem. The first month was building the basic tool, and then later on, adding the templates for various categories was my decided plan, and I ended up making a simple canva alternative tool, [kixi.app](http://kixi.app) Building an internal tool will take time, but if that tool is reducing your development debt and saving time to give better output, then it always works. Another example is our FREE open-source internal writing app, which works offline, is simple, easy to use, has a dark/light theme, is open-source and shows a graph network connection between all the created notes, Check Github: [https://github.com/shreyvijayvargiya/opennote](https://github.com/shreyvijayvargiya/opennote) Why do we need these tools in times of Notion and Apple Notes? The concept is simple for internal use, no payment issues, no authentication issues, no data transfer issues. The choice is yours if needed and can reduce costs and save time by building that internal tool for yourself and maybe that tool helps others, for example, React CRM SAAS template I made for my small SAAS businesses and ended up adding more pages 60 pages in total with classic theme editor and luckily it has helped 10+ businesses worldwide and my current client need CRM based on our React CRM template. I often rely on the concept of easing my own work, making it a more fun job to do and then figuring out how to monetise it. In today's blog, we will be discussing another open-source tool, the idea of sharing a single React code by deploying it on a custom domain or a demo pseudo domain. But first, I want to explain the problem statement: Every time I went to Claude and asked for a code, it gave me either HTML or React code. Claude can render HTML easily inside a browser, and React too, but not NextJS or Vite, and TanStack apps; those framework codebases cannot be rendered and previewed inside Claude, and Claude needs React rendering and a building engine under the hood to make it possible. Another problem I've faced is that all the React code written by Claude can only be shared via Artefacts, not as a URL or domain, or even a subdomain. For example, paste the below prompt in Claude code ``` Give me a classic animated hero section with an animated background using Tailwind CSS, React lucide-react for icons and use Framer Motion for animation, give me a single-file React code component ``` The Claude will return the single-file React code component. Why only a single file? I'll explain it later on. Once we got the code, I couldn't share this code with others to view inside the browser, nor could I share the code output preview to view; all they needed was a Claude for the same. Here comes RepCN to the rescue, which sits nicely between Claude and shareable React code for designers and developers. Imagine you can create Nextjs or Vite, or Tanstack repository using that single React code. Push the repository to Github creating a new repository on Github and finally deploy that repository onto Vercel to get your own URL of {project-name}.[vercel.app](http://vercel.app) **How RepCN can help** One of the most important reasons I need RepCN is to create a new repository based on a single React code with all packages installed. The default packages it includes are as follows But the above packages can be changed, and you can choose Vite or Tanstack as a framework, shadcn as a UI library with JS or TS supporting both. RepCN is open-source and built using Nextjs and React No authentication needed No server-side API is required No databases are used in making it Completely FREE and Open-Source Give it a try on a website: [https://repcn.buildsaas.dev/](https://repcn.buildsaas.dev/) Fetch Github repository: [https://github.com/shreyvijayvargiya/repcn](https://github.com/shreyvijayvargiya/repcn) That would be enough for today, see you in the next one Cheers Shrey One last thing, my last release template was Tooldir: Directory creating starterkit with complete payment and authentication integrated, check [tooldir.buildsaas.dev](https://www.tooldir.buildsaas.dev)