Executive Summary

On July 30, DataBahn, a startup based in Dallas, Texas, raised a $40 million Series B. Insight Partners led the round, which follows a $17 million Series A in June 2025. The company does not build smarter models. It sells the pipeline that sits between the 600-plus sources pouring out logs, events, and metrics and the tools that consume that data—ingesting it, shaping it, and routing it to where it needs to go.

What changed is who is lining up to take that data. Telemetry was traditionally consumed by security platforms (SIEM) and data warehouses; now AI agents and copilots have joined the same line. But an agent does not want raw logs—it wants the context it needs to decide and act. That is why DataBahn calls itself an "agentic data control plane."

This piece looks at where that $40 million points. For anyone who works with data, the investment translates into a single question: is AI-ready data the output of a batch job you run once, or an always-on infrastructure layer that has to normalize, route, and record data at every moment?

The Numbers

Source: SiliconANGLE, 2026-07-30

Four figures compress the backdrop to this round: the size of the Series B, the number of sources a single pipeline connects, revenue growth over the past year, and the rate at which customers who evaluated the product went on to sign.

$40M

Series B

Led by Insight Partners, $59M raised to date

600+

Connected sources

Logs, events, and metrics through one pipeline

400%+

YoY revenue growth

180% NRR · zero customer churn

97%

PoC win rate

Evaluations that converted to contracts

1

Agents Joined the Telemetry Line

Start with the deal. DataBahn was founded in Dallas in 2024. This $40 million Series B was led by Insight Partners, with participation from Forgepoint Capital, GTM Capital, and S3 Ventures. It follows a $17 million Series A led by Forgepoint in June 2025, bringing total funding to $59 million. The company says it will use the money to expand R&D and to broaden a customer base that has so far clustered among Fortune 100-scale enterprises, reaching down into the mid-market.

DataBahn official company logo
▲ DataBahn, which raised $40 million in a Series B | Source: PR Newswire

What DataBahn does fits in one sentence. It sits between the 600-plus sources that generate logs, events, and metrics and the tools that consume them, and it ingests, normalizes, and routes that data. Information the destination does not need gets stripped out along the way. The company calls this position an "agentic data control plane," and it sells its neutrality—any source, any destination, any model, tied to no particular vendor—as the pitch.

600+ sources Logs Events Metrics DataBahn Agentic data control plane • Ingest · Normalize • Route · Drop unneeded data • Cruz AI — auto-generated parsers/mappings Change & routing records (governance) Destinations SIEM · security Data warehouse AI agents (new) Alongside traditional consumers (SIEM, warehouse), AI agents join the same data line
▲ Original Pebblous diagram — DataBahn's control plane sitting between sources and destinations

Why this position gets priced now becomes clear on the destination side. Until recently, telemetry went to security platforms and analytics tools. Now AI agents, copilots, and autonomous applications stand in the same line demanding data. At the same time, the cost of collecting, moving, storing, and processing data is rising on every front—cloud bills, storage, inference, and sheer data volume all climbing together. Where the old "move everything everywhere" architecture stops being affordable, demand concentrates on a layer that filters data and forwards only what fits.

What DataBahn sells is not new data but the junction the data passes through. As sources grow toward 600 and agents pile onto the destination side, the position that shapes and directs the flow between them gets more valuable. The value comes not from the volume of the data but from the location.

2

What Agents Want Is Context

Here we need to draw a distinction. The data a SIEM wanted and the data an agent wants are different in kind. Security analytics tools pile up as much raw log as possible and dig through it after the fact. An agent, by contrast, does not just produce an answer—it acts on that answer. So it needs not a heap of raw logs but context it can use immediately to decide and act: current, structured, and backed by evidence that the data is trustworthy.

DataBahn's way of manufacturing that context is automation. The company's "Cruz AI" is an agentic data engineer that takes over the integration and parsing-rule work people used to do by hand. It watches the schema of incoming data, detects when a source's format changes, and generates updated parsers and mappings on its own for a human to approve. A human keeps the final call (human-in-the-loop), but the burden of manually chasing 600 sources whose formats shift by the day is lifted.

A line from CEO Nanda Santhana compresses the product's premise: "AI is only as good as the enterprise data it can understand." However capable the model, if the data reaching it is a tangle of raw logs, the quality of its judgment is capped at that level. The control plane is therefore more than plumbing. It decides what an agent can see and records how data was changed and routed—a governance function that carries particular weight in regulated industries.

3

From a Batch Job to Always-On Plumbing

This is where things get genuinely important for people who work with data. Many organizations have treated "AI-ready data" as a project. Gather the data once, clean it, label it, get the quality right, and you are done—the mindset of a batch job. But once agents demand data at every moment and act on it immediately, data quality stops being a one-time deliverable and becomes a state that keeps running.

Where data quality sits is moving Batch job (before) A deliverable cleaned once Provenance: logged once, at cleaning time Normalization: fixed by upfront schema Routing: destination set in advance Owner: data pipeline team (a project) Agent era Always-on plumbing (runtime control layer) A state that runs at every moment Provenance: recorded on every change/route Normalization: detect format shifts, auto-regen Routing: per-destination shape, in real time Owner: control-plane operations (always-on)
▲ Original Pebblous diagram — provenance, normalization, and routing moving from a batch deliverable to an always-on operational responsibility

This shift changes who owns three things. First, provenance stops being metadata written once at cleaning time and becomes a record that continues every time data is changed and routed. Second, normalization stops being a schema you design and freeze upfront and becomes the work of detecting a source's format change and re-fitting it each time. Third, routing stops being a setting that fixes the load destination in advance and becomes a real-time judgment about which tool needs which shape right now.

DataBahn's customer stories make the transition concrete. Parrish Gunnels, CISO of MVB Bank, said the company was able to fold regulatory requirements, audit controls, and validation processes into a single cohesive solution—lowering cost and freeing staff to move to governance and oversight work. Ricardo Henry, security architecture lead at the Canada Pension Plan Investment Board (CPPIB), said that onboarding a single new log source used to require custom integration and significant engineering time, with no way to even confirm whether critical systems were actually sending logs. With DataBahn providing a standardized, repeatable onboarding approach, coverage gaps became far easier to find.

When data quality moves from batch to runtime, it becomes operations rather than a project. Not a cleaning you finish once, but something you keep watching and keep fixing. At that moment provenance, normalization, and routing stop being a task the data team handles each quarter and become an infrastructure layer someone owns continuously.

4

A Genuinely New Layer? The Cribl Question

Here an honest doubt deserves a hearing. Is an "agentic data control plane" a genuinely new layer, or a rebranding of the existing telemetry pipeline? It is a question the industry keeps putting to DataBahn. Companies that collect, route, and store data already exist. Cribl, most notably, was founded in 2018 and has become an incumbent in IT and security data management; in August 2024 it raised $319 million in a Series E, pushing total funding past $700 million. It is the leader of an adjacent category with far deeper capital than DataBahn.

The competitive map is not settled either. Observo AI, an independent rival in telemetry management and threat detection, exited the standalone category when SentinelOne acquired it in September 2025. Splunk and the large cloud and security vendors all route and store data too. So DataBahn is in the position of having to prove for itself that the "agentic data control plane" is a real, distinct category rather than a rebrand. The way the company leans so hard on vendor neutrality and cross-platform independence reads as an attempt at differentiation along exactly that boundary.

The very fact that the boundary is blurry is a signal that the category is still forming. But still forming and lacking substance are not the same thing. As agents newly join the consumer side, the burden of deciding in real time "in what shape, when, and to whom to send the data" has genuinely grown, and capital is concentrating on a layer dedicated to that burden. Whether it ends up as an extension of Cribl or a new DataBahn category, the trend—that this position is getting priced—is clear.

5

What a Data Quality Team Now Needs

Step back and DataBahn's $40 million is a signal that goes beyond one company's success story. Several industry analyses find that while most enterprises have experimented with AI agents, the share that scaled to measurable value is still low. The bottleneck repeatedly named is not the model's reasoning ability but data quality and governance. That is why bolting on a few more agents does not produce results. If clean data in the right shape does not reach each agent in time, even the smartest model stalls in front of tangled input.

It is no coincidence that the phrase "control plane" is surfacing in several places at once. Gartner has proposed the Agent Management Platform (AMP) concept as a central hub sitting above the agent execution layer, where governance, performance, and value converge, and Microsoft's agent-management product likewise positions itself as a control plane that discovers and secures agents wherever they run. What DataBahn aims at, among these, is the layer that handles the data agents feed on. Alongside the layer that controls agents' execution permissions, which drew capital earlier, the layer that controls the data going into agents is now hardening into infrastructure as well.

The concern Pebblous has been raising with AI-ready data sits at exactly this spot. Ready is not a state you reach once and are done with. Every time a source's format changes, a destination's required shape shifts, or a new agent demands new context, the data has to be normalized again, routed again, and recorded again. What a data quality team needs is not a batch pipeline team that cleans data each quarter, but the capacity to watch the junction where data flows and treat provenance, normalization, and routing as operations. DataBahn's round is a signal that this capacity is starting to be priced. Models have already become expensive; the work of forwarding the right data to them, in the right shape, is only now starting to become expensive too.

R

References

Industry Coverage

Official Sources

  • 4.PR Newswire. (2026). "DataBahn Raises $40 Million Series B Led by Insight Partners." Press release.
  • 5.Gartner. (2026). Agent Management Platform (AMP) — the concept of an operational control plane above the agent execution layer.
  • 6.McKinsey. (2026). Research on enterprise AI agent scaling — naming data quality and governance as the reason the share scaling from experiment to measurable value is low.