groundcover: Cloud and On-Prem Observability Platform

Key Features

• eBPF-powered Sensor

  Collects telemetry across the stack without requiring code changes or manual instrumentation.

• Infrastructure & APM

  Provides visibility into infrastructure health and application performance, including service dependency mapping.

• BYOC Architecture

  Processes and stores observability data within the user's own Virtual Private Cloud (VPC).

• Agent Mode AI

  An investigation tool running on Amazon Bedrock inside the customer's AWS account to analyze logs and traces.

• Log Management

  Supports streaming, storing, and querying logs with centralized alerting.

• LLM Observability

  Designed to monitor reasoning paths, token usage, and tool calls for AI-powered applications.

Use Cases

• Kubernetes Monitoring

  Supports cluster visibility and troubleshooting for Kubernetes stacks without manual code changes.

• AWS Environment Observability

  Monitoring EKS, EC2, and RDS while keeping data within the AWS environment.

• Regulated Data Management

  Using on-premise or air-gapped deployments to meet data residency and security requirements.

• Cost-Predictable Monitoring

  Using a per-host monthly cost model instead of ingestion-based pricing.

Integrations

• OpenTelemetry
• Prometheus
• CloudWatch
• Grafana
• Slack
• PagerDuty
• Microsoft Teams
• Opsgenie

FAQ

How does groundcover's pricing work?

groundcover uses a host-based pricing model based on the average number of monitored Kubernetes or Linux hosts per month.

Does groundcover store my data on their servers?

groundcover uses a Bring Your Own Cloud (BYOC) or on-premise model, which is designed to keep observability data within the user's own environment.

Is code instrumentation required for groundcover?

No, it uses an eBPF-powered sensor to provide visibility across the stack without requiring manual code changes.