Storage Costs

See how much Monad saves you by filtering noise before it reaches your security storage destinations like Splunk, Snowflake, and S3. Monad removes redundant and low-value security data at ingress so it never reaches your destinations (learn more here).

Using your actual pipeline volumes and contracted storage prices, this page breaks down the costs you're avoiding.

You'll find the page at Settings → Storage Costs.

There are three tabs, each of which is explained in more detail below:

• Storage costs — a breakdown of volume and cost by storage type.
• Estimated totals — summary cards rolling everything up.
• Annual projection — a 12-month cumulative forecast.

The cost breakdown table

This table lists every active storage destination in your organization and shows the data volumes we've measured passing through your pipelines for a given time range.

Once you set prices, you'll see an estimate of the costs for filtered vs unfiltered data.

What you're seeing in the table

Each row represents one storage destination. The columns are:

Column	What it means
Storage type	The destination (e.g. Datadog, Splunk, S3).
Data volume at ingress	Total bytes flowing into Monad for this destination over the selected time range.
Data volume at output	Bytes actually delivered to the destination after Monad filtering.
Storage price per GB	Your negotiated per-GB rate for this destination. You set this yourself — see below.
Storage cost unfiltered	What you would have paid if all ingress data had been stored — i.e. without Monad.
Storage cost with Monad	What you're actually paying after Monad filters out noise.
Difference in cost	Percentage reduction between unfiltered and filtered cost.
Cost avoided	Dollar amount saved for this destination over the selected time range.

The final row sums every column into an organization-wide total.

Setting a price

Monad knows how much data you're sending to each destination but doesn't know what each destination costs you — those rates vary by contract. You set them yourself.

To set or change a price:

1. Click the price cell for the row you want to edit.
2. Enter a value, or use the slider to adjust.
3. Click the check button to save your changes.

The table will then be recalculated according to the new price.

Permission required

You need the Organization Write permission to edit prices. If you don't have it, the price field will be read-only. Ask an organization admin to grant the permission, or have them set the prices on your behalf.

Sorting

Click any column header to sort by that column. Click again to reverse the direction. The default sort is Cost avoided, descending — so the destinations where Monad is saving you the most money are at the top.

Here we have sorted the table by data volume, from largest to smallest:

Changing the time range

The range selector in the top-right controls the window over which volumes and costs are calculated. You can choose:

• 8 hours — recent activity, useful for spotting spikes.
• 24 hours — a full day.
• 7 days — a typical working week.
• 30 days — the default, and the most representative view for steady-state usage.

Changing the range recalculates every number on the page.

Estimated totals

Set at least one price first

This tab is only enabled once you've set at least one storage price. Until then, there's no dollar value to total up. Set prices on the Storage costs tab first.

The second tab rolls the per-destination numbers into three summary cards:

• Storage cost unfiltered — what you'd spend without Monad.
• Storage cost with Monad — what you're actually spending.
• Total savings — the difference, shown with a percentage ring visualizing the proportion saved.

You can vary the range here too if you want to see how costs look for a shorter time frame:

Annual projection

Set at least one price first

Like Estimated totals, this tab requires at least one storage price to be set.

The third tab projects your current 30-day costs out over 12 months. You'll see:

• A cumulative bar chart showing unfiltered cost, filtered cost, and savings month by month.
• Summary cards with the full 12-month totals.

The projection always uses a 30-day window as its basis — if you were viewing a different range on the Storage costs tab, the page will automatically switch to 30 days when you open this tab so the projection stays consistent.

How prices and data work

A few details worth knowing:

• Volume data comes from your actual pipeline traffic — there's nothing to configure.
• Prices are per-organization — everyone in your org sees the same numbers.
• Cost calculations account for ingested volume, the number of outputs that volume would have fanned out to, and your configured price per GB. A single pipeline often sends the same input data to several destinations, so filtering at ingress avoids that data being stored once per output — which is why savings can be substantial even when the ingress volume looks modest.
• Destinations shown are those your pipelines have delivered data to within the selected time range. If you don't see a destination you expect, try widening the range.

FAQ

Why are the Estimated totals and Annual projection tabs disabled?
You haven't set any storage prices yet. Once at least one price is in place, both tabs become available.

Why is one of my destinations missing?
The table is scoped to your current time range. If a destination isn't showing, try widening the range.

Why can't I edit prices?
You need the Organization Write permission. Contact an org admin.

Can I see historical cost trends?
Not yet — today the page shows costs over a single chosen time window. Trend views are on the roadmap.