I'm a non-technical founder.
I've built a couple of SaaS companies, many products, etc. Some failed, some allow me to conduct my living.
I'm non-technical so please consider you're explaining this to a Neanderthal:
What's the deal with this increasing trend of open-source SaaS companies?
Sure I know of WordPress and what have you - but what's the implication of e.g. Cal dot com, who's a Calendly alternative, but it's open source and it's clearly a business?
For instance, is it that: • people contribute to it (since it's open-source) and the founders can therefore build a better product... • ...whilst the PEOPLE also get a better free product, if they so choose to run it on their instance?
Is the above true? Because if so, I get it - it's a win-win, and the founders "tap into" a bigger pool of "effort", if that makes sense.
What other implications are there? Thanks so much.
But if you don't want to read the entire post, here's the tl;dr:
1. My (larger) customers wanted the source code for auditing purposes. I was using code escrow for larger customers and it was annoying to manage. If some can have the code, why not all?
2. My customers wanted me to eliminate my bus-factor of 1. If I got hit by a bus, the business died. Now it can live on and I can grow on my terms.
3. My customers wanted to have an "out" if the business ever decided to shut down. Now they have that "out" via self-hosting/forking.
4. My customers wanted me to show them they can trust me with their vital business data, and open source builds trust.
5. I was tired of dealing with copycats (some verbatim stealing my API schema and docs). Hopefully, moving forward, nobody will want to use a closed source copycat of an open source project.
6. My (larger) customers wanted to self-host for compliance purposes (mostly i.r.t. where data is hosted and accessed). If some can self-host, why not all?
As you can see, most of my reasons (but not all) stem from what my customers wanted. I didn't open source my SaaS for community, or to get free work, or to tap into "a bigger pool of effort." I did it because being closed source was a major pain point for me and my customers. So I took notes over the first 7 years, and I finally reacted. And I've only seen positives thus far (which I'll write more about later this year), so my initial fear wasn't warranted. I encourage others to do the same.
(My reasons aren't going to Cal's reasons. Peer wrote about his reasons here [1].)
[0]: https://keygen.sh/blog/all-your-licensing-are-belong-to-you/
We're doing just that with our own CRM [1]. It couldn't have been a side-project as you need thousands of engineering hours to build something decent. But with only a few millions in engineering spend, we'll have something that is genuinely as good as the products from billion dollar behemoths. Open Source software will never be able to monetize as well as closed-source. We might only capture 10% of the value we create. But being open source inherently creates strong network effects that tends to push towards a limited number of winners, and the addressable market in CRM is so big that it's still possible to build a multi-billion dollar company while massively driving the costs down for everyone.
It's kind of like the Prisoner's Dilemma: If every company keep their software proprietary, they can all make moderate growth/profit. But if one goes open-source, they could attract a large community, drive innovation, and potentially reap long-term profits while reducing the overall market size.
Consider Bitwarden, for instance. Does it have any real competitors running on a quick rebrand of their stack?
Better yet, as a non-technical founder, why haven't you stood up a successful Bitwarden competitor? The secret sauce is right there and you can contract-out the rebranding for like $20.
It's rare to have a tech mote nowadays and without a tech mote competitors will pop up whether or not you choose to go F/OSS.
I can simply run a self hosted solution.
This is why I love Bitwarden and Source Hut so much.
Of course, the other side of the coin is that you have to be careful with the price point, if you move it up too much I might want to self host despite the inconvenience.
What do people pay for? The code, or the things the code does?
What is valuable to customers? Is trust more important than the unknown? Is expertise valued?
What other things apart from code makes up a business? For example customer service, marketing, etc.
Also for reference, RedHat's entire business model was like this, mostly charging for enterprise support. I use past tense because I have no idea what they do today. Way back in the day that mean when you submitted a support ticket, you might get a developer that worked on the product to help you if it was beyond their initial support triage level.
More sales and trust. Vendors who open source are offering their customers the right to repair and self-host their products should they go belly up. That itself is a selling point.
You could read up on the "open core" approach. Gitlab is a good example.
For example a collaborative software text editor might require connections to a central database for synchronising the various users. The code to handle these connections might not be available, or at least heavily restricted through licensing from using in a business environment.
The SaaS company makes money by providing the infrastructure to allow users to actually collaborate with others. Until then it's simply a stand alone desktop text editor.
Alternatively the company may offer basic collaborative features which only support one 3rd party auth provider and synchronise via the public internet.
A customer might want on-prem networking only and Active Directory auth, and will pay for these features.
People find your free product, you lock some core features behind a paywall or make the cloud offerring easier to use, so people switch from free to paid. It's a lead magnet.
