Accelerate web development with your own Turborepo codebase, featuring a design system, landing page components, multilingual static sites (blog, docs), and more. Perfect for solo makers and tech teams. Say goodbye to setup fatigue and hello to rapid launches!
Hey Product Hunters 🙋🏻♂️
I'm Jakub, the solo maker behind CodebaseUp, a project all about simplifying web development and accelerating your journey from idea to launch.
It was born from my own startup journey. I've been in your shoes and spent endless hours tackling web development challenges so you don't have to.
Here's why it matters:
🚀 Rapid Time to Launch
You can go from idea to production-ready in minutes, not days or weeks.
📦 Comprehensive Boilerplate
It's a Turborepo codebase and comes with modules that address major use cases. It features a Next.js app (v14 App Router), a design system with landing page components, blog and documentation sites, a database, authentication, internationalization, emailing, forms with validations, file uploads, and more. I update it daily based on feedback and whenever I see fit from my other projects. You own the code, with no vendor lock-in.
💰 Zero Infrastructure Costs
All built-in modules start with free tiers, and you only pay as you validate and grow.
🙌 Free Version Available
CodebaseUp Core is a public repository containing a subset of Pro modules. It can still get you far. Just clone it, install dependencies, and run localhost.
git clone git@github.com:jhavej/codebaseup-core.gitpnpm installpnpm run dev
🤓 1-on-1 Consultation Included
I'm here to help! Schedule a personalized session to dive into your project and codebase.
🎯 For Devs at All Skill Levels
Solo makers will value guides and clean code that doesn't need comments. Tech teams will benefit from Turborepo modularity and performance.
As a thank-you for joining this launch, enjoy a special offer for our Product Hunt community. Use coupon code PH100 at checkout to get $100 off.
I'd love to hear your feedback.
Jakub
Congrats on the launch! Even if it's yet another template package being launched 🤓 A have a few questions though:
- Does it currently support payments? You mention it's included in the pricing page, but in the features section you say "Soon" (just one of the many examples where there's this inconsistency)
- Which service is it using for infrastructure (e.g. hosting)? Does it use serverless functions or traditional server?
- Does it automate infrastructure creation, configuration and deployment too?
- Does it include CI/CD automation?
- Do we get updates over time?
- Any plans to support other tech stacks other than nextjs?
- Can I host using my custom domain?
- Does it set up DNS? e.g. my custom domain for the landing page, e.g. app.example.com for my app, blog.example.com for my blog, etc...?
@rogeroba Thanks, Roger! 🤓
Q1: Does it currently support payments?
The Stripe integration is currently in progress, and I plan to have it delivered this Friday. I've just fixed the inconsistency on the pricing page – thanks for bringing it to my attention.
Q2: Hosting?
I recommend using Vercel (and therefore serverless) for a seamless experience. The main app is built with Next.js (v14, App Router), and it can also be deployed outside Vercel, like on Render, if that's your preference.
Q3: Does it automate infrastructure creation, configuration, and deployment? Does it include CI/CD automation?
Yes, it certainly does. It has been tested on Vercel. You can simply run 'git push' and it will be deployed. Each separate branch comes with its own preview deployments. To ensure reliability, all tests (currently Typescript/ESLint) must pass; otherwise, the deployment gets canceled, keeping you safe.
Q4: Do we get updates over time?
Absolutely! I'm building it in public on Twitter/X, and there's a member-only project roadmap on GitHub. Even though I'm the sole developer, I create Pull Requests for everything, so members can see and contribute to the progress.
Q5: Any plans to support other tech stacks besides Next.js?
Yes, I'm also a fan of Remix and Python/Django, which are part of my stack. What would you like me to consider?
Q6: Can I host using my custom domain?
Yes, you can. Just deploy the codebase to Vercel and add your custom domain in a few clicks.
Q7: Does it set up DNS? For example, my custom domain for the landing page, e.g., app.example.com for my app, blog.example.com for my blog, etc...?
Absolutely, one of the advantages of the built-in Turborepo modularity is that it allows you to separate packages and apps. This means apps can be deployed separately on their own domains or subdomains.
@jhavej thanks for the thorough answers! Everything is clear now, thanks! As for the diff tech stacks, I'm a fan of Ruby on Rails + Next.js combo, would you consider that?
What do you mean with built-in turborepo modularity, btw? Would I configure it directly on Vercel, like "folder 'blog' in my monorepo should be deployed to 'blog.example.com'"?
Lastly, does it have built-in support to multiple envs (e.g. dev and prod — dev.example.com VS example.com)? Or would I have to configure that on my own?
@rogeroba Let's consider a scenario where you have three apps within the monorepo (app/web, app/blog, app/docs). All these apps utilize functionalities from shared packages, such as packages/database and packages/ui. When using Vercel, you can create separate projects for each app, all linked to the same repository. You only need to specify a root path (e.g., app/web, app/blog, etc.). Vercel is fully compatible with Turborepo, so deployments work seamlessly out of the box.
Each Vercel project offers independent configuration, allowing you to set custom (sub)domains and environment variables for various environments (production, preview, and development).
In a nutshell, you set up your environment variables and go live.
If purchasing CodebaseUp Pro isn't the right fit for you, consider trying CodebaseUp Core. It's a public repository that includes a subset of Pro modules, and it's still highly capable.
https://github.com/jhavej/codeba...
Regarding your tech stack, it seems you use RoR for API endpoints and the database, along with Next.js for the frontend, right? Have you ever thought about transitioning entirely to Next.js?
Thanks, Roger, I appreciate your feedback.
@jhavej got it, that sounds awesome! Thanks for linking me to a free version of the Pro package, I'll check it out 😊
That's right, RoR for API and Next.js for FE. I have considered going full Next.js, but the thing is that I already have a BE in RoR, so it would require a full migration, and on top of that I'm already quite comfortable (read: productive) with RoR and its stack, so those were the two main reasons I haven't made the switch. But I'll reconsider it 😅
Thanks for taking the time to share your knowledge and explaining the product better 🙏 best of luck on your sales! Keep shipping! 🚀
@rogeroba You're most welcome, Roger. You gave me plenty of ideas on what I should include in the documentation for CodebaseUp, thanks.
I used to develop SW the same way - Django for BE, and pure React.js for FE. Then I discovered Next.js & Vercel and its convenience... I truly value the easy way to end-to-end type safety and the automated CI/CD.
Thanks and let's ship things fast! 🚀
CodebaseUp
Statused
CodebaseUp
Statused
CodebaseUp
Statused
CodebaseUp
CodebaseUp