Great question. It has two components for OpenMeter: 1. My personal frustration when I had to do usage-metering at Stripe and wanting to have a standard for it, like how we have it for metrics. I also find it silly that every company trying to figure this out on their own. 2. We want to build usage collectors for common cloud components and third-party APIs and I think it's going to be easier to do it together as a community instead of working in silos.

But yes I agree, it's more challenging to build in open but I think it benefits the customer, the quality has to be there.

Point 1 is a matter of personal taste so I can't argue. But for point 2, you don't have to opensource the whole project contribs. Contribs could be sub modules that can be imported into the project. My 2 cents is that you are heavily marketing that you are open source but might from an outsiders perspective it looks like a distraction.