pitbox by DesiredCloud
alpha · launching soon
Crossplane console

The operator console for Crossplane.

See, trace, and debug everything your control plane runs. Every read served from an in-memory cluster cache — ms answers to the questions you ask all day: what's degraded, what composed what, what actually got created.

No spam — one email when helm install pitbox is real. Source opens at launch.
pitbox — live against a Crossplane v2 cluster
1binary, no dependencies
11typed Crossplane resource kinds
<50mscluster-wide search
read-onlyby design, writes behind flags

Built for the questions operators actually ask

Not another CRD table. pitbox understands Composite Resources, compositions, providers, and operations as first-class concepts.

Answers, not tabs

The Overview leads with a diagnosis — what's degraded, the controller's own message, and how long it's been failing. Triage starts at a sentence, not a list.

⌘KSearch everything

One palette across every resource in the cluster — names, kinds, labels — with results in under 50 milliseconds at typical cluster sizes.

Trace

Walk any XR down through nested composites to every leaf managed resource, with live status at every node. The composition tree, finally legible.

Outcomes

What did this XR actually produce? Wrapped Kubernetes objects, Helm releases, Terraform modules, and cloud identifiers — flattened into one table with ready-to-paste kubectl commands.

The whole estate, live

XRs, MRs, XRDs, MRDs, Compositions, Providers, Functions, Configurations, and Operations — live-updating lists and detail pages with YAML, events, and relationships.

Safe by default

Read-only console. Secrets and credential-shaped fields are redacted server-side in every YAML view. Mutations stay behind explicit flags — and soon, real RBAC.

Runs next to your cluster in minutes

A single Go binary with an embedded UI. Point it at a kubeconfig, open a browser. Helm chart and public source land at launch.

Crossplane v2 · single pod · no Redis, no sidecars