A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
Hi guys, I've been working on a self-hostable web analytics platform since the start of this year after being frustrated with Google Analytics and Plausible.
I've packed a bunch of cool web analytics features into Rybbit, but I've tried very hard to keep the interface simple to use,
https://github.com/rybbit-io/rybbit
Check it out!
A few more screenshots in case you don't want to leave the site
I have no idea how to use this, but this is amazing!
What should we try with the live demo? Neat stuff, it's this a long-term project?
You're awesome. Thanks!
Wow holy crap, great work - the world badly needs this. Im assuming the mechanism is the same, you inject a js script into your site. I'm also very interested in pure server side solutions for analytics, but they can't hit all the features you did in a generic way afaik
Yea, we use a client-side script like almost everyone else. The major difference is that we don't use cookies so you can avoid a lot of the cookie banner/GDPR nonsense.
Rybbit definitely isn't the first open source cookieless web analytics platform (Plausible and Umami are the two other big ones), but it's probably the most "all-in-one" of all these alternatives.
Do you use fingerprinting instead? Or what’s the mechanism you use?
You mentioned being frustrated at Plausible. What did you not like about it?
I haven't tried Plausible, but it seemed popular
it didn't have enough features, especially since the community version is heavily nerfed (it's missing even funnels)
Question is the self-hosted version less featured than the paid hosted version?
This looks amazing btw.
Only very slightly so. One of the reasons I created Rybbit is because platforms like plausible and fathom have much inferior self-hosted versions (very limited featureset and basically never updated). We have a comparison here
@Goldflag
I appreciate the intent behind Rybbit, but I have to respectfully disagree with the "only very slightly so" characterization. Looking at your official comparison table, the self-hosted version is missing:
That's 7 significant features—which seems more than "very slightly" different.
More importantly, this raises AGPL compliance questions. Under AGPLv3 Section 13, if users interact with modified AGPL software over a network (your cloud version), you're required to make the complete corresponding source code available to those users. If these cloud-only features are integrated into the same AGPL-licensed codebase, withholding them from the public repo while running them as a network service appears to conflict with the license terms.
There are really only two compliant scenarios here:
If it's neither—if these are AGPL-covered features running in your cloud service but withheld from the repo—that's exactly the "loophole" the AGPL was designed to close. The irony is that you criticized Plausible and Fathom for having "much inferior self-hosted versions," yet this appears to be a similar approach.
Could you clarify the licensing status of these cloud-only features? Are they in the public repo but disabled by default, or are they proprietary additions that don't derive from the AGPL codebase?
Thank you for your service.
OAuth is one thing I hate to see locked behind a paywall; it's one thing for the pretty, management-geared stuff (dashboards and charts) to be a paid feature, but not security.
AGPL means they are licensing it to you, they are not bound by the license because they are the copyright owners.
That's excellent and very clear, thank you for the explanation.
Thats fuckin baller!!
🐸
hmm interesting im using matomo but im not liking how its increasingly becoming bloated and subscription based
Aways a fan of alternate options, this looks quite tidy! I had a few thoughts / queries. Not at my system right now but I will test it out later.
I noticed in the screenshots you have a "users" page - but with a cookieless tracking system I would have assumed it wouldn't be reliable to identify a long term user past individual sessions? Are you doing some hefty finger printing?
Looking at your features table has a few statements that might need adjusting. Such as GA4's segmentation sequencing / filtering can be quite complex, I'd argue its not limited and potentially more advanced than Rybbit (not tested yet). It also has a user exploration feature.
Do you have any plans for a drag and drop style report creation, so that I could create reports with any dimensions / metrics and filter accordingly? I think that would bring a lot of flexibility to the platform for an individuals bespoke needs.
How would this compare to something like PostHog?
Posthog makes it almost impossible to actually self-host since they try to push you onto the cloud as much as possible. They say that the self-hosted version only works well up until 100k events ... which is insane since their cloud free tier is 1 million events. It's actually the reason why I built Rybbit. I tried to self-host posthog on my server but it ran it up to 100% CPU on 8 cores and didn't even work.
Ok posthog rant done.
The other main difference is that Posthog has like 10+ different products all in one. Their web analytics is good, but it's just kind of bland (imo) because it's not their main focus.
This looks... Great? Nice work
Just a word of warning for everyone: The free self hosted version is heavily limited. I will stick with Plausible which may be simpler but also doesn't want to push me into a subscription.
Is it "reebit"? OR "Raybit" ?
it's "ribbit"
it looks beautiful!! do you plan on making the wcv available for the self hosted version in the future?
Glad to see you post this here. I've been experimenting with selfhosted analytics for a while now and have attempted your project here a couple times. The thing that kills me is the Clickhouse requirement. It makes it impossible to host on a lightweight VPS. Like why should my analytics platform require so much more compute than my simple static site? Am I missing something?
Clickhouse definitely takes a lot of resources! There's unfortunately no way around that, though in my experience it runs fine on the cheapest Hetzner instances which are like $3-4 a month for 2GB of RAM. How lightweight is your VPS?
And yea, you don't need clickhouse for a simple static site. I chose clickhouse because it Postgres or MySQL does not scale well since the main site I personally use Rybbit for sends around 20 million events a month.
It pains me to plug my competitors, but check out Umami or Goatcounter if you want a platform that uses postgres.
Aren't there already tons of these already? Piwik has been around for a quite a while, plus there are others mentioned in the comments.
variety is the spice of life.
What's the advantages over awstats?
from what i know, awstats gets analytics from server-side logs while Rybbit uses a client side script. So not really and apples to apples comparison
The same advantages as all free and open source solution, it's free and open source. That means how much it's going to cost to your business is directly under your control. You can make a decision on how you acquire hardware based on your business's needs. If you want to add or change features you can decide how to do that based on the deals you have with your programmers (like pick the developer you have with the best skills and the lowest cost), and then you get to control how much it costs you and how reliable the result is going to be.
If you feel like the support you get from customer service from Amazon or Google or Microsoft is reliable enough and you don't need more reliability then go ahead and stick with paid products. But if you already have a team of really expensive and talented engineers you might as well let them solve problems with free and open source equipment.