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.
Selfhosted
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.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
as opposed to plausible community edition which is even more limited and is only updated a couple times a year?
The community edition allows me to have multiple sites, multiple users and is way easier to set up. If I ever need additional features like funnels I would need a subscription for both - Plausible is less expensive.
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?
Is it "reebit"? OR "Raybit" ?
it's "ribbit"
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.
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.
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:
- Pages View
- Web Vitals
- Email reports
- Google Search Console integration
- VPN/Crawler/ASN tracking
- Google/GitHub OAuth
- Email support
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:
- These features exist in the public repo but are just marketed as "cloud-only" (in which case the comparison table's misleading)
- These features are truly separate proprietary code that interfaces with Rybbit without being part of the AGPL-licensed work (which would require careful architectural separation)
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?
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 misleading. While copyright owners aren't bound by their own license, AGPL Section 13 requires that when they run AGPL software as a network service, they must make the complete source available to users.
The AGPL was specifically designed to close the "SaaS loophole." Being the copyright owner doesn't exempt you from AGPL's network service requirements if you're distributing under that license.
This is flat out wrong. If you're the copyright owner, you're not licensing the code to yourself. The AGPL is the license under which they're making the open source version available to YOU. The version they run themselves is proprietary.
That's inacurrate. Licensing representation matters. If the cloud service is genuinely presented as AGPL-licensed, Section 13 obligations apply regardless of copyright ownership. However, copyright owners remain free to maintain truly separate proprietary versions under dual licensing.
Thank you for your service.
Is there any plans for a data migration feature from Plausible?
I don’t think that's plausible.
We have data migration plans in work but it doesn't appear that a plausible migration is possible
I've been using Plausible for a long time, will definately be checking this out.
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.
Thats fuckin baller!!
🐸
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