VisiCore AI — Extending X10
X10 Dividend

Assess

An automated scan that turns a diagnostic bundle into quantified savings — priced at a share of what it finds.

Observability and security data costs keep climbing. Platform spend grows quarter after quarter. Every budget owner asks the same question: which of these dollars can I get back, and how? They rarely get a direct answer. Assess answers it, in dollars.

Assess is the front door of X10 Dividend. It reads a diagnostic bundle. It measures the savings in dollars. Then it hands back a report a finance team can act on. Your data pays you back, and this is where we measure the payment.

The core scan runs the same way every time — no AI involved. No AI touches customer data before a person approves it. The findings come from repeatable processors, not a model's guess.

The front door: the savings calculator

Most engagements start before anyone uploads a bundle. The savings calculator takes a few facts about an environment: daily ingest volume, main source types, and yearly spend. It returns two numbers. One is what the assessment costs. The other is what we expect it to recover.

The calculator is a simple lookup against measured reduction benchmarks. It runs the same way every time. You submit nothing, we analyze nothing, and a security team has nothing to review. It exists to show the size of the prize before anyone commits.

Run the numbers first

The calculator estimates cost and recovery from a few inputs. It is the easy way to start.

The automated scan

When a customer is ready, they connect Cribl or upload a Splunk or Cribl diagnostic bundle. Two processors read the bundle: one for Splunk, one for Cribl. Each turns the bundle into clear findings. This stage is pure automation — no AI. The same bundle gives the same findings every time.

Assessment flow: a diagnostic bundle is uploaded, sanitized by fixed rules, scanned with no AI in the path, reviewed by a senior engineer, and delivered as a branded savings report

Upload or connect

The customer gives us a diagnostic bundle or connects their Cribl environment. We need no write access to production.

Sanitize

Sanitization strips sensitive values — secrets, hostnames, and IDs — before any model runs. It is a fixed step, not an AI judgment call.

Scan

The processors turn the sanitized bundle into findings: savings, settings to tune, and risk. Each one carries a dollar figure you can measure.

Review

A senior engineer checks the findings against the environment. Optional AI help from Vizzy speeds up the write-up. It runs only after sanitization, and only on data a person has cleared.

Report

The reviewed findings become the branded savings report.

Sanitization is a fixed step that runs first. So Assess is the easiest offering to clear a customer security review. There is a clear, auditable answer to "what leaves our environment?"

The branded report

The report is built for the person who signs off on the spend, not just the engineer who runs the platform.

Executive summary

The bottom line in plain words: total savings found and the expected yearly recovery.

Quantified savings in USD

Each finding carries a dollar figure. The report totals what the current setup can hand back.

Risk posture

Bad settings and compliance gaps show up next to cost, so you read risk and spend together.

Remediation steps

Every finding maps to a clear fix. That is where Remediate picks up.

What a finding looks like

The scan finds savings you cannot see in a monthly bill but that are obvious once measured. One source type using a quarter of indexer CPU is exactly what the processors flag. It is a big, costly problem that no one watches, because the standard tools never point at it.

Named, dollar-for-dollar proof from live environments lives on the benchmarks page.

The pricing

The assessment costs 25% of the savings we deliver each year. The customer pays a share of measured recovery. It is not a flat consulting fee cut off from the result. It is not a share of a guess either. The fee rests on savings we actually deliver. So the incentive lines up on both sides: the more savings the scan finds and Remediate recovers, the more both sides gain.

This matches VisiCore's founding model: map the data flows, prove the savings, and get paid on the result. Assess turns the "prove the savings" step into a repeatable product.

Where it leads

Assess is one part of a loop. The findings it measures become real dollars in Remediate, and Monitor keeps the savings from slipping back.

On this page