Independent reference. Not affiliated with any vendor mentioned on this site.
Pricing Models

SIEM pricing models: per-GB vs per-EPS vs per-employee vs flat-rate

The four billing structures every SIEM uses, the trade-offs of each, the vendors behind each, and a side-by-side comparison of the same environment priced under all four. Worked examples, no hand-waving.

Most common
Per GB
Splunk, Sentinel, Datadog
Most predictable
Flat tier
Panther
Simplest for SMB
Per employee
Blumira
Best for compliance
Per EPS
QRadar, ArcSight

Model comparison matrix

ModelVendorsBest forWorst forPredictability
Per GB ingestedSplunk, Sentinel, DatadogHigh-value, low-volume telemetryVerbose firewall and NetFlowLow (volatile with noise)
Per EPSQRadar, ArcSightQuiet, predictable sourcesSpiky bursts that breach peakMedium (peak governs)
Per employee / seatBlumiraSmall headcount, SMBLarge headcount, high log volumeHigh (linear with headcount)
Flat-rate / volume tiersPantherPredictable budgets, SMBVolume crossing tier ceilingsHigh within tier; cliffs between

Per-GB ingested

The dominant SIEM pricing model in 2026. The vendor meters every log byte that crosses the ingest boundary. Compression at rest does not reduce the bill. Splunk, Sentinel, Datadog, and most newer cloud SIEMs use this model.

Wins when security data is high-value (authentication logs, EDR alerts, threat detections) and low volume. Per-GB lines up cost with detection value.

Loses when verbose, low-value sources dominate. Firewall syslog, NetFlow, and DNS query logs can quickly consume 80 percent of GB billing while contributing 10 percent of detection value.

Worked example. 50 GB per day at $4.30/GB Sentinel PAYG = $78,475 per year. Filter 30 percent of low-value logs at the agent and the same environment costs $54,933. Filtering pays back faster than negotiation.

Per-EPS (events per second)

QRadar and ArcSight bill on event rate, not data volume. The metric is sustained events per second across all log sources, with a separate peak ceiling. EPS billing flatters quiet sources and penalises spiky ones.

Wins when log sources are predictable and balanced. Compliance environments with steady audit logging benefit.

Loses when bursty sources push the peak EPS ceiling. Web traffic spikes, batch jobs, or attack waves can force a tier upgrade based on bursts that don't reflect sustained value.

Worked example. 50 GB per day with mixed sources averages roughly 3,500 EPS sustained. QRadar on Cloud at this tier is an estimated $110K-$140K per year on licence (IBM publishes no list price). Equivalent per-GB billing runs roughly $60K-$100K depending on vendor: about $59K-$78K on Sentinel, and roughly $100K all-in on Splunk Cloud with Enterprise Security.

Per employee / per seat

A per-employee meter sizes the subscription by headcount rather than log volume. Blumira is the clearest 2026 example, billing from $12 per employee per month (Detect) up to $21 (Automate), so the invoice tracks seats and stays flat regardless of how much you ingest. Google SecOps (Chronicle) is often filed here by mistake: earlier Chronicle deals were sized relative to seat count, but its contractual meter is a GB data cap, so it belongs with the volume-priced vendors.

Wins when headcount is small and log volume is unpredictable: because the bill tracks seats rather than bytes, a noisy month costs nothing extra, which suits SMBs with lean teams and verbose telemetry.

Loses when headcount is large relative to log volume, because you pay per seat for log infrastructure a per-GB meter would bill far less for.

Worked example. 300 employees on Blumira Automate at $21 per employee per month is about $75,600 per year, flat whether you ingest 5 GB or 50 GB per day. Contrast Google SecOps, once the canonical per-employee example but now metered on a GB data cap (about £2,000 per terabyte per year on the only published listing): a firm ingesting 200 GB per day pays Chronicle roughly £146K on that rate, a bill that moves with data, not headcount. The meter you are on decides whether seats or data growth drive the invoice.

Flat-rate tiers

Panther sells tiered subscriptions: a fixed monthly fee covers a defined ingest ceiling, log retention period, and feature set. Cross the ceiling and you either upgrade tier or pay overage rates. Sumo Logic used to fit here too but has moved to its Flex credit model.

Wins when volume is predictable and growth is slow. The bill is genuinely flat for budgeting.

Loses when volume crosses the ceiling. Overage rates are typically 1.5-2x the in-tier per-GB equivalent. Tier upgrades create cliffs.

Worked example. Sumo Logic now sells Flex, which bills on data scanned and stored rather than ingest (ingest itself is free), so there is no clean per-GB-per-day headline and a 50 GB-per-day cost swings widely with query volume. Panther still sells true fixed volume tiers where the bill genuinely flattens inside the ceiling. For comparison, Splunk Cloud plus Enterprise Security at 50 GB per day runs roughly $100K all-in, and a fitting flat tier can sit noticeably lower. The discipline is monitoring usage against the ceiling before overage rates bite.

Same environment, four pricing models

Annual licensing only (no staffing or storage). Same log volume; different billing structure.

Model and vendorSmall (10 GB/day)Mid (50 GB/day)Enterprise (200 GB/day)
Per GB (Splunk Cloud + ES, all-in)$25K$100K$340K
Per GB (Sentinel)$16K$59K-$78K$200K
Per EPS (QRadar Cloud, est.)$28K$110K-$140K$440K-$560K
Resource-based (Elastic Platinum)$25K$95K$320K
Credit-based (Sumo Logic Flex, est.)$22K$80K$280K

Comparison assumes mixed log source profile, 365-day retention, and no negotiated discount. Splunk figures are all-in (base ingest plus Enterprise Security, which roughly doubles the base; mid-tier base ingest alone is ~$50K). QRadar publishes no list price, so those cells are modelled estimates. Sumo Logic Flex bills on data scanned and stored rather than ingest, so its figures are rough scan-dependent estimates, not a per-GB headline. Real-world deals routinely vary 20-40 percent either direction.

FAQ

Common questions

Which SIEM pricing model is most cost-effective?

It depends on your log mix. Per-GB pricing rewards organisations that filter aggressively and ingest mostly high-value security data. Per-EPS pricing rewards predictable, quiet sources but punishes bursts. Per-employee pricing rewards lean teams, since the bill tracks seats rather than log volume. Flat-rate tiers reward predictable volume that fits within a tier ceiling. Modelling your real log profile against each structure before signing matters more than picking a 'best' model in the abstract.

Why does Splunk charge per GB and QRadar per EPS?

Splunk's history is log analytics: their search engine scales by data volume, so per-GB billing aligned costs with the resource genuinely consumed. QRadar's history is correlation engine performance: their detection engine scales by event rate, so per-EPS billing aligned costs with the constraint that mattered. Both models survived because they roughly track the underlying cost driver, even though customers find one or the other easier to reason about depending on their environment.

How do I convert EPS to GB for vendor comparisons?

Rough conversions vary by source type. Windows event logs average 60-80 EPS per GB per day. Firewall and NetFlow data run 200-400 EPS per GB. SaaS audit logs run 30-50 EPS per GB. As a starting point, 1 GB per day of mixed enterprise log volume equates to roughly 70 EPS sustained. Sample your real environment for 30 days before locking in a per-EPS commitment; first estimates routinely understate by 30-50 percent.

Are flat-rate SIEM tiers cheaper than per-GB?

Within tier, often yes. Panther and Blumira flat tiers frequently undercut equivalent per-GB pricing while volume sits comfortably inside the tier ceiling (Sumo Logic no longer fits this camp: its Flex model bills scan and storage, not a flat tier). The risk is the cliff: cross the ceiling and you pay overage rates that can spike sharply. Flat-rate tiers work best for organisations with predictable, slow-growing volume and an alerting discipline that catches tier breaches before they become bills.

Updated 13 July 2026