Reaction to the new pricing: The per-worker model hurts our bursty workloads.

DavidN · 2026-08-05T15:26:21Z

The shift to a per-worker pricing model in Cribl Stream's latest structure has created a significant financial and operational mismatch for our specific use case. Our data ingestion is inherently bursty, tied to end-of-month financial closes and quarterly logistics audits, where volumes can spike 10-12x above baseline for 48-72 hours. Under the previous capacity-based model, this was manageable. Now, provisioning for peak with dedicated workers is cost-prohibitive, while provisioning for average leaves us unable to handle critical business events without data loss or queue overflows. The auto-scaling groups in the cloud are a partial answer, but the licensing constraint means we must permanently license for our theoretical maximum, negating the economic benefit of scaling the underlying infrastructure. I've mapped the cost impact across three scenarios: * **Baseline (Average Load):** 2 workers constant. New model shows a ~15% increase over previous, which is acceptable. * **Monthly Close (5-Day Burst):** Requires 12 workers. New model costs 6x the baseline for that period, whereas previous model would have incurred only a slight overage. * **Quarterly Audit (2-Day Burst):** Requires 18 workers. This short, extreme burst is now the single largest cost driver for the quarter, skewing our entire OpEx forecast. This model seems optimized for stable, predictable data flows, not for the variable nature of B2B logistics and integrated ERP event streaming. Has anyone else in supply-chain or SaaS-ERP verticals developed a strategy to mitigate this? I'm particularly interested in architectural workarounds, such as: * Pre-processing spike data to a buffer (S3, Kafka) and metering it to a smaller worker pool. * Negotiating a hybrid license that combines a base worker commitment with a burst pool at a different rate. * Leveraging the free tier for specific, high-volume but low-criticality sources during peaks. Without a more flexible licensing approach, we are being penalized for the very business cycles that make our data valuable.

Page 2 / 2 Prev

Cribl Reviews

Last Post by ide_tinkerer 58 minutes ago

16 Posts

16 Users

0 Reactions

1 Views

RSS

ide_tinkerer

(@ide_tinkerer)

Reputable Member

Joined: 4 months ago

Posts: 189

06/08/2026 9:22 am

That attestation flip is brilliant. We tried something similar, but got bogged down in defining "preventable." Your version puts the onus back on them to prove their model doesn't cause it. That's much cleaner.

It makes me wonder if this is less about licensing and more about vendor-customer power dynamics. A vendor confident in their model's fairness would sign that without blinking. The fact they can't is a huge signal.

What happens when procurement gets that red flag? In my experience, they just use it to negotiate a small discount, and the process continues. Has that written risk actually led to walking away?

editor is my home

ReplyQuote

Page 2 / 2 Prev