BeaverDeck
Get started
Release 1.6.5Go standard-library security update

Kubernetes operations, from signal to action.

BeaverDeck is a self-hosted workspace for Cluster Insights, resource inspection, logs, exec sessions, and controlled day-2 actions, with GPU capacity visibility for AI-oriented clusters.

Get started Read the docs
$helm upgrade --install beaverdeck oci://ghcr.io/arequs/charts/beaverdeck
BeaverDeck pods view with namespace filters, resource table, and streaming logs
37Insight checks across 7 categories
1Helm command to install in your cluster
SSOLocal users, Google, OIDC, and Microsoft Entra ID
Why BeaverDeck

Shorten the path from a cluster signal to a controlled action.

Built for platform, DevOps, and SRE teams who need answers during an incident, not another dashboard to stare at.

01 / Triage

Slow incident triage

Start from grouped health signals instead of jumping between raw object tables, terminals, and ad hoc commands.

02 / Day-2

Scattered day-2 work

Logs, manifests, exec sessions, YAML apply, scaling, restarts, drains, and deletes live in one permission-aware workspace.

03 / Compute

Expensive compute blind spots

GPU visibility and capacity signals help teams understand AI workload placement and reduce waste on costly infrastructure.

Features

Everything you reach for during an incident, in one place.

Inspect Kubernetes state, triage findings, and carry out common day-2 operations from one self-hosted workspace.

Cluster Insights

Grouped findings for nodes, workloads, GPU capacity, networking, storage, security, and configuration.

Resource inspection

Search workloads and Events, spot Warning and Error severity, and inspect manifests and relationships without switching tools.

Logs and exec

Stream regular and init-container logs, then open terminal sessions with explicit container selection for multi-container pods.

Controlled operations

Apply YAML, edit manifests, scale or restart workloads, and run node actions under BeaverDeck permissions.

GPU visibility

Allocation pressure, scheduling constraints, idle allocations, fragmentation, quotas, and placement signals.

Self-hosted access

Run in your cluster with local users or Google, OIDC, and Microsoft Entra ID sign-in, plus namespace-scoped roles.

Insights-first triage

Start from grouped signals, not raw tables.

Every finding links to the resource, log, manifest, or action behind it. Each check is documented with its trigger, risk, remediation, and limits.

BeaverDeck Insights view with critical and warning findings and actions to open resources and logs

Explore all 37 Insight checks

Operations workspace

Keep the confirmation and action path close to the signal.

Inspect and troubleshoot

  • Pods, workloads, nodes, services, ingresses, config maps, secrets, PVCs, PVs, storage classes, CRDs, and events
  • Manifests as YAML
  • Streaming pod and workload logs, including failing or active init containers
  • Exec sessions into running pods

Operate with control

  • Apply YAML and edit resources through server-side apply
  • Scale, restart, delete, evict, drain, and uncordon from the UI
  • GPU visibility and capacity signals for AI workload placement
  • Users, roles, and namespace-scoped permissions for every action
A / Visibility

Operations visibility

Start from useful signals, then get to the resource, log, manifest, or action behind them.

B / Efficiency

Compute efficiency

Understand costly infrastructure better, including GPU capacity used by AI workloads.

C / Ownership

Self-hosted control

Deployment, access control, and operational configuration stay inside infrastructure you operate.

Deployment

Running in your cluster in minutes.

Install with the official Helm chart. No external database and no agent outside your cluster.

  1. Install the chart

    One Helm command creates the namespace and deploys BeaverDeck with its service account and RBAC.

  2. Open the UI

    Expose it through your ingress, or port-forward the service for a quick local look.

  3. Create the first admin

    On first start, set the initial administrator. Auth configuration is stored in a Kubernetes Secret; DATA_DIR holds only non-auth runtime metadata.

Getting started guide Helm values 
# 1. Install BeaverDeck
$ helm upgrade --install beaverdeck \
    oci://ghcr.io/arequs/charts/beaverdeck \
    --namespace beaverdeck \
    --create-namespace \
    --set clusterName=your-cluster-name

# 2. Wait for the rollout
$ kubectl -n beaverdeck rollout status deployment/beaverdeck

# 3. Open http://localhost:8080
$ kubectl -n beaverdeck port-forward svc/beaverdeck 8080:80
Open source

Bring clarity to your clusters.

Install BeaverDeck in your own infrastructure and keep cluster access under your control.

Get started