Credits and Usage
This page only applies if you're on the Flex Intelligence Credits (FIC) model. If you're not sure which model you're on, check your Order Form or ask your customer success representative.
SenseOn uses a credit-based model to measure and report on platform consumption. This article explains how to read your usage data and what to do if you approach or exceed your allocation.
Credits Dashboard
The credits dashboard shows:
- Credits used: the number of credits your organisation has consumed
- Allowance: your organisation's allocated credit ceiling
- Breakdowns: various views that help you see what's using the most credits
Contact your customer success representative if you anticipate sustained overage.
What Consumes Credits
Everything you use on the SenseOn Platform draws from a single pool of credits. This section explains which features use credits and how many.
Check your contract. Some agreements differ slightly or don't include all the features listed here.
Data pipelines
Ingesting and storing data uses credits. The amount depends on how much data you send and how long you keep it.
| Pipeline | What we measure | Credits |
|---|---|---|
| Edge Processing | GB of raw data ingested per day, before any filtering | 0.25 per GB |
| Detection & Response Pipeline | GB per day that reach detection, after filtering at the edge | 1.25 per GB |
| Observability Pipeline (warm storage) | GB multiplied by months of retention | 0.08 per GB per month |
| Compliance Pipeline (cold storage) | GB multiplied by months of retention | 0.03 per GB per month |
Filtering data at the edge lowers what reaches the Detection & Response Pipeline, so it lowers your credit use. For example, if you send 100 GB of raw data in a day and 40 GB remains after filtering, Edge Processing uses 25 credits and the Detection & Response Pipeline uses 50 credits.
Resolve
Resolve uses credits only when it closes a case on its own, with no human involvement. If a case is escalated to a person, there's no charge. The amount depends on the severity of the case.
| Case severity | Credits per case |
|---|---|
| Low | 1 |
| Medium | 2 |
| High | 3 |
| Critical | 5 |
Hunter
Each new hunt query that Hunter generates uses 2 credits. Refinements to a query aren't charged. A single conversation can generate several new queries, so it can be charged more than once. Hunts that Resolve runs as part of a case investigation aren't charged separately. Queries run by SenseOn analysts aren't charged either.
Insight
Each report or briefing that Insight delivers uses 25 credits.
Forge
Each new custom detection you create with Forge uses 25 credits. Drafts aren't charged.
Summary
| Feature | What triggers a charge | Credits |
|---|---|---|
| Edge Processing | Raw data ingested | 0.25 per GB |
| Detection & Response Pipeline | Data reaching detection | 1.25 per GB |
| Observability Pipeline | Warm storage | 0.08 per GB per month |
| Compliance Pipeline | Cold storage | 0.03 per GB per month |
| Resolve | Case closed autonomously | 1 to 5 per case |
| Hunter | New hunt query generated | 2 |
| Insight | Report or briefing delivered | 25 |
| Forge | New custom detection created | 25 |
Managing Consumption
If you are consistently approaching your limit:
- Filter out high-volume, low-value logs before they reach SenseOn. See Log Ingestion for guidance.
- Discuss increasing your credit allocation with your SenseOn account manager.
Contacting Support
For billing queries or to request a credit allocation review, contact support@senseon.io or speak to your dedicated customer success representative.