Launch HN: OpenMeter (YC W23) – Real-Time, Open Source Usage Metering

Re:Launch HN: OpenMeter (YC W23) – Real-Time, Open Source Us... by mercurialsolo on Thursday June 22, 2023 @10:26AM (#36432662)

I would love to see a wrapper around all API calls which is metered by default. Showing usage and meters which you can set at a per-integration level, per-user, per-key, per-function level.

Congrats on launching this, there's lots of ways to deal with this, but would love a metering standard much like we have one around tracing.

[ Parent | on HN ]

Re:Launch HN: OpenMeter (YC W23) – Real-Time, Open Source Us... by hekike on Thursday June 22, 2023 @10:36AM (#36432792)

I like the idea of meter all primary business executions by default and pick what you want to use later. This is useful if you want to do cost analysis, iterate on pricing, etc.

Would you track API calls by default like a usage-based third-party (OpenAI API, Twilio, etc.)? Or your own web server (Lambda, Next.js etc)? Or both.

[ Parent | on HN ]

Re:Launch HN: OpenMeter (YC W23) – Real-Time, Open Source Us... by mercurialsolo on Thursday June 22, 2023 @10:58AM (#36433149)

We do both, services as well as a mix of serverless and on-demand servers we spin up. I would also like this to have the SaaS usage sprawl bundled into this, e.g. emails, notifs, and SaaS tools with expanding usage tiers,

[ Parent | on HN ]

Re:Launch HN: OpenMeter (YC W23) – Real-Time, Open Source Us... by hekike on Thursday June 22, 2023 @11:41AM (#36433885)

Cool, thanks for sharing it. Would you use SaaS usage for cost analysis or to charge your own customers for shared resources?

[ Parent | on HN ]