Remediate
The platform CLIs turn assessment findings into realized savings — dry-run first, engineer-approved.
A report full of findings that nobody acts on just sits on a shelf. The hard part of cost recovery is not finding the savings — Assess does that. The hard part is capturing them without breaking the environment. That means work across dozens of pipelines and source types, under a change-control process that makes every edit slow.
Remediate closes that gap. Findings map to actions, and the platform CLIs (command-line tools) run those actions in a fraction of the usual hours.
The platform CLIs
Two command-line tools do the work: vct-cribl-cli and vct-splunk-cli. Each
strings together vendor API calls from start to finish. So a finding like "drop
null fields from these logs and re-route them" becomes a clear, reviewable set
of API steps. No afternoon of clicking through a GUI.
vct-cribl-cli
Covers the full set of Cribl Cloud REST resources. Mature and in active use on live engagements today.
vct-splunk-cli
The Splunk version. Works from start to finish. We are hardening it for enterprise use before its first client engagement.
The CLIs run the same way every time — no AI involved. They run vendor API calls exactly as told. They never improvise. AI helps only upstream, where it drafts the intent, covered under Playbooks. The execution layer itself is plain, auditable automation.
Dry-run first, engineer-approved
Every change runs as a dry run first. A dry run previews the change but applies nothing. The engineer reviews the preview — the exact steps, against the customer's real setup — and only then approves it. Nothing runs on a customer environment that a person has not read and cleared.
Finding
A measured finding from the assessment report — a specific, priced problem.
Compose
The finding maps to a fix, built as a set of CLI steps against the vendor API.
Dry run
The CLI previews every change without applying it. The engineer sees exactly what would happen.
Approve
A senior engineer approves the change against the real environment and its security setup. This gate is not optional.
Execute
The approved change runs. The savings the assessment priced become a real reduction on the bill.
Findings become real savings
This is the step where the assessment's dollar figures stop being a guess. Assess measures the savings. Remediate captures them. The difference is real, recurring savings on the next bill.
That link is also what the pricing rests on. The Dividend assessment costs 25% of the savings we deliver each year — and we deliver them here, in Remediate. We never charge the fee against a number on a report. We charge it against savings this step has actually delivered.
A cut upstream keeps paying downstream. Trimming volume before it reaches the indexer cuts the ingest cost and every per-GB cost after it. So one well-placed fix shows up in more than one line of the bill.
What exists today, stated plainly
We describe the tools as they are. The Cribl CLI is production-grade. The Splunk CLI works and is being hardened. We do not inflate either claim to make the story cleaner.
Where it fits
Assess
Where the findings and their dollar figures come from.
Monitor
Keeps the recovered savings from slipping back.
How the AI drafting works
The Playbooks initiative covers the AI layer that drafts intent before the platform CLIs run it.