Skip to content
Spinoza

Run modes

Your machine, or one shared cluster.

Local mode is the supported product. Cluster mode uses the same binary to serve one cluster to a team and is in preview.

Supported

Your machine

Run one binary in a browser tab or desktop window. It reads your kubeconfigs in place and can keep several clusters open at once.

Preview

One shared cluster

Run the same binary from its OCI Helm chart. A team signs in through OIDC or an authenticated proxy and works against that cluster.

AreaYour machineOne shared cluster
StartInstallShell or PowerShell installer, archive, deb or rpmOCI image and Helm chart
StartAddressLoopback onlyThe public URL and listener you configure
AccessSign-inA token minted for that runOIDC or an authenticated proxy; anonymous admin needs an unsafe opt-in
AccessKubernetes identityThe selected kubeconfig contextA read-only service account by default; the signed-in account once impersonation is on
AccessRead scopeWhatever the kubeconfig may read, including credentials limited to named namespacesWith impersonation, the namespaces the account may list; whole-cluster views need whole-cluster read
WorkspaceClustersSeveral at once, each in its own tabThe cluster running Spinoza
WorkspaceInterfaceBrowser and desktop; move between them mid-sessionBrowser
WorkspaceLifetimeStops when the last view closesRuns with the pod; takes traffic once its caches are filled, and drains before it stops
WorkspaceSaved viewsYours, on this machineEach person's own; an admin can publish one for everybody
OperationsWrite accessThe kubeconfig's RBAC, with protected-cluster confirmationViewer, editor or admin role, then Kubernetes RBAC
OperationsPort-forwardingPods and services forwarded to your machineUnavailable
OperationsAudit trailEvery change Spinoza made, per clusterChanges and sign-ins, exported by admins as CSV or JSON and logged as structured lines
OperationsTerminal transcriptsOff unless started with --record-sessionsOff unless the deployment turns them on; admins read them
OperationsSelf-reportingText logs, and /metrics behind the run's tokenJSON logs, /metrics for admins or a separate scrape port, and a readiness check
OperationsUpdatesOptional update check; never installs by itselfNo update check or self-install path