OSS Alternatives to SaaS: What Technical Founders Are Actually Shipping

There's a GitHub repo called awesome-oss-alternatives, maintained by Runa Capital, that tracks open-source startups organized by the SaaS product they compete with. It has 18.9k stars, 1k forks, and 110 contributors — which makes it one of the most-watched signals for where technical builders are spending their energy.

The list has a specific bar for inclusion: the company must be for-profit, founded in the last 10 years, have a well-known closed-source competitor, and the repo must have 100+ GitHub stars. That filter makes it genuinely useful — it's not a list of side projects, it's a list of businesses that are fighting for real market share.

Here's a breakdown of what the list reveals — organized by category density, traction signals, and what it means for founders deciding where to build.

The Categories With the Most Competition

Some categories have attracted so many OSS entrants that the competitive dynamics have shifted. These aren't wide-open opportunities — they're crowded markets where differentiation is the only lever.

Auth & SSO has more OSS entrants than any other category — Keycloak, Ory, Supertokens, FusionAuth, Zitadel, BoxyHQ, Hanko, Cerbos, OPAL, Oso, and Warrant are all competing for developer mindshare in roughly the same space. That's not a gap in the market. That's a market that has already been heavily colonized.

The notetaking category tells a similar story. AppFlowy, Outline, Logseq, Joplin, Notesnook, Trilium, Bangle.io, Boost Note, Dendron, Athens Research, Notabase — all Notion or Roam alternatives, all with active GitHub repos, all fighting for the same knowledge worker.

The Standout Products by Star Count

Raw star count is an imperfect signal, but when a project has dramatically more stars than its category peers, it's usually because it solved the problem clearly enough that developers recommended it to other developers without being asked.

What these projects share: they're not thin wrappers around an API. Each one is a complete platform that a developer can deploy, own, and extend. The star counts reflect not just interest but trust — developers recommend these to colleagues because the project has proven it can run in production.

The Categories That Are Underdeveloped

The more interesting signal isn't where the list is crowded. It's where the list is thin — one or two entrants, a clear incumbent, and a gap that hasn't been filled yet.

Cal.com is a useful case study here. It's the only serious OSS scheduling infrastructure play on the list, which means it's been able to build a defensible position — not because the problem is easy, but because nobody else showed up to compete in the same way. That's a different kind of moat than being the best in a crowded field.

Three Patterns That Define the Best OSS Businesses

Looking across the full list, the projects that have built the most durable positions share three characteristics. These aren't guarantees — they're filters.

Infrastructure, not application. The strongest projects in the list — Supabase, Grafana, Meilisearch, n8n, Keycloak — are infrastructure that developers embed into their own products. They're not competing for end users; they're competing for developer trust. Once embedded, they're extremely sticky. Application-layer OSS (task managers, note-takers, email clients) has much higher churn because the switching cost is low.

The commercial open-source model is the business model. The list criteria requires for-profit companies, which means all of these projects are figuring out how to monetize openness. The pattern that works: self-hosted free, cloud-managed paid. The projects that struggle are the ones that try to make the OSS version deliberately crippled — developers notice and the community trust erodes fast.

Specificity beats breadth. PostHog (product analytics) is more defensible than a generic "analytics" tool. Lago (billing API) is more defensible than a generic "payments" tool. The more precisely a project names the problem it solves, the more likely a developer with that exact problem will find it, star it, and eventually pay for the managed version.

What This Means for Technical Founders Building Now

The list is a map of where technical founders have already gone. The implication for someone building today isn't to copy what's on the list — it's to notice the structure.

The Repo Itself as a Signal

The metadata on the repo is worth reading as carefully as the content. Last updated September 2025. 409 commits over 4 years. 110 contributors. The most recent commit added OpenStatus, a synthetic monitoring platform.

That update cadence — steady, community-maintained, not a rapid burst — is a signal that the OSS-vs-SaaS dynamic is still active but maturing. The explosion of new entrants that happened post-2020 has slowed. The list is no longer growing as fast as it was, which means the "easy" categories have been colonized and the remaining opportunities require more specific insight.

For a technical founder deciding where to build, the list is most useful not as an exhaustive catalog but as a calibration tool: if your idea maps to a dense category, your go-to-market strategy needs to be fundamentally different from if you're entering a thin one. Same code quality, different everything else.