Cloud features aren’t just a toggle away for self-hosters because setting CLOUD=true enables unwanted restrictions like Stripe billing endpoints and event limits—it was intended as a binary switch for enabling the entire cloud infrastructure.

Rybbit wasn’t architected so self-hosters could modularly enable advanced features. To solve this, I’ve forked the project and made all enterprise features modular and enabled by default, so people can test them.

Of course, it would be desirable that @Goldflag implements this himself because I’m sure he could do it more elegantly and maintain it properly as part of the official project going forward.

@Goldflag,

Thanks for clarifying! Good to hear everything’s in the repo and that it’s truly AGPL compliant.

Since as self-hosters we already carry the burden of maintenance, updates, security, and infrastructure costs that cloud users don’t, would you consider documenting how to enable the cloud features in self-hosted setups?

I see the docs cover basic environment variables, but not for Pages View, Web Vitals, or VPN/ASN tracking. Even if some features need extra config (SMTP, OAuth creds), having that documented would help those of us willing to do the work.

That would truly differentiate Rybbit from Plausible/Fathom—not just code parity, but empowering self-hosters with full feature access.