News for hackers. Stuff that matters.
Re:O'saasy License Agreement by the_mitsuhiko on Tuesday December 16, 2025 @02:30AM (#46285760)
I know I am tooting Sentry's own horn a bit here, and since I was involved it is close to my heart. We struggled at one point with how to build a large company on top of an open source project, and we never liked the idea of simply carving out parts of the codebase and marking them as closed source (open core). At the same time, there was always the latent risk that even if you put 95% of the energy into the product, you were still not fully in control and someone else exploits the economic value without investing.

Our way of dealing with this was delayed open source publication. That led to the FSL [1], and later to bootstrapping the Fair Source initiative [2] to establish an umbrella term that does not conflict with Open Source. What I have found interesting in the years since is that many companies are wrestling with the same problem, but feel that the two year head start the FSL gives is too aggressive.

I actually still find that surprising. I would like to know whether this is a legitimate concern that two years is not enough, or mostly a perceived one. To me, moving to an Apache 2 or MIT license after a relatively short period is a much stronger statement than a license that risks the project effectively ending if the commercial entity is unwilling to relicense it more openly at the end of its life such as the O'saasy license.

[1]: https://fsl.software/

[2]: https://fair.io/

Re:O'saasy License Agreement by actionfromafar on Tuesday December 16, 2025 @04:13AM (#46286390)
The end of life problem can be solved by source code escrow, with a clause putting the code under an open source license and published in case of the demise of the owning cpmpany.
Re:O'saasy License Agreement by ta2234234242 on Tuesday December 16, 2025 @07:40AM (#46287795)
If the company is sold for its assets is the code released to the public? Or removed from escrow and kept private?
Re:O'saasy License Agreement by actionfromafar on Tuesday December 16, 2025 @09:03AM (#46288582)
That's the gritty stuff which must be spelled out in the terms.
Re:O'saasy License Agreement by Kerrick on Tuesday December 16, 2025 @05:29PM (#46295517)
With O'Sassy specifically, the end of life problem solves itself. If the original vendor stops offering the software, a third party offering the software is not competing with the original vendor. Thus, the third party can offer paid hosting for the software if the original vendor does not.

Or am I reading it wrong? I am not a lawyer.

Re:O'saasy License Agreement by ezekg on Wednesday December 17, 2025 @12:25PM (#46302553)
This is the entire point of Fair Source undergoing delayed Open Source publication -- to codify the forward-path into the license itself, without the need for external source code escrow services.
Re:O'saasy License Agreement by cobertos on Tuesday December 16, 2025 @03:57AM (#46286307)
Why not just release the software after your set threshold of time versus opening it up with such a license? To get eyes on it before-hand?

Also how does this work with contributor contributions? Does the owning SaaS get the benefit of contributor work instantly while everyone else has to wait 2 years? What about the contributers themselves?

Re:O'saasy License Agreement by Nextgrid on Tuesday December 16, 2025 @04:20AM (#46286435)
> Why not just release the software

You may want to allow certain uses (self-hosting, etc) even before it transitions to a fully open-source license. Having access to the source code can also help SaaS users debug certain situations.

Re:O'saasy License Agreement by rcxdude on Tuesday December 16, 2025 @04:22AM (#46286452)
presumably because a) it still allows the source code to be available and used for the 'permitted purposes' (i.e. anything that's not directly competing), and b) it represents a concrete commitment to open up, not just a pinkie promise (even if they were to have a license or contract which promised it, it would not be as easy to rely on as actually having the source code published. Companies have reneged on such promises before).

And yeah, by my reading essentially people can contribute code or publish patches (with just a plain MIT license in principle), just the original and derivatives still can't be used for non-permitted purposes until the timer is up.

Re:O'saasy License Agreement by the_mitsuhiko on Tuesday December 16, 2025 @05:05AM (#46286763)
> Why not just release the software after your set threshold of time versus opening it up with such a license?

That requires trust that the company will do this. The FSL is irrevocable and comes with a future promise.

> Also how does this work with contributor contributions?

The same way as any other thing with a CLA works. If you don't have a CLA, then you have a bit of a mess.

Re:O'saasy License Agreement by bberenberg on Tuesday December 16, 2025 @03:40AM (#46286197)
Isn’t the “solution” for Sentry that deploying it is such a pain in the ass that no one bothers to really do this? I haven’t checked in years but that always seemed like the real competitive blocker?
Re:O'saasy License Agreement by Nextgrid on Tuesday December 16, 2025 @04:21AM (#46286446)
Agreed. It was easier for me to rebuild parts of it for my own use than to self-host it. At my scale, a single DB works well as a datastore instead of Clickhouse/etc.

But then again I think this only prevents small players from "competing" by self-hosting, so the revenue loss there would be minimal either way. Large enterprises are too incompetent to even self-host a single self-contained binary, so for those the availability of source code and ease of hosting would make no difference, they would still use the SaaS.

Re:O'saasy License Agreement by mechsy on Tuesday December 16, 2025 @04:31AM (#46286523)
If you need less scale/features go for glitchtip. If you’re not going for k8s, the self-hosted docker-compose version of sentry works fine including proper releases and support by the sentry team etc. Just experimental newly introduced features can be a bit wonky. They are doing much more than just throwing code over the fence. Also phone home telemetry is optional and there’s a switch for just errors mode. IMHO this really builds trust. With regards to deployment complexity: well it’s built for handling high volumes of events. I’d reckon this is more a consequence of scaling the project rather than a coordinated plan to push people to their cloud offering. If you do go for k8s or choose to deploy the stack yourself, you even get access to the full scale solution. But if you’re at that scale, you probably have someone hanging around who knows how to run your clickhouse setup. You still get the full sentry software and SDKs for free in that case. I think this is as fair as it gets with regards to the open source SaaS model.
Re:O'saasy License Agreement by homebrewer on Tuesday December 16, 2025 @04:43AM (#46286602)
This may very well be caused by my incompetence, but Sentry's docker-compose setup has never survived for more than a few months under my control. Something always destroys itself without an obvious reason sooner or later, and either refuses to start, or starts and doesn't really work. I tried updating it regularly, tried never updating it, getting the same treatment either way.
Re:O'saasy License Agreement by bberenberg on Tuesday December 16, 2025 @04:55AM (#46286694)
I did not intend to be critical of their work. They're doing OSS as best as they can and good for them. I am just saying that it's a different beast if Sentry is OSS vs a much simpler to operate OSS product. Licensing matters less when the operational cost acts as an inhibitor to adoption of your OSS offering.
Re:O'saasy License Agreement by mechsy on Tuesday December 16, 2025 @05:48AM (#46287040)
True, opportunity cost is a factor, sorry if my reply sounded a bit brash. IMHO they are one of the few orgs who got this model right compared to lots of others who went the open core or support/consulting contract required OSS route.
Re:O'saasy License Agreement by the_mitsuhiko on Tuesday December 16, 2025 @05:03AM (#46286758)
> Isn’t the “solution” for Sentry that deploying it is such a pain in the ass that no one bothers to really do this?

That Sentry is a pain to deploy is not really intentional, it just happened over the years. However because it's a pain to deploy it also opens up a market for people that create managed deployments so I would say, that if anything, it made it worse. For self deployed Sentry you do not need to pay cent, the license explicitly allows it.

Re:O'saasy License Agreement by veeti on Tuesday December 16, 2025 @02:07PM (#46292860)
Don't believe the salesmen, self hosting Sentry has been the most liberating feeling in a long while. Buy a cheap dedicated server with 64 gigs of RAM from Hetzner, run their install script and it's literally up and running. I'm processing volumes that would bankrupt me on their managed service without breaking a sweat.
Re:O'saasy License Agreement by charlestehio on Wednesday December 17, 2025 @03:34AM (#46299558)
I had no idea an error/APM monitoring requires this much of RAM. Could you provide a ballpark number on your processing volume?
Re:O'saasy License Agreement by vanschelven on Tuesday December 16, 2025 @02:29PM (#46293179)
Earlier discussion on Hacker News: https://news.ycombinator.com/item?id=43725815

I'm personally on the fence how much of it is intentional... from the_mitsuhiko's side it probably isn't, but "the purpose of a system is what it does" and all.

Re:O'saasy License Agreement by ignoramous on Tuesday December 16, 2025 @04:05AM (#46286342)
> you were still not fully in control and someone else exploits the economic value without investing

O'Sassy came up recently in one of the forums I lurk in [0], and as discussed there, I tend to agree with Adam Jacob (SystemInit) and others that FSL is definitely one way out but doesn't totally solve the commercialization aspect, because the code & all that IP is still readily available.

Adam, in this talk [1], argues that like RedHat (and unlike Canonical), Open Source businesses must learn to separate source license from distribution license and if they do so, the money is there to be made (in a b2b setting, at least).

> What I have found interesting in the years since is that many companies are wrestling with the same problem, but feel that the two year head start the FSL gives is too aggressive.

... if the companies conflate Open Source and business models, rather it being merely a Go-To-Market (like open core).

Especially true for dev/infra upstarts competing with incumbents (PostHog v Amplitude / GitLab v GitHub [2]), and lately for AI labs (DeepSeek/Qwen/Llama v GPT/Gemini/Claude). In a role reversal, BigTech also uses Open Source to commodotize its competition's advantages (Android v iOS / k8s v Swarm / IE v Firefox/Chrome) [3].

[0] https://forum.fossunited.org/t/6878

[1] https://www.youtube-nocookie.com/embed/watch?v=rmhYHzJpkuo / Summary: https://gemini.google.com/share/e21cd1bacff6 (mirror: https://archive.vn/Jzhk3)

[2] https://www.heavybit.com/library/video/commercial-open-sourc... / https://archive.vn/jQh27

[3] https://gwern.net/complement / https://archive.vn/QITxC

Re:O'saasy License Agreement by zeeg on Tuesday December 16, 2025 @11:39AM (#46290709)
The issue is these are mostly academic points of view. Sentry’s model on the FSL (and previously the BUSL) has shown to be working just fine at scale.

Whereas, for example, trademark protections have shown to fail easily.

So people can argue it doesn’t work, but so far we only have evidence to the contrary and Sentry is quite successful.

Re:O'saasy License Agreement by ignoramous on Tuesday December 16, 2025 @02:02PM (#46292787)
> So people can argue it doesn’t work, but so far we only have evidence to the contrary and Sentry is quite successful

So, RedHat has also been successful?

GP says that some companies don't find FSL aggressive enough, despite it having worked nicely for Sentry. And that's similar to the point Adam makes: That Open Source (per OSI not FSF) is a development model not a business model. Companies that don't want/need to prioritize collaboration tend to use FSL / BUSL / etc; but those licenses aren't really going to significantly change their development or business (other than prevent competition from using it as-is, but now the code is out there anyway [0][1]), and so they might as well go close source (and Lockdown the code, too).

> issue is these are mostly academic points of view

Both, commodotizing competition (through OSS) and using OSS as Go-To-Market aren't academic PoVs, I don't think.

[0] And trained on by LLMs, which makes cloning probably that much faster? https://x.com/paultoo/status/1999245292294803914 / https://archive.vn/kTiyZ

[1] Companies will deep pockets and technical expertise can/will anyway clone it: https://bcantrill.dtrace.org/2018/12/14/open-source-confront...

Re:O'saasy License Agreement by zeeg on Tuesday December 16, 2025 @04:00PM (#46294404)
I'm not talking about RedHat, I'm talking about the perspective that "FSL / BUSL aren't effective enough". They solve the problem. O'saasy is just freeware at the end of the day, FSL creates more open source, and BUSL often has (though unfortunately the license doesnt require it).

The idea that FSL ~= Closed Source is entirely wrong and misunderstands the value that an open distribution gives. We have 10s of thousands of customers that run Sentry self-hosted. We regularly get contributations back to our core service - both in code and (what we prefer) other artifacts like feedback.

We were "Single Origin Open Source", which is extremely common whether people like to believe it or not. Its the entire premise of the sustainability issue in the industry. Thats not just an issue for commercial entities, its also most of the big open source software people rely on. In our case though we have a great business model that makes it entirely sustainable, and now have built a solid licensing mechanism around it that protects that, while ensuring our community is still successful.

Ive written about a lot of these kinds of things:

https://cra.mr/open-source-is-not-a-business-model https://cra.mr/open-source-and-a-healthy-dose-of-capitalism https://cra.mr/the-busl-factor

These same issues around single origin open source are why we started the no-strings-attached funding mechanism via Open Source Pledge (https://opensourcepledge.com), why we push Fair Source (https://fair.io).

Maybe others will find defensible models, but I'm skeptical. I also respect Adam, but last I understood it the model they were going after sounded pretty similar to trademark protection (which doesnt work).

Re:O'saasy License Agreement by ignoramous on Saturday December 20, 2025 @06:37PM (#46340760)
Thanks for the links. I read those and some more from your blog. I've also been to a Chad Whitacre talk about Sentry's OSS approach at a conference this year.

I don't think we're disagreeing at all. I quoted Adam to drive the point that tech shops that value collaboration will tend to prefer OSI-approved licenses. That doesn't seem to be the case for Sentry:

  [Sentry is] single-source. That is, [the Company behind it] are the authors and maintainers of the software, and [does] not expect the community to provide us with contributions. We still allow it, and are thankful, but we consider it our duty to develop our software.
At the other end of the "single-source" spectrum is SQLite which is closed to collaboration but is dedicated to public domain and requests a fee for "Warranty": https://sqlite.org/copyright.html

It does seem like Sentry wants control over distribution, but by the way of license? Adam proposes something similar (and I guess that's the reason he's okay with "Fair Source", like a few others too who want to unchain the idea and go beyond OSI / Open Source [0]):

  [Sentry wants] to allow people to self-host our software.
> I also respect Adam, but last I understood it the model they were going after sounded pretty similar to trademark protection (which doesnt work).

A counter example: The Android Open Source Project is OSS, and is firmly gate-kept by Google via trademark and other collaborative arrangements like the Open Handset Alliance and Linaro. That said, this is the happy case. Sentry clearly had a different experience with bigger tech shops (GitLab?) trying to monetize its offering without contributing anything back, which (tbh) sounds super terrible.

To me, there seem to be pathways to both succeed & fail with OSI-approved licenses (probably you'd argue... one'd fail more than succeed), and these licenses on their own are neither the only condition nor a sufficient one for business build around them to stumble and falter. That said, I get your point that "Fair Source" gives "single-source" projects a fighting chance, like it did for Sentry. I'd also have thought that the OSI-approved AGPLv3 (your reservations about copyleft notwithstanding) is enough to keep big shops from leeching from other high-quality mostly single-source projects... but may be I was mistaken (given MongoDB / Elastic / Redis / CockroachDB didn't think so; even if, Elastic & Redis switched back to including OSI-approved license, specifically the AGPLv3).

[0] as indicated here (linked to from one of your blog posts): https://medium.com/@nayafia/i-hate-the-term-open-source-a65f... / https://archive.vn/K7CHs