Nexus lets different teams share Temporal workflows across team, namespace, region, and cloud boundaries — without exposing internal implementation details.
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.
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).
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 automatically — across any boundary.
fraud.v1/checkTransactionfraud.v1Async Nexus Operations can run for up to 60 days in Temporal Cloud. The caller workflow is suspended until the result arrives.
Nexus Machinery retries failed operations automatically. Pair with workflow ID policies to get exactly-once semantics.
mTLS encryption and namespace allowlists control who can call what. No API keys flying around in code.
Works across teams, namespaces, regions (AWS & GCP), and clouds — with the same developer experience everywhere.
Nexus has four key concepts. These four concepts are the foundation of everything in Nexus.
The address you publish and route through
Think of an Endpoint like a URL for your team's services. It's a named entry point registered in the Nexus Registry that routes requests to a specific namespace and task queue.
It's not a general HTTP proxy — it's specifically designed for Nexus, with built-in auth, retries, and observability.
The contract you publish for others to consume
A Service is a named collection of Nexus Operations — like an API interface. Multiple services can run in the same worker. Callers import the service definition to get type safety.
Example: fraud.v1 service exposes checkTransaction, flagUser, and getScore operations.
The individual action — sync or async
Synchronous operations complete in under 10 seconds. The result comes back in the same HTTP round-trip. Great for quick lookups, scoring, or validations.
Asynchronous operations start a Workflow and return an operation token. The caller workflow is suspended. When the handler workflow completes, a callback delivers the result.
The directory of all Endpoints in your account
Scoped to your Temporal Cloud account or self-hosted cluster. Teams register Endpoints here. The Registry is the source of truth for endpoint discovery, access control, and audit logging.
Walk through the step-by-step lifecycle of a Nexus Operation. Choose sync or async.
Walk through a real Nexus service from scratch using the samples-dotnet NexusSimple sample. Click each step.
Three official Nexus samples — pick your language and run locally in minutes.
Defines a typed IHelloService interface with sync Echo and async SayHello (workflow-backed) operations across two namespaces.
Go implementation of the same Hello/Echo pattern with sync and workflow-backed async operations.
TypeScript version using nexus-rpc and @temporalio/nexus.
Check what you've learned. Click an answer to see if you're right.