For the even faster start, it also features Open SaaS - a 100% free and open-source boilerplate starter for React & Node.js. Just clone it and get a working app with auth, billing, Open AI API, user dashboard and more!

When building AI Blog Articles, I decided to get started as fast as possible. So I looked for a free boilerplate and stumbled upon Open SaaS, which used YC-backed Wasp. It is a full-stack React + NodeJS + Prisma that takes 8 hours to get started with.

In addition, their CLI can help you start faster too. By running wasp new, you can get yourself a custom template that fits your needs. For example, if you’re building up a new SaaS, you’ll probably find a fit with OpenSaaS or if you’re creating a more specific solution, an AI code generator can help you start quickly if nothing else fits.

9,500 stars and almost 3 years later, here we are today. Wasp is getting close to entering the elite 10,000 stars club on GitHub, next to the giants of the industry. The framework we started, and developed further with the invaluable feedback from the community, is being used by all kinds of developers - from weekend projects, to startups and top enterprises. Startups made with Wasp have been acquired. I just saw a job ad today on Upwork, where a company is hiring for Open SaaS (an open-source, free boilerplate starter for React & Node.js, powered by Wasp) developers 🤯.

These days, I'm building side projects, like Open SaaS pictured above, and working as a developer relations engineer.

Although some people could consider Wasp’s opinionated stance a negative thing, it is the driver behind Wasp’s numerous full-stack features. With Wasp, starting a full-stack project for a single developer or a small team is much easier, especially if you use one of the pre-made templates or OpenSaaS as your SaaS starter. Because the core of the project is well-defined, it is very easy to get started with a project and potentially, make your own full-stack SaaS in a couple of days! What’s also cool is the fact that most of the pre-existing knowledge of web developers for most of them still applies here, because the technologies that Wasp uses are established.

OpenSaaS – I was curious what the latest starter kit for building out SaaS apps looks like. I wrote my own a whole decade ago github.com/eddywashere/node-stripe-membership-saas.

We’ve launched 6 times on Product Hunt in the last 3 years, won “Top Product” awards (#1 and #5 of the day), and collected over 2,000 upvotes in total. We just finished our sixth launch with Open SaaS - an open-source alternative to $300+ SaaS starters, a week ago.

Hey,

a few people have asked me how we got our [open-source SaaS starter](https://github.com/wasp-lang/open-saas) to the front page of GitHub trending, so I thought I'd share the details:

1. started sharing a funny promo [video on twitter](https://x.com/hot_town/status/1752243248439910626?s=20) and reddit

import { unstable_noStore as noStore } from "next/cache"; import Link from "next/link"; import { CreatePost } from "~/app/_components/create-post"; import { getServerAuthSession } from "~/server/auth"; import { api } from "~/trpc/server"; export default async function Home() { noStore(); const hello = await api.post.hello.query({ text: "from tRPC" }); const session = await getServerAuthSession(); return (

Create T3span> App h1>

First Steps →h3>

Just the basics - Everything you need to know to set up your database and authentication. div> Link>

Documentation →h3>

Learn more about Create T3 App, the libraries it uses, and how to deploy it.div> Link> div>

{hello ? hello.greeting : "Loading tRPC query..."}p>

{session && Logged in as {session.user?.email}span>} p> {session ? "Sign out" : "Sign in"} Link> div> div> div> main> ); } async function CrudShowcase() { const session = await getServerAuthSession(); if (!session?.user) return null; const latestPost = await api.post.getLatest.query(); return (

{latestPost ? (

Your most recent post: {latestPost.name}p> ) : (

You have no posts yet.p> )} div> ); }

I thought he was making stuff up - "t3 stack vs t4 stack". But about 2 minutes in, I realized that I'd heard of a few things that he's talking about so I looked it up and they're real!

I think it's possible everything he's saying is true, more or less. LOL

t3: https://create.t3.gg

t4: https://t4stack.com

We start with a project that was bootstrapped with create-t3-app. For internationalization we use next-intl and set it up as described in the getting started guide. With this initial project setup we can jump into implementing localized error messages.

I used create-t3-app to scaffold the Next.js app, with TypeScript, Prisma, and "app router" enabled in the options. You can also use create-next-app for the job and install Prisma manually.

I agree that the quantity of publicly available code isn't the most reliable indicator of someone's seniority.

My issue with this individual arises from the discrepancy between his public claims of significant expertise in the content he produces. He positions himself as a highly experienced developer, attracting a large following of junior developers who take his advice at face value.

I am trying to collect data points supporting his claims of seniority. For instance, his website prominently features a statement that he is the creator of the T3 Stack. However, a review of the contributor statistics for the T3 Stack (https://github.com/t3-oss/create-t3-app/graphs/contributors)... minimal contributions from him, which raises questions about the validity of his claims.

I would recommend - https://create.t3.gg/

It uses the following, which as of late are pretty well know and common, so you can punch in your problems to stackoverflow, google, or chatgpt and get some pretty good answers.

It uses:

Nextjs (React), typescript, trpc (typescript rpc), auth, tailwind, and Prisma (ORM)

Though of course these could go out of fashion tomorrow, but I don't think the essential idea behind these libs and frameworks are that wacky, unique or unordinary.

Prisma ORM, is a little opinionated, and you could swap it out for Drizzle, which is basically typescript side sugared SQL.

TRPC might be also be a little sticky because it is tied to typescript, this is the tradeoff for the buttery smooth coupling for the fullstack experience. I think there exists a typed-rest solution out there, but haven't used it.

Personal anecdata, I used this stack for a little hobby project and it was FUN.

Open SaaS was built with Typescript, and because it’s a full-stack app, type safety from the back-end to the front-end can be a real lifesaver. I mean, some opinionated stacks have gotten hugely popular on this basis.

Let's start by creating a Next.js application. We will use the T3 stack (TypeScript, TailwindCSS, and Prisma ORM) for this tutorial to skip installing and configuring all the dependencies which is out of the scope of this article. You can find more information about the T3 stack.

https://github.com/t3-oss/create-t3-app

You still would need to add Stripe but there are so many examples publicly available that it should be straight forward