Skip to content

What is a Runtime Plane?

In everyday terms, a Runtime Plane is the Kubernetes namespace (namespace and related resources) where Trust3AI runs connectors — the components that connect to your data platforms. You define runtime planes and connectors in the portal. The Runtime Agent runs in that namespace: it manages connector workloads and keeps them aligned with what you configured.

How work flows (simple view)

  1. You change settings in the portal (connectors).
  2. The Runtime Agent polls Runtime Manager for configuration updates and applies what is needed in your runtime plane.
  3. The agent also sends status back — about itself and the connectors — so the control plane and portal stay up to date.
  4. Connectors poll the agent to pick up updates to the configuration properties they use.

Deployment options

You choose how a runtime plane is deployed when you create it: Partially Managed (D2P) or Self-Managed. The two differ in where the control plane runs and who operates it. See Deployment Options for what runs where, a comparison, and the recommendation.

  • Deployment Options — D2P vs Self-Managed: what runs where, comparison, and recommendation.
  • Before You Begin — What to have ready before creating a runtime plane, per deployment type.
  • Support Matrix — Supported clouds and connectors for each deployment type.
  • Getting Started — One-time secrets, provisioning, and day-two notes without repeating the portal form.
  • How Sensitive Data is Handled — Where secrets can live, Trust3AI Managed keys (API key and private encryption key), and how they are protected.
  • Runtime API Reference — HTTP APIs for the runtime plane (connector export, import, and related operations).