Skip to content
Drill

Find problemsbefore your users do.

Scheduled checks for every workload and for the cluster itself, tuned to each technology — and alerts that arrive already explained.

From a scheduleto a signal you can trust.

01

Recognises your stack

Drill finds your Deployments and StatefulSets and works out what each one runs.

02

Checks on a schedule

Security posture or performance, a quick pass or a deep look per workload — hourly, nightly, on your own cron, or right now.

03

A specialist's playbook for each technology

PostgreSQL, MySQL, MongoDB, ClickHouse, RabbitMQ, Node.js and Kubernetes each get the checks an expert would run.

04

Findings, not noise

One problem is one tracked concern. It reopens if it comes back and closes itself when it's gone — or mute it, accept it, mark it fixed.

05

Alerts that arrive explained

Alertmanager alerts land on the workload they're about, next to what Drill had already found — and can be investigated the moment they fire.

Ready the day you install it:30 checks.

14 for security and 16 for performance & reliability, each citing its source — Pod Security Standards, kubescape, Polaris, Trivy and the kube-prometheus rules.

Security14

  • Privileged containers
  • Host namespaces
  • Over-privileged RBAC
  • Privilege escalation
  • Running as root
  • Host path mounts
  • Added capabilities
  • Writable root filesystem
  • No seccomp profile
  • Service-account token automount
  • Secrets in environment variables
  • No network policy
  • Mutable image tags
  • Workloads in the default namespace

Performance & reliability16

  • OOM kills
  • Restart churn
  • Unavailable replicas
  • Pending pods
  • Stuck rollouts
  • No resource requests
  • No resource limits
  • CPU throttling
  • Saturated autoscalers
  • Volume pressure
  • Right-sizing
  • Missing probes
  • Misconfigured probes
  • Single replica
  • No disruption budget
  • No topology spread

Stop finding outfrom your users.