Usage Metering For Engineers
While shifting to a world where we pay for software based on what we use, engineers lack standards around metering and businesses struggle to find actionable insights in usage data.
While Peter was working at Stripe, he realized it was challenging to collect usage data from all the different components due to the lack of standardization around metering. While having good data quality was critical to working with Finance and Efficiency, collecting, aggregating, and analyzing usage took a lot of time and effort.
In 2023, we joined YCombinator, and as we started to dig deeper, it became clear that this was just the tip of the iceberg. Companies with usage-based pricing face challenges from engineering to finance, from product to sales. Once revenue is driven by usage, it is critical to have an accurate view of it and to identify actionable insights around it.
This is especially true for AI and DevOps companies that price their products based on a large volume of data points, like the number of seconds, token usage, or API calls.
To change the status quo, we launched OpenMeter as an Open Source project because we believe standardization is only possible as a community. We want to do this together, with you.
The Team Behind It
We are a team of engineers who worked on observability and infrastructure at Stripe, Netflix, IBM, Ustream, Banzai Cloud, and Cisco. Before OpenMeter, we built a Node.js APM together and led the Node.js Diagnostics Working Group.