Everyone figured open source would just keep winning — free code for all, clouds feasting on our labor without a dime back. But here’s source-available crashing the party, barely-open licenses that let you peek but not touch. Redis kicked it off loud in 2023, and now it’s a flood.
CockroachDB. ScyllaDB. Even Sentry. They’re all flipping the script.
And yeah, it changes everything. Solo devs built empires on trust; now it’s moats around the code.
Look, the big three — AWS, GCP, Azure — they’ve been freeloading forever. Fork your project, slap it on their cloud, rake in billions. No contributions. Redis screamed ‘enough’ and went source-available. Fair play? Maybe.
But.
This sprawls into a mess — projects listing tantalizing GitHub repos, but core features? Locked behind SaaS paywalls. SpacetimeDB’s self-hosted version? One node only. Marketed magic vanishes.
Why Are Databases Ditching Open Source?
Databases first. Always databases. Redis in March 2023. SpacetimeDB August same year. Terraform — wait, infra — but then CockroachDB November 2024, ScyllaDB February 2025. Bear blogging in November 2025? Pattern’s clear.
Data’s gold. Clouds want it. Devs built horizontal scaling dreams — my hobby too, tinkering distributed systems sans vendor lock. Now? Peek at source-available code, but deploy? Pray it scales without their cloud.
It seems more and more projects move away from open-source to commercial source-available models. And I can see the benefit of course… When everything is open-source it is so easy to take advantage for the «big three».
That’s the Reddit spark. Spot on about freeloaders. But here’s my twist — this reeks of the 90s shareware era. Remember? Devs released crippled binaries, full version for $29.95. Innovation starved; users bolted to Netscape or Microsoft. Source-available? Modern shareware, dressed in GitHub sheep’s clothing.
Punchy truth: it’s not protection. It’s paranoia. Protects from competition, sure — your fork won’t steal thunder. But solo devs? We’re screwed. Can’t vet licenses pre-download. Is it OSI-approved? Or Elastic’s SSPL trap?
Short para. Bad.
And the hype. Companies spin ‘source-available’ like a feature. ‘See our genius code! Just don’t use it fully.’ PR fluff — call it out. MongoDB 2018, Elastic 2021; Redis lit the fuse. Postgres next? God forbid.
Is Source-Available Bad for Solo Devs?
Damn right it is. Imagine forking Sentry for your error tracking side gig. Nope. License says ‘no commercial hosting without us.’ Fine for enterprises? They pay anyway. Us indies? Hunt alternatives, waste weeks.
Or SpacetimeDB — video screams distributed glory. GitHub? Single node toy. Vendor lock baked in. That’s not open. That’s bait-and-switch.
Worse: fragmentation. Open source thrived on remixing — Apache Kafka on RocksDB stacks. Now? License roulette. Can’t build confidently. Ecosystems splinter.
My bold call — this births a dark pattern. By 2027, half top projects source-available. True open source retreats to niches. Clouds win indirect; they partner with ‘available’ vendors. Devs lose freedom.
But wait — upsides? Devs eat. Redis Labs (now Vector) thrives. No more AWS Redis gravy train. Fair. Yet at what cost?
History echoes: copyleft wars. GPL fought proprietary abuse; OSI pushed permissive. Source-available? Neither. Hybrid Frankenstein — viewable, unbuildable.
Sentry August 2024. CockroachDB November. Accelerating. Nobody notices till their stack breaks.
Here’s the rub — recognition fails. GitHub stars blind us. LICENSE file? Buried. We download, hit walls, ragequit.
Source-Available vs Open Source: The Real Fight
Open source: fork, modify, sell. Freedom 0-3.
Source-available: read. That’s it. No derivatives without permission. BSL, SSPL — sneaky names.
Dry humor: it’s like dating someone who shows nudes but ghosts commitment. Tease, no touch.
Unique insight time — parallels Netscape’s doom. Opened Mozilla source; Microsoft crushed with IE. But forks lived (Firefox). Source-available? No forks. Dead end.
Prediction: backlash brews. Forks spawn anyway — Redis? Valkey lives, AWS-backed. But energy wasted fighting licenses, not building.
Corporate spin? ‘Protect innovation.’ Bull. Locks users in.
Long para now: we wanted vendor-free worlds — Postgres eternal, Linux kernel god. But greed creeps; authors eye VC bucks. Self-host? Pay for ‘enterprise’ keys. Or SaaS it. Indie dreams die slow.
FAQ time? Nah, end proper.
So, source-available. Fix for cloud pigs? Partly. Poison for collaboration? Absolutely.
Fight back. Scrutinize licenses. Star true open source. Demand better.
**
🧬 Related Insights
- Read more: AI’s Source-Blending Mess: How Citation Registries Rescue Attribution
- Read more: One Dev’s Radical Shift: Ditching Linux Cert Cram for a Living GitHub Lab
Frequently Asked Questions**
What is source-available software? Source-available lets you view code but restricts copying, modifying, or redistributing — unlike full open source licenses.
Will source-available replace open source? It’s gaining fast in databases and tools, but community forks like Valkey show resistance — expect fragmentation, not full takeover.
Is source-available good for developers? Protects project owners from cloud giants, but hurts solo devs needing full freedom — check LICENSE before diving in.
