Why local-first matters for Kubernetes tooling
Why conndeck is designed local-first: no telemetry, no login, and cluster credentials that stay on your device by default, plus the trade-offs of that posture.
Read the postconndeck blog
Writing about local-first Kubernetes operations: security posture, fleet drift, GUI plus TUI workflows, and verifiable releases. No telemetry, no login, no data leaves your device.
Verifiable releases: SBOM, provenance, and signatures
Admin tools with deep cluster access are sensitive supply-chain targets; hashes, detached signatures, an SBOM, and provenance let you verify a release before it runs.
Read the postFleet drift detection without a control plane
How conndeck approaches fleet drift compare and guarded promote from a local-first desktop tool, without a hosted control plane in the middle.
Read the postOne core, two surfaces: GUI and TUI for Kubernetes ops
How conndeck's single Rust Kubernetes core powers both a desktop GUI and a terminal UI, keeping behavior, permissions, and guarded actions consistent.
Read the post