Hyground vs
Hyground vs Datadog Bits Investigation: read every source, not one vendor's
Bits Investigation is Datadog's autonomous agent. It reasons from inside Datadog, and it now pulls Grafana, Dynatrace, Splunk and Sentry in alongside. Hyground works the other way. It installs into your cluster and queries your observability stack, your cloud accounts, your wikis and your code from there.
A fair starting point
Datadog renamed Bits AI SRE to Bits Investigation, and inside the Datadog estate it is a strong product: it forms a hypothesis, pulls the telemetry, reasons over it and names a root cause. It reads runbooks out of your monitor messages or a linked Confluence page, takes environment context from a bits.md file, and integrates GitHub, Grafana, Dynatrace, Splunk, Sentry and ServiceNow. So the old objection, that it only sees what Datadog ingests, no longer stands. What has not changed is where it lives. It is Datadog's service, running in Datadog's cloud, on a model Datadog chooses. Hyground runs inside your cluster, reads whatever you already run, and leaves the model choice to you.
Side by side
Hyground vs
Bits Investigation
at a glance
What matters
Hyground
Bits Investigation
Where it runs
Entirely in your own Kubernetes cluster, on-premises and air-gapped included.
In Datadog's cloud, as part of the Datadog platform.
Where your telemetry goes
Nowhere new. It is queried in place, and the only traffic leaving is the call to your model provider.
Into Datadog, which is where the investigation reasons from. Third-party sources are integrated alongside it.
LLM choice
Any provider through LiteLLM: a cloud model in your own tenant, a self-hosted model, or any OpenAI-compatible API.
Datadog selects and operates the model. Their documentation describes no customer choice.
Sources it reads
Prometheus, Loki, Elasticsearch, OpenSearch, Jaeger, InfluxDB, the cluster API, cloud accounts, databases, Jira and ServiceNow.
Datadog telemetry, plus GitHub, Grafana, Dynatrace, Splunk, Sentry and ServiceNow.
Observability platform
None. Hyground reads your tools and stores nothing.
A full observability platform underneath the agent, with its own metrics, traces, logs and profiling.
Your documentation and runbooks
Confluence Cloud and on-premises, up to 100 Git repositories, Artifactory and uploaded files, embedded inside your cluster.
Runbooks in the monitor message or a linked Confluence page, plus a bits.md context file in preview.
What the agent changes
Nothing in your infrastructure. Hyground diagnoses and recommends.
Recommends remediation, delivers findings to Jira and ServiceNow, and can generate a code fix through Bits Code.
Pricing model
Priced on infrastructure size, not seats. Quote on request.
AI Credits, in bundles of five hundred a month on commit or on demand, resetting monthly with no rollover, on top of the platform.
Why teams choose Hyground
Where Hyground differs
Decision
When each platform fits
If your observability already lives in Datadog, their agent starts from inside the data and that is a real advantage. If it does not, or if the agent has to stay inside your perimeter, the calculation changes.
Choose
Bits Investigation
when
Your observability already lives in Datadog. You want the agent that reasons from inside that data, with the whole platform underneath it. And one more line on the Datadog renewal is the procurement path you prefer.
FAQ