Intro

<aside> ⭐ I'm very proud to announce that Saasify's open source GitHub repo has just hit 600 stars.

</aside>

This is a small but important milestone for us that has taken over a year of consistent, daily work including contributions across over a dozen related projects in the more general JS and TS communities.

I'm a big believer in the power of open source and can say from experience that a lot of people underestimate the second & third-order effects of building a strong open source community.

With all this in mind, I thought this would be the perfect time to share some general thoughts on our approach to open source.

Open Core

Saasify is what's known as an open core company. This just means that some of our code is open source, and some of it is closed source.

Our platform's codebase is split into two monorepos, one for our publicly-facing, MIT-licensed open source work, and one that's private, for proprietary closed source work.

Saasify Open Source

• User-facing parts of the platform (e.g., our Node.js CLI, React component library, marketing website / admin webapp, JS client API, etc)
• All platform documentation (source and generated docs)
• Lots of generally useful functionality that other open source projects and companies may benefit from (OpenAPI utilities, FaaS utilities, badge generator powered by headless Chrome, etc)
• 20 or so example projects showcasing different use cases for Saasify
• A standalone project for Functional TypeScript which transforms normal TS functions (and jsdoc-annotated JS functions) into JSON Schemas and OpenAPI specs

Saasify Closed Source

• Our platform's main backend API
• Our API gateway for proxying FaaS requests
• Various serverless functions whose business logic is built on top of OSS packages from Saasify's public repo
• The template-based SaaS web client (most of the React components that comprise this webapp are from our open source react-saasify package)