Re:Show HN: I built a self-hosted error tracker in Rails
by vanschelven on Sunday November 09, 2025 @01:54PM
(#45868059)
"it can deal"... with 300 events/s easily.
Re:Show HN: I built a self-hosted error tracker in Rails
by nasmorn on Monday November 10, 2025 @10:11AM
(#45876712)
It works out because sentry has basically gone full solarwinds. Trying to get rid of the small accounts because they only care about the enterprise market anymore
Re:Show HN: I built a self-hosted error tracker in Rails
by zeeg on Monday November 10, 2025 @01:55PM
(#45879414)
Clearly this is bait but we have done nothing but be supportive of small accounts.
It’s still $29, we still are extremely generous on forgiveness and sponsorships, and we still prioritize the long tail.
70% of our business is smb/mm, and if you knew anything about us you wouldn’t make the statement you said above.
If we have done something to show otherwise I would love to see it so we can address it.
Re:Show HN: I built a self-hosted error tracker in Rails
by nasmorn on Tuesday November 11, 2025 @06:43AM
(#45886248)
I guess I’ve got a lot of resentment for when I suddenly paid for 100k reserved errors suddenly that I didn’t remember asking for. I probably figured out I have control about it at some point and that’s why I decided to not do the Schlepp of changing the error reporting on all these small projects.
So while I can actually corroborate that your cheapest plan has not changed my takeaway is that changes to billing just make people unreasonably resentful. At least me.
Re:Show HN: I built a self-hosted error tracker in Rails
by dang on Tuesday November 11, 2025 @04:52PM
(#45893391)
Please don't hijack competitors' Show HNs to promote your own thing. A single mention is arguably ok, but beyond that it gets too be too much, especially when related accounts are involved or it crosses into multiple threads.
Also, please don't use HN primarily for promotion in general. This is in the site guidelines: https://news.ycombinator.com/newsguidelines.html.
High throughput: Bugsink has at least 2 layers of spike-protection: ingestion (storing) and digestion (dealing with) events are separated out; also: you can set rate limits. Ingestion-wise it can deal
The pricing model has been mentioned a few times already: I wonder how that will work out for them. In any case, Bugsink is free to use if you host it yourself and cheaper than Sentry if you go hosted/SaaS.
It's interesting to say that the "drop in replacement for Sentry" is a model that is gaining popularity.