Number of Seats/Users: groundcover offers discounts based on the number of users or seats. A higher volume typically leads to a better discount structure, especially for enterprise-level usage.

Commitment to a Long-Term Contract: Discounts are often provided to companies that commit to using the service for a longer period (e.g., 1-year or 3-year contracts). A longer commitment shows groundcover that the company is serious and willing to invest in the platform long-term.

No Active Discounts: Companies that are not already receiving other active discounts may have a better chance of qualifying for additional discounts from groundcover. groundcover reserves discounts for new customers or those not currently under promotional pricing.

Volume or Usage Commitment: groundcover offers discounts if you agree to a minimum amount of usage or transaction volume. This could be based on data storage, transactions, or other metrics tied to how much you will use the platform.

Enterprise-Level Negotiation: Companies that qualify as “enterprise” due to their size or complexity (e.g., having large teams, multiple departments, or geographical presence) may be eligible for additional discounts from groundcover. Such companies are often in a position to negotiate for better pricing.

Early Renewal or Prepayment: groundcover often offers discounts if you renew early or prepay for the entire contract period. This is a common approach to securing a lower price.

Here at Spendbase our internal data shows that groundcover is seen as a high‑value, modern observability platform, especially for Kubernetes‑centric teams, with a few clear tradeoffs that are useful in pricing and contract talks.

Overall sentiment
Most Spendbase clients rate groundcover very highly, often equating it with, or even preferring it to, tools like Datadog, New Relic, Dynatrace, Kibana, and Instana, especially when cost is factored in.

Key strengths our clients highlight
– Cost & commercial model
– Predictable, simple pricing with no hidden fees
– Very strong cost‑to‑value ratio for full‑stack observability
– Data and retention often hosted in the client’s own cloud without direct cost impact
– Kubernetes‑first observability
– Excellent fit for EKS and cloud‑native workloads
– eBPF‑powered data collection with minimal footprint
– Logs, metrics, traces, and infra views in one place
– Speed to value
– Fast setup, often “minutes to insights”
– Little to no code changes needed
– GitOps‑friendly configuration
– Usability & support
– Generally intuitive UI, easy dashboards and alerting
– Strong Slack‑based support, responsive and hands‑on
– Good for debugging production and test environments, including use cases like Kubeflow and Playwright

Main friction points (good levers in negotiations)
Spendbase clients also surface consistent areas where groundcover is still maturing:

• Product gaps
• Limited support for some legacy, on‑prem, and hybrid environments
• Some eBPF integrations and protocol support still missing
• History/retention limits in some plans and log size limits
• No unified multi‑cluster view yet in some setups
• UX and performance
• UI not as polished as long‑standing incumbents
• Occasional sluggish pages, slow or stuck queries, and dashboard loading delays
• Screen‑resolution issues and complex filters/log drill‑down in some workflows
• Navigation of distributed traces can be improved
• Adoption curve
• For a few newer users, the breadth of capabilities feels overwhelming at first
• Some note data consistency concerns and a desire for more node‑level and log‑level clarity (partially addressed over time)

From a Spendbase discount perspective, this mix is attractive: groundcover delivers strong, Kubernetes‑native observability at a lower and more predictable cost, while the noted UX gaps, feature roadmap items, and environment limitations create solid arguments for better pricing, favorable terms, and added concessions around support and roadmap commitments.