HN user

hot_town

17 karma

turtles are just shielded toads.

DevRel at https://wasp.sh

Posts10
Comments22
View on HN
[dead] 12 months ago

I launched Open SaaS about a year and a half ago and surprisingly it’s become the most popular free SaaS boilerplate starter on github (https://github.com/wasp/open-saas).

After 2 years of work total, I’m pleased to launch what I’m calling “Open SaaS v2.0”.

Here’s a breakdown of all the features and updates I’ve made to it over time:

*New Big, Shiny Things for v2.0*

- Complete redesign with Shadcn UI for a modern and consistent look (themeability coming soon...). - Script that autogenerates an LLM-friendly version of the documentation https://docs.opensaas.sh/llms-full.txt. - Added Zod validation for webhook payloads.

*Main Features*

- 100% open-source repo w/ a focus on open-source tools when possible. - Auth that you own (no 3rd party services): email, google, github, discord... - Full Payments Integration: easily swap out Stripe for Lemon Squeezy or Polar (coming soon!). - Full-stack typesafety on top of React, NodeJS, Prisma. - Admin dashboard w/ revenue and site analytics (Google or Plausible) - OpenAI API & AWS S3 integrations.

*New Features*

- Added Lemon Squeezy as payment provider option (Polar and Paddle in the works!). - Enhanced file uploads with progress bars and validation. - Added a generic cookie consent banner (if you need one). - Integrated Playwright for end-to-end testing. - Added a 404 page.

*Fixes & Improvements*

- Upgraded Wasp (React/NodeJS/Postgres) framework to v0.17.0. - Upgraded AWS and OpenAI SDKs to their newest-ish versions. - Tightened S3 CORS configuration for better security. - Improved payment webhook logic. - Made UI components more consistent (e.g., controlled switches). - Fixed various styling issues, including dark mode inconsistencies. - Improved error handling and validation across the app.

*Refactoring & Code Organization*

- Major "vertical reorganization" of the codebase for improved modularity (auth, payments, users, file-upload). - Significant refactoring of user management pages and queries. - Refactored to use prisma transactions for safer DB mutations. - Cleaned up and simplified various parts of the codebase.

*Docs & Content*

- Updated documentation for deployment, installation, and new features. - Added a customization checklist.

There have been a slew of paid SaaS boilerplate starters popping up since we started, but Open SaaS will stay free and open-source forever.

So if you're interested in becoming a contributor, or just wanna add a suggestion to the roadmap, feel free to create an issue https://github.com/wasp-lang/open-saas/issues.

I launched Open SaaS about a year and a half ago and surprisingly it’s become the most popular free SaaS boilerplate starter on github (https://github.com/wasp/open-saas).

After 2 years of work total, I’m pleased to launch what I’m calling “Open SaaS v2.0”.

Here’s a breakdown of all the features and updates I’ve made to it over time:

* New Big, Shiny Things for v2.0 *

- Complete redesign with Shadcn UI for a modern and consistent look (themeability coming soon...). - Script that autogenerates an LLM-friendly version of the documentation https://docs.opensaas.sh/llms-full.txt. - Added Zod validation for webhook payloads.

* Main Features *

- 100% open-source repo w/ a focus on open-source tools when possible. - Auth that you own (no 3rd party services): email, google, github, discord... - Full Payments Integration: easily swap out Stripe for Lemon Squeezy or Polar (coming soon!). - Full-stack typesafety on top of React, NodeJS, Prisma. - Admin dashboard w/ revenue and site analytics (Google or Plausible) - OpenAI API & AWS S3 integrations.

* New Features*

- Added Lemon Squeezy as payment provider option (Polar and Paddle in the works!). - Enhanced file uploads with progress bars and validation. - Added a generic cookie consent banner (if you need one). - Integrated Playwright for end-to-end testing. - Added a 404 page.

* Fixes & Improvements*

- Upgraded Wasp (React/NodeJS/Postgres) framework to v0.17.0. - Upgraded AWS and OpenAI SDKs to their newest-ish versions. - Tightened S3 CORS configuration for better security. - Improved payment webhook logic. - Made UI components more consistent (e.g., controlled switches). - Fixed various styling issues, including dark mode inconsistencies. - Improved error handling and validation across the app.

* Refactoring & Code Organization*

- Major "vertical reorganization" of the codebase for improved modularity (auth, payments, users, file-upload). - Significant refactoring of user management pages and queries. - Refactored to use prisma transactions for safer DB mutations. - Cleaned up and simplified various parts of the codebase.

* Docs & Content*

- Updated documentation for deployment, installation, and new features. - Added a customization checklist.

There have been a slew of paid SaaS boilerplate starters popping up since we started, but Open SaaS will stay free and open-source forever.

So if you’re interested in becoming a contributor, or just wanna add a suggestion to the roadmap, feel free to create an issue https://github.com/wasp-lang/open-saas/issues.

Hey. Creator and maintainer of Open SaaS here.

There may be some config steps, but everything is well documented https://docs.opensaas.sh/, and we have simple commands like `wasp db start` to get a local postgres instance running and connected to your app.

Here's a video walkthrough on how to get started: https://x.com/hot_town/status/1833449116145267183

If you have any questions, feel free to jump into our discord and we'll be happy to help: https://discord.gg/aCamt5wCpS

Hey. Vince, DevRel @ Wasp here.

The cool part about Wasp is that it allows you to build full-stack apps with minimal effort, so that you can spend the majority of your time actually writing React and Prisma, and not configuring servers, routes, authentication, and the like. Just by defining your Entities and the necessary read & write operations in your Wasp file, Wasp is able to build a NodeJS server based on industry best-practices, create your Auth "plumbing", build your API, protect pages, etc.

You're free to define the logic as you see fit, without the grunt work of setting up services from scratch.