Billing, simplified - from CPU cores to captured volume
Since the first license management UI, Spider licences have been priced on CPU: you prepaid a number of cores, usage was sampled every 20 seconds across the whole system, and anything above your prepaid cores billed as pricier “extra” cores. It worked, but it was never a great fit.
Why CPU never quite worked
Core usage depends on your infrastructure as much as on how much you actually use Spider - a slower cluster or a heavier query pattern moved the number around without anything meaningful changing on your side. It was also hard to predict up front, and migrating between setups needed care, since prepaid cores always counted against whichever setup was more expensive.
Billing on volume instead
Spider now bills on the one metric that maps directly to value delivered: how much traffic you capture in a year, in terabytes. You commit an annual TB pool, and that’s it - no per-core metering, no per-seat fees, no guessing at cluster overhead.
Pricing is a simple ladder, each band’s rate applying only to the terabytes within it:
| Annual volume | Price per TB (ENTERPRISE list) |
|---|---|
| First 100 TB | €100 |
| 100 – 500 TB | €80 |
| 500 – 1,000 TB | €60 |
| 1,000 – 2,500 TB | €50 |
| 2,500 TB+ | Contact us |
| Above your pool (overage) | €120 |
TEAM licences take a flat −25% off every band, including overage. There’s a minimum annual licence of €3,000 (ENTERPRISE) or €1,000 (TEAM), so very light usage still has a predictable floor rather than an unpredictable near-zero bill.
You can estimate your own pool - and see the full band-by-band breakdown - on the Pricing page.
Cheers, Thibaut