Skip to main content

Nexus Registry

SUPPORT, STABILITY, and DEPENDENCY INFO

Temporal Nexus is now Generally Available for Temporal Cloud and self-hosted deployments.

The Nexus Registry manages Nexus Endpoints. Adding an Endpoint to the Registry deploys it for immediate runtime use. Endpoint names must be unique within the Registry. In Temporal Cloud, the Registry is global across your entire Account, spanning all Namespaces. In self-hosted deployments, it is scoped to a Cluster.

View and manage Nexus Endpoints​

Manage Endpoints using the Temporal UI, CLI, Terraform provider, or Cloud Ops API.

RESOURCES

Search for a Nexus Endpoint​

Search by Endpoint name or target Namespace.

Nexus Endpoints

Nexus Endpoints

The details page shows the target Namespace, Task Queue, and description rendered as markdown.

Nexus Billing

Nexus Billing

Create a Nexus Endpoint​

Creating an Endpoint includes setting an Access Policy - the allowlist of caller Namespaces permitted to use the Endpoint. No callers are allowed by default, even if in the same Namespace as the Endpoint target.

Create Nexus Endpoint

Create Nexus Endpoint

Edit a Nexus Endpoint​

Everything except the Endpoint name can be edited. New Operations route to the updated target immediately.

Changing the target Namespace
  • In-flight async Operations - Completion callbacks point to the original handler Namespace and are unaffected, but Cancel requests route to the new target.
  • Workflow ID uniqueness - IDs are scoped per Namespace. Signal-With-Start creates a new Workflow in the new target even if the same ID is active in the old target, resulting in potential duplicates.
  • Recommendation: Drain existing Nexus Operations and underlying handler Workflows before changing the target Namespace.
Edit Nexus Endpoint

Edit Nexus Endpoint

Configure runtime access controls​

The Access Policy controls which caller Namespaces can use an Endpoint at runtime. No callers are allowed by default.

Configure runtime access controls

Configure runtime access controls

See Runtime Access Controls for details.

Roles and permissions​

info

Temporal Cloud has built-in Nexus security. For self-hosted deployments you can implement custom Authorizers.

In Temporal Cloud:

  • View/search Endpoints: Read-only role (or higher) in the Account.
  • Manage Endpoints (create, edit, delete): Developer role (or higher) and Namespace Admin on the target Namespace.

See Nexus security in Temporal Cloud.

Terraform and Ops API support​

Automate Endpoint provisioning and lifecycle management with Terraform or the Ops API.

RESOURCES