Integrations

Every system you run, integrated

Hyground wires into your existing cloud, Kubernetes, observability, ticketing, and chat tools. Read-only by default, verified at startup, every credential stays inside your cluster.

Read-only by default. Verified at startup

Hyground ships read-only adapters for the tools your team already runs. 21 of them, across 11 categories.

01 · CLOUD

Cloud platforms

AWS
Azure
GCP

02 · ORCHESTRATION

Kubernetes

Cluster API
Custom CRDs (Argo, Prometheus, Traefik)

03 · TELEMETRY

Logs, metrics, traces

Prometheus
InfluxDB
Loki
OpenSearch
Elasticsearch
Jaeger

04 · STORAGE

Databases

PostgreSQL
MongoDB
ClickHouse
Redis

05 · WORKFLOW

Tickets and code

Jira
ServiceNow
GitHub
GitLab

06 · KNOWLEDGE

Knowledge sources

Confluence
Git repositories
Artifactory
File upload (PDF, DOCX, MD, TXT)

07 · COMMUNICATION

Email and chat

Microsoft 365
IMAP/SMTP
Slack
Microsoft Teams

08 · INTELLIGENCE

LLM providers

Azure OpenAI
Anthropic Claude
Google Gemini
AWS Bedrock
Local via Ollama or self hosted

Our adapters refuse to start if the principal can write

Read-only is enforced at startup, not promised in a policy document. Five scoped-write surfaces (Jira, ServiceNow, GitHub, GitLab, email) can be sandboxed with a single flag.

How integrations work

Tokens you paste once. Adapters that wrap tools you already trust. Model providers and MCP servers you can swap.

Each adapter runs in your cluster

Adapters live in the Hyground namespace inside your infrastructure. Credentials never leave. Hyground never sees them.

Hardened wrappers around tools you already trust

Cloud and Kubernetes adapters wrap aws, az, gcloud, kubectl, gh, glab inside a hardened shell. Database adapters use the read role you create.

Pluggable model providers

Run Hyground on Azure OpenAI, Anthropic, Gemini, or Bedrock via a LiteLLM chain. Primary plus fallback. No model lock-in.

Bring your own MCP server

If you already run MCP servers in-cluster, Hyground can call them as adapters alongside its own.

Anything that speaks JSON, integrates

Herald is Hyground's external-notification gateway. Producers without a dedicated adapter wire up the moment they can POST JSON to one URL.

One URL, any producer

A single endpoint accepts free-form JSON. Alertmanager, Grafana, PagerDuty, Datadog, cron, curl: anything that speaks JSON wires up the moment it can POST.

An LLM decides what matters

Two LLM checks read the payload. Real alerts trigger an investigation; the rest gets summarised. No per-source adapter code.

Two layers of defence

Authentication decides who can call the endpoint. An LLM check decides what reaches an agent. Producers get an immediate acknowledgement; investigation runs in the background.

See Hyground in action

Check out our sandbox or schedule a demo with our team and experience sovereign AI for DevOps firsthand.

Try our sandbox Book a demo