Hyground vs
ilert
Hyground vs ilert: the investigation runs inside your cluster
ilert is a European alerting and on-call platform whose AI agents investigate from ilert's cloud, on models hosted in the EU when the customer is in the EU. Hyground installs into your Kubernetes cluster and reads the cluster API, Prometheus and Loki from inside it, on whatever model you point it at.
A fair starting point
ilert is a genuinely European option. Its AI runs on region-specific endpoints, and for EU customers the models are hosted in the EU, Anthropic through AWS Bedrock in an EU region. Every AI and agent action is logged, and the whole AI layer can be switched off account-wide, after which nothing is sent to an external model at all. It also does the things Hyground does not do: paging, on-call schedules, call routing with a voice agent, and status pages. The difference is location: ilert's agents reason in ilert's cloud, against the tools that you connect to them, and Hyground's agents reason inside the cluster that they are installed in.
Side by side
Hyground vs
ilert
at a glance
What matters
Hyground
ilert
Where it runs
Entirely in your own Kubernetes cluster, on-premises and air-gapped included.
In ilert's cloud. An on-premises agent, ilagent, relays events and reaches local systems.
Where the model runs
Wherever you point it, including a model you host yourself inside the cluster.
Region-specific endpoints. EU customers get EU-hosted models; other regions get US-hosted ones.
LLM choice
Any provider through LiteLLM: a cloud model in your own tenant, a self-hosted model, or any OpenAI-compatible API.
Models ilert selects for your region. The whole AI layer can be disabled account-wide.
Kubernetes and the observability stack
The cluster API, Prometheus, Loki, Elasticsearch, OpenSearch, Jaeger and InfluxDB, queried from inside the cluster. Our engineers build any other connector that you need with you during onboarding.
Whatever the agents reach through connected tools and MCP servers, from ilert's side.
Alerting, on-call and status pages
Not offered. Hyground takes the alert and hands findings back.
The core product: paging, schedules, escalation, call routing with a voice agent, and status pages.
What the agent changes
Nothing by default. Hyground diagnoses and recommends, and changes happen only if you enable them.
Agents reason, investigate and can act on incidents, with every action logged and traceable.
Your documentation and runbooks
Confluence Cloud and on-premises, up to 100 Git repositories, Artifactory and uploaded files, embedded inside your cluster.
Whatever the agents can reach through the tools and MCP servers you connect.
Pricing model
Priced on infrastructure size, not seats. Quote on request.
Per user.
Why teams choose Hyground
Where Hyground differs
Decision
When each platform fits
These solve different halves of an incident: an alerting and on-call platform with AI on top, and an investigation agent that lives in your cluster. They pair well.
Choose
ilert
when
Alerting, on-call scheduling, call routing and status pages are what you are buying first, you want the AI noise reduction and autonomous triage to sit inside that same platform, and what your compliance review wants to see is a European vendor with EU-hosted models.
FAQ
Hyground vs
ilert
:
common
questions
Is Hyground an alternative to ilert?
For the investigation, yes, and Hyground runs it inside your own cluster. ilert runs alerting, on-call and status pages, and its agents reason in ilert's cloud. Hyground does the investigating and hands the findings back to ilert.
Do we have to replace ilert?
No. ilert keeps paging the right person and running the incident process, the alert goes to Hyground, and what Hyground works out lands back in the incident.
Does our telemetry stay in our infrastructure?
With Hyground, yes. Hyground queries Prometheus, Loki, Elasticsearch, OpenSearch and the cluster API in place, and the only traffic that leaves is the call to the model provider that you choose, which can be a model that you host yourself. ilert's agents read your tools from ilert's side, so what they read passes through ilert's platform.
Can we choose the model, or host it ourselves?
Yes. Hyground connects to any LLM provider through LiteLLM, including a cloud model in your own tenant or a model that you host yourself. ilert selects the models and hosts them by region.
How do we get Hyground running, and what does it cost?
A forward deployed engineer works with your team from install to daily use. The engineer connects your stack, builds any connector that you are missing, and runs the training and workshops. Hyground is priced on the size of the infrastructure that it covers, not per seat, and you get a quote on request.