I was informed that starting January 1, 2025, the updated pricing model will take effect.
Simplified Consumption Credits: The current pricing model, based on data routed from Notehub, will be replaced with a simpler approach based solely on event ingresses into Notehub.
I noticed that every time I receive an event in my Notehub, I first get a _session.qo (opened) and then a _session.qo (closed) message.
Could you confirm if these _session.qo messages will also count as events and consume credits?
If that is the case, each event sent from my sensors would consume 3 credits.
Additionally, I was informed that each event costs 1 CC, priced at a flat rate of $0.000750 each.
Does this mean that discounts for bulk purchases will no longer apply?
I see we posted at the same time the same question :-), For us _session.qo events account for approx 10x the _data.qo events we generate due to scheduled sync requests
Yes, I noticed that. I am also concerned about the flat rate and the potential impact on bulk pricing.
I hope these changes won’t lead to a more expensive and complex service. When bringing a solution to market, changes in pricing models for critical components are not ideal.
Yes, _session.qo is also counted as the ingress event, similarly to other system events like _geolocate.qo, _log.qo and so on. We’ll provide a UI in Notehub that enables you to opt-out from us generating these events in Notehub if you wish so. Please also note that _session.qo (as well as other system events) provide quite a lot of useful information that increases an overall service value.
The rule-of-thumb here is that whenever an event appears in Notehub’s event view, it is counted as the ingress event. We are not going to count any events that are not accessible to our users.
Please also note that you have control over how often _session.qo events occur from your hub.set configuration. See Essential Requests - Blues Developers. Please also note that we abolish any charges for routing data out of Notehub.
As for the unit price for the consumption credit, it is set to a flat rate of $0.000750. However, we will continue to offer significant volume-based discounts for enterprise customers. If you’re scaling a deployment and interested in learning more, you can reach out to our Sales team at Contact Blues.
I must express my disappointment with these recent changes. Removing the bulk buy option is a major setback, especially for small businesses like mine that are trying to scale our solutions affordably. This change will undoubtedly make things much more expensive, and that raises significant concerns about long-term sustainability and trust. It’s a huge red flag for me.
It’s also concerning to think about what could come next. What would happen if my final product were already designed with the Blues connection? Such abrupt changes could put businesses in difficult positions, forcing expensive redesigns or operational shifts.
While I appreciate the transparency regarding _session.qo and other system events, as well as the ability to opt out of generating these events, the overall direction of these pricing and service changes feels unfavorable for smaller-scale developers. The flat rate and volume-based discounts for enterprise customers only seem to widen the gap.