For procurement, security and compliance teams
When the technical team is convinced, the second loop begins: procurement, security review, legal, compliance. Hyground was built to make that loop short. Here is the answer pack you can hand over before they have to ask.
The six questions we get every time
Each card pairs a real procurement question with how Hyground answers it today. If you need the underlying artefact, the questionnaire response or the contract clause, ask and we will hand it over.
Data residency
Inside your cluster, in your region. No telemetry leaves your perimeter, no inference runs outside your network. We do not operate an API gateway that would ever see your data, and there are no third-party sub-processors in the data path.
Compliance and audit
Hyground is architecturally aligned with the EU AI Act's limited-risk profile and the GDPR data-minimisation principle: no data egress, no third-party processing, no training on your operational data. ISO 27001 and SOC 2 Type II certifications are in progress, with final attestation expected in August 2027. A data processing addendum (DPA) is available on request.
Vendor lock-in
Helm uninstall and you are out. No proprietary data formats, no customer data stored on our side, no license-server dependency. Your skills, knowledge base and session history live as plain YAML and Markdown inside your cluster, exportable any time.
Pricing and TCO
Fixed pricing scoped to your infrastructure footprint, deployment size and use cases. No per-investigation metering, no egress bill because nothing leaves your perimeter, no surprise inference-spike charges. The number you quote internally on day one is the number you pay in year three.
Liability and risk
Adapters start read-only and refuse to start if their credentials can write. Any mutation is explicitly opt-in and human-gated. Every output is auditable and reversible. The SLA and liability cap are written into the MSA, not left to interpretation.
References
Deutsche Bahn (Reisendeninformation), ifm, and a number of additional regulated operators running Hyground in production under NDA. Reference calls are available on request, including conversations directly with the customer's platform or security lead.
How we work together
Hyground is a platform plus a team. Onboarding, training, workshops and Forward Deployed Engineering are part of every engagement, scoped to the outcome you actually need, not bundled as filler.
Onboarding
Helm chart install, adapter configuration, RBAC scoping, your first skills imported from existing runbooks. By the end of week two your team is running investigations end-to-end against production, with a documented runbook for operating Hyground itself.
Training
Live sessions covering investigation patterns, skill authoring, scheduling, trigger configuration and adapter setup. Recorded for re-use, paired with hands-on labs against your own environment.
Workshops
Working sessions on your specific operational pain: incident retrospectives, capacity reviews, FMEA exercises, runbook hardening. We use Hyground as the operating canvas, and your team leaves with new skills committed to the knowledge base.
Forward Deployed Engineer
For complex rollouts or critical engagements, we embed a Forward Deployed Engineer for a defined sprint. They write skills against your runbooks, integrate non-standard tools, and pair directly with your SREs in production. Time-boxed, scoped to a deliverable, with a clear hand-back to your team.
Walk us through what your procurement, security and compliance teams need from a vendor. We will return a tailored pack with our answers, the relevant artefacts, and reference customers willing to take an NDA-protected call.