Grow Splunk revenue in your accounts. Fleak brings the data.
Fleak is a managed data pipeline that brings customer data into Splunk and runs the work for the customer. It fits two situations: accounts that pay for Cribl, and Cisco hardware whose telemetry isn’t in Splunk yet.
“If you run Cribl or Cisco hardware, Fleak can bring that data into Splunk and handle the work. I’d like to introduce them.”
Cribl accounts: move the spend to Splunk
Fleak replaces Cribl Stream. Retention moves from Cribl Lake to Splunk Machine Data Lake. About three months.
Details → 02 / Turn it onCisco hardware: new Splunk ingest
AI POD, UCS, Unified Edge, Nexus, Catalyst, Secure Firewall and Meraki telemetry in Splunk, without a connector project.
Details →Move Cribl spend onto the Splunk order.
Customers pay Cribl for routing (Stream) and retention (Lake). Fleak takes over the routing, and retention moves to Splunk Cloud and Machine Data Lake.
Today’s Cribl routes are rebuilt in Fleak and run side by side.
Same events, same alerts on both sides before anything switches.
One flow at a time. History moves into MDL. Cribl is retired.
70 TB a day on Cribl Stream + Lake, modeled as a managed Splunk MDL package.
Annual, modeled at list prices. In evaluation with the Splunk account team. Name withheld.
Cisco hardware telemetry, live in Splunk.
Each device family usually needs its own connector and dashboards, so these projects stall. Fleak reads Cisco telemetry directly and turns on the Splunk dashboards. It is ingest the customer doesn’t send to Splunk today.
Watch on YouTube: Fleak routing Cisco OT telemetry to Splunk and S3. Fleak is the data fabric in the Cisco Secure AI Factory reference architecture, with Splunk as a destination.
Fleak is a managed data pipeline that brings customer data into Splunk and runs the work. For a Cribl customer, Fleak moves that spend to Splunk in about three months. For a customer with Cisco hardware, Fleak turns the telemetry into Splunk dashboards. Refer the account to partner@fleak.ai to grow the Splunk revenue.
Common questions
Doesn’t Splunk Edge Processor already do this?
Edge Processor filters data on its way into Splunk. It doesn’t rebuild Cribl routes, keep feeds to Elastic and other tools, or onboard new Cisco device families without a connector project. Fleak covers those cases, and the data still lands in Splunk.
Is Fleak a Splunk competitor?
No. Fleak moves data. It doesn’t store or search it.
Does Fleak eat into Splunk ingest?
No. Fleak is priced on compute, not data volume, so it doesn’t compete with Splunk ingest for budget.
Where does it run?
In the customer’s cloud account or on Cisco UCS in their data center. The data stays in their environment.
How does the customer buy it?
Migration work goes through Cisco services today. A Fleak SKU on the Cisco price list is coming.
Send the account to Fleak.
Fleak handles the scoping, the savings model and the work.
To: partner@fleak.ai Subject: Account for Fleak: [customer name] Customer: [name] Angle: Cribl move / Cisco gear What I heard: [e.g. Cribl renewal in Q2] Me: [your name, team, region]