Concepts

Security model

How nodes prove who they are, how access is cut off, and where secrets live.

For: cluster operators and plugin authors.

The edge checks node identity and authority. Sandboxes limit what plugin processes and harness sessions can read, change and reach. These controls have different boundaries; use the pages below to assess the one your deployment relies on.

Nothing phones home: no telemetry, usage statistics or update checks, from the server, the embedded Temporal or the node, and any future telemetry is opt-in. Outbound connections lists every connection to a host outside the cluster, when it happens and how to turn it off.

Previous section links

a backdoored model: Read the section.

cutting access: Read the section.

how tier 1 works: Read the section.

identity: Read the section.

limits protected paths and file writes: Read the section.

plugins are trusted code: Read the section.

sandboxes: Read the section.

secrets: Read the section.

secrets in calls and requests: Read the section.

secrets in the working directory: Read the section.

the egress proxy: Read the section.

two ways in: Read the section.

what tier 1 blocks: Read the section.

which tier runs what: Read the section.

On this page
Copyright © 2026