SaasRock - The SaaS building framework

@avalonxt Thank you :D... Yes. You have 3 main parts: front pages (for anon users and marketing), /app/:tenant pages, and /admin pages. I've built 5 different type of B2B apps (you can see them at /showcase). The last SaaS I built is Indexer.so, a 3-day project (see it at /saas-templates/google-page-indexer). And I'm currently working on a Directory Listing Builder template/youtube-series, and my focus this year is to release as many SaaS templates as possible, covering different SaaS types.

@avalonxt @alexandromtzg the showcase is super helpful! Subscribed to your YouTube for more content :) SaaSRock is a really powerful concept and great for PH community - excited to play around with this and I dig the positioning around MVP'ing something as a use case.

@zama_khan_mohammed 1) SaaS templates, 2) building SaaS apps of my own will improve the codebase, 3) custom subdomains/domains, 4) Vercel, Cloudflare and more deployment provider docs (now with Vite), 5) more built-in features like Help Desk, 6) resolve/close the current 80 open issues 7) AI everywhere 8) … time is what I need!

@alex_dulub The most difficult one for me was the Entity Builder, it started as a simple feature for a Expense Request app I was building and it required custom properties. I thought, why not built a whole autogenerated list, new, edit, overview, share, comments... forms? and while I'm at it, autogenerated API and API docs, with relationships (one-to-one, one-to-many) integrated. Turned out to be a super complex no-code "form" builder for app tenants. But I love it! Even though no-code hits a wall at a certain point, I move quickly (watch my latest Directory Listing Builder where I use it) Thanks for the support :D

@10xmarketer By throwing more RAM to your server 😅! On a serious note, 1) saasrock has a build-in metrics tracker to analyze performance in your routes/functions/actions, 2) everything that can be cached will be cached eventually, 3) I'm already exploring a true multi-tenant architecture (database-per-tenant). I have a few very succesful clients with over 1M API requests/month, so there are frequent updates, as long as burnout doesn't get to me that is 😬. 1. Built-in Help Desk and Affiliates 2. More SaaS templates to cover different SaaS types 3. More AI 4. More Youtube tutorials I'm open to anything as long as it's what the majority wants. For example, I was about this close 🤏 to migrate everything from Prisma to Drizzle ORM, but more than 50% voted to stick with Prisma. And everyone screamed to get shadcn/ui integrated, so I managed to put it in this 1.0 release.

@sara_with_h Great Sarah! You're also welcomed to join the discord server to clear any questions you may have.

@ahmad_sadeddin Thanks! I have not touched SSO although it was on my plans since the beginning (2 years ago), until I need it in one of my saas apps I’ll built it! As for Oauth GitHub and Google are implemented, but adding a new provider it’s fairly easy with the remix-auth package.

@alexandromtzg makes total sense! Thanks :)

@productpie Thank you :D 1. No security tests! 2. You'll get access to the repository (depending on the edition) and get 1.x free bug fixes / updates 3. I would say you need to use it full-time at least a week to get a grasp of it. You can see how I build things in the youtube channel youtube.com/@saasrock or follow one of these "tutorials": https://saasrock.com/build-marke... or https://saasrock.com/docs/articl.... 4. None, I was going to do Clean Architecture (similar to my previous boilerplate NetcoreSaas), but ended up with no architecture. 5. I haven't deployed to AWS but SST is on my list for Deployment providers to make a tutorial on.

@saasrock @alexandromtzg thanks for the response! Looking forward to the tutorial on SST deployment. Just One week of lift is awesome! That speed is important for us. Curious to learn more about the no architecture choice. And, could you help on the question regarding coding standards.

@saasrock @productpie The no architecture thing was not really a choice, it was a consequence of shipping features as fast as possible, see the full changelog at https://saasrock.com/changelog. I've been wanting to do refactoring to improve at least folder structure, but I would have launched in another year haha. So no coding or architecture standards. But you can see the overall code structure in https://github.com/AlexandroMtzG... (which is saasrock v0.0.1), my way of coding I mean.

@ckluis Thanks for your quality advice Chris! Now that 1.0 is out, we might want to do a Next.js edition 😛… the Build, Market, and Manage vision you suggested cleared the path for a top-tier SaaS building solution 👌