Hyground
Hyground GmbH (Hamburg, Germany) builds a sovereign, self-hosted AI SRE (Site Reliability Engineering) agent for European enterprises. The multi-agent platform deploys as a Kubernetes-native Helm chart inside the customer's own perimeter and correlates Kubernetes, observability (Prometheus, Loki, Elasticsearch), cloud (AWS/Azure/GCP), CI/CD, and ticketing data to produce evidence-backed root cause analysis, autonomous incident response, and scheduled operations work such as CVE blast-radius mapping, RBAC drift audits, cluster right-sizing, and cost triage. It runs read-only by default, is bring-your-own-model (Azure OpenAI, Anthropic Claude, Gemini, Bedrock, Ollama), and keeps all data in-cluster with no external egress, targeting GDPR, BaFin, DORA, and NIS2 compliance requirements. Backed by partech; raised a EUR 3M pre-seed round.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Hyground the way a machine reads it — 1 machine-readable artifact, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Hyground scores 19.0/100 (emerging), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Hyground
Each block below is one kind of artifact we hold for Hyground. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Hyground — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Access & Security 2
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 1
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/hyground · machine-readable index on apis.io