Meet Vizzy
by VisiCoreYour AI. Your Splunk. Your Cribl.
Actually connected.
VisiCore’s AI harness for Splunk and Cribl. Vizzy works across your environments. Upskill everyone. Talk to your infrastructure.
- Cross-platformCribl route → Splunk index → license $, in one answer.
- Read + writeNot a chatbot over docs. Vizzy discovers, correlates, dry-runs and deploys.
- Audit trailEvery task lands in your X10 service board: findings, diffs and deploy notes, reviewable by your team.
How Vizzy works
Where the harness sits
Vizzy is the harness between your AI and your live systems. It supplies context, memory, guardrails and the engineering discipline, then drives the same CLI tools our engineers use every day.
- Web
- Slack
or VisiCore credits
- 01You ask
From the portal or Slack. Plain English, no SPL or JavaScript required.
- 02Vizzy plans
Pulls context from your KB, docs and past tickets. Proposes a plan and asks for approval.
- 03Tools act
vct-cribl-cli and vct-splunk-cli read the live state, dry-run the change, then write once confirmed.
- 04Ticket closes
Findings, diffs and deploy notes land in the X10 ticket. Your team can review every step.
The value of connection
Your AI + a harness + live Splunk & Cribl = actionable answers
Try asking
Questions Vizzy answers with ground truth
Ask about ingest volume, Cribl routing, ticket status and license usage. Configure sources, routes, pipelines and destinations. Open tickets and request service.
Chat with Vizzy ↗- License
“Which source is driving our Splunk license this week?”
- Routing
“Show me every Cribl route that lands in the firewall index.”
- Splunk Apps
“Is the CriblVision app installed on our search head? What version?”
- Indexes
“Check index retention for anything over 90 days and tell me the cost.”
- Account
“Schedule 30 minutes with our account manager next week.”
- Change
“Add a Drop function for debug events on the k8s pipeline. Dry-run first.”
Vizzy is an AI consultant that acts directly on your environment. Verify its changes and findings there, and treat the ticket notes as the record of what was actually done.
See it work
The CLI under the harness, on a real Cribl stack
Short demos of vct-cribl-cli driven by Claude Code. Vizzy uses the same tools, with the guardrails and ticket trail on top.
- Vizzy · CLIVisiCore's Cribl CLI mapped my entire Cribl stack in 23 seconds
- Vizzy · CLIUsing VisiCore's Cribl CLI + Claude Code
- More on our YouTube channel ↗
AI-enhanced service delivery
Bring your own AI. We make it work with your Splunk & Cribl.
Modular CLI tools in your local harness for Splunk and Cribl, Cloud and Enterprise. Open source.
Custom agents, integrations and automations for your Splunk and Cribl, built with the AI you already have.
Scope a projectAvailable to subscription and managed clients on the web and Slack. Your AI key or VisiCore credits, with a VisiCore engineer as the human backstop on every ticket.
Open the portal ↗FAQ
Straight answers
See Vizzy on your data
Thirty minutes, your Cribl and Splunk, real questions. We’ll show you what a connected harness changes.