Skip to content
Spinoza

Features

Security posture

Local mode holds your kubeconfigs. Cluster mode serves a team from a service account. Each model keeps its own boundary.

Drain plans first. It counts what it would evict, leave and block, names the reason for each, and keeps the button disabled until you accept the blocked pods.

Spinoza drain plan for a node: how many pods it would evict, leave in place and block, the reason for each, and the drain button disabled behind a checkbox

  • Loopback-only local mode

    Local mode refuses any other interface; cluster mode binds the address you configure.

    Local mode only

  • Per-run token in local mode

    A token minted for that local run, required on every request and socket.

    Local mode; cluster mode uses a signed-in session

  • Kubeconfigs referenced, never copied

    Read in place, never merged into a file the tool manages.

  • RBAC-aware UI

    Actions the cluster would refuse are not offered.

  • Attested release artifacts

    Archives, desktop apps, image, chart and SBOMs carry build provenance; installers verify checksums.

  • SSO for a shared deployment

    OIDC or an authenticated proxy in front of preview cluster mode.

    Preview cluster mode

  • Audit trail

    Every change with who asked and whether the cluster allowed it, plus sign-ins in cluster mode. Admins export it as CSV or JSON.

  • Terminal transcripts

    Exec and node shell sessions recorded beside their audit entry, only when a deployment turns it on.

    Off until a deployment or a flag turns it on

In the documentation