OEM / White-label feed
Our intelligence, inside your product.
For security product companies, MSSPs, and data platforms that put prioritized vulnerability intelligence in front of their own customers. You are not buying seats — you are licensing data rights and scalable API consumption.
The unit of measure
One Feed Unit.
One API request returning up to 250 CVE records is one Feed Unit. Each additional block of up to 250 returned records counts as one more. A request returning 1,000 CVEs is four Feed Units.
Counting both requests and returned records means heavy payloads are measured fairly.
| Request | Charged |
|---|---|
| 1 request → 250 CVEs | 1 Feed Unit |
| 1 request → 1,000 CVEs | 4 Feed Units |
| 1 request → 1 CVE | 1 Feed Unit |
How it is packaged
Four shapes of engagement.
Tiers are sized by polling frequency and payload volume, and by how many downstream customers, tenants, or product lines the feed serves.
Starter
A single product integration or a low-frequency MSSP workflow. Sized for roughly 30-minute polling.
Growth
Most commonA high-frequency integration or several moderate downstream keys. Sized for roughly 5-minute polling.
Scale
Larger MSSP or security product workloads with heavier polling, many downstream keys, and multi-tenant use.
Enterprise
High-volume platforms, dedicated infrastructure, custom SLAs, bespoke data packaging, or complex redistribution terms.
Feed licensing is scoped per engagement. Tell us how your product consumes the data and we will size it with you.
Sizing reference
How often will you poll?
The fastest way to land on a tier is to start from your integration's polling interval.
| Polling frequency | Calls / day | Calls / year | Typical tier |
|---|---|---|---|
| Every 30 minutes | 48 | 17,520 | Starter |
| Every 15 minutes | 96 | 35,040 | Starter + usage pack, or Growth |
| Every 5 minutes | 288 | 105,120 | Growth |
| Every minute | 1,440 | 525,600 | Enterprise / custom |
Common questions
What partners ask before they sign.
Why not price this per customer?
For OEM and white-label use, a single API call can serve many downstream customers. Usage-based Feed Units are more transparent, and far easier for both sides to track.
Why does returned CVE volume count?
One request returning 1,000 records creates more data value and more platform load than one returning a single CVE. Feed Units account for heavy payloads without penalizing normal delta polling.
Can we cache the data?
Caching and retention are contract-defined. Short-term caching for performance is generally workable; redistribution, derived datasets, and post-termination use need explicit terms.
Can we start smaller?
Start on Starter for 30-minute polling or a limited integration, then move up when you need 15-minute or 5-minute updates.
Decide what matters. Before it decides for you.
Start on the free community edition, or talk to us about an enterprise license, CT monitoring, or an OEM feed for your product.
No card required. The community edition is free.