Built for cautious hands
Truss opens in read-only mode. Write mode is explicit, visible, and hard to forget when you turn it on.
v0.8 Local Kubernetes desktop
Truss
A Kubernetes workbench that starts from the way production incidents actually feel: too many panes, too much trust, not enough context.
Truss default
Context: prod-east Vault Preferences
RO Ctrl+P or : Command, / Search
prod-east / payments / Pods / api-gateway-7c8d9
Namespace: payments 5/214
Pods Filter by name... 3 1 1
Name Namespace Status Age
api-gateway-7c8d9 payments Running 3/3 12m
ledger-writer-0 payments Running 2/2 31m
refund-worker-6f44 payments CrashLoopBackOff 1/2 4m
stripe-egress-86bd payments Running 1/1 2h
public-web-77d9 web Pending 0/1 55s
Pod
api-gateway-7c8d9
payments
DataYAMLScaleRestartDelete
SummaryDataYAMLEventsPods
Kind
Pod
Namespace
payments
Node
ip-10-42-7-19
Ready
3/3
Restarts
0
Age
12m
Ready all containers passing probes
Event one sibling pod is backoff-looping
Owner deployment/api-gateway
What gives it character
It behaves like an operator desk, not a dashboard demo.
Local by design
Kubeconfigs stay in an encrypted local vault using Argon2id/AES-256-GCM or your GPG key.
Fast without hiding kubectl
Logs, exec, file transfer, YAML diffing, Helm history, events, and port-forwards open as focused app windows instead of crowding the inspector.
Daily loop
Inspect, intervene, recover.
The shape is intentionally boring: context on the left, resources in the middle, the thing you are touching on the right. The character comes from making the dangerous path visible.
- 01
Inspect
Tree, list, and inspector stay in sync while events and health keep updating.
- 02
Intervene
Open logs, exec, file transfer, YAML, or port-forward in focused panes and popouts.
- 03
Recover
Compare YAML, inspect Helm values, and roll back only after leaving read-only mode.
Ship it onto your workstation.
Linux AppImage, macOS DMG, and Windows installer builds are published from signed release tags.