Interactive Demo

What is Temporal Nexus?

Nexus lets different teams share Temporal workflows across team, namespace, region, and cloud boundaries, without exposing internal implementation details.

The core idea in one sentence

Team A can call Team B's workflows like a typed API, with full durability, retries, and fault-tolerance built in, without needing access to Team B's namespace or knowing how their code works.

The Problem Nexus Solves

Without Nexus

Siloed Teams

Each team works in their own Temporal namespace. There's no clean way for the Payments team to trigger an action in the Fraud Detection team's workflow without tight coupling or shared credentials. Teams either share namespaces (messy) or build fragile HTTP bridges (unreliable).

With Nexus

Modular and Safe

The Fraud Detection team publishes a Nexus Service with a clear contract. The Payments team calls it from their workflow like any other operation. Nexus handles routing, retries, security, and observability, across any boundary.

What It Looks Like

Team A: Payments

W

PaymentWorkflow

Caller Namespace

Calls fraud.v1/checkTransaction
Waits for result (sync or async)

→

Nexus Endpoint

Routes securely

Retries · Auth

→

Team B: Fraud Detection

S

Nexus Service: fraud.v1

Handler Namespace

W

FraudCheckWorkflow

Runs internally, result returned

Key Facts

Durability

Up to 60 Days

Async Nexus Operations can run for up to 60 days in Temporal Cloud. The caller workflow is suspended until the result arrives.

Reliability

At-Least-Once

Nexus Machinery retries failed operations automatically. Pair with workflow ID policies to get exactly-once semantics.

Security

Built-in Auth

mTLS encryption and namespace allowlists control who can call what. No API keys in code.

Boundaries

Cross-Everything

Works across teams, namespaces, regions (AWS & GCP), and clouds, with the same developer experience everywhere.