Merge branch 'main' into reset-with-move-docs

Author: axfelix

docs/evaluate/development-production-features/multi-cloud-namespace.mdx

@@ -0,0 +1,92 @@
+---
+id: multi-cloud-namespace
+title: Multi-cloud Namespace - Temporal Cloud production feature
+description: Temporal Cloud's Multi-cloud Namespaces offer automated failover, synchronized data replication, and high availability for workloads requiring disaster-tolerant deployment and 99.99% uptime.
+sidebar_label: Multi-cloud namespace
+tags:
+  - Temporal Cloud
+  - High availability
+keywords:
+  - availability
+  - explanation
+  - failover
+  - high-availability
+  - multi-cloud
+  - multi-cloud namespace
+  - namespaces
+  - temporal-cloud
+  - term
+---
+
+Temporal Cloud offers disaster-tolerant deployment for workloads with stringent availability requirements.
+With the multi-cloud feature enabled, Temporal Cloud automates [failover](/glossary#failover) and synchronizes data between Namespaces hosted on different cloud providers (either AWS or GCP).
+This page introduces Temporal Cloud patterns that support your workload's availability requirements.
+
+## Multi-cloud Namespaces
+
+Multi-cloud Namespaces provide failover capabilities to mitigate service outages due to regional failures.
+They reduce risk and minimize operational disruption.
+This feature seamlessly shif​​ts Workflow execution between regions to maintain service availability.
+
+Your Clients use a single logical Namespace with a single endpoint that operates on two separate cloud providers: one active and one standby.
+As Workflows progress in the active provider, history events asynchronously replicate to the standby provider.
+Data replication ensures both providers are in sync so the standby is ready to take over when needed.
+
+Should an incident or outage occur in the active provider, Temporal Cloud initiates a "failover" to the standby provider.
+During a failover, the roles of the active and standby providers reverse.
+The standby takes over as the primary provider.
+
+### Advantages of multi-cloud Namespaces {#multi-region-advantages}
+
+**Why choose multi-cloud replication (MCR)?**
+
+- **Reduce Risk**:
+  Protects your operations from unexpected regional outages.
+  Automated disaster recovery features ensure that workloads remain available and continue execution.
+- **Minimize Operational Disruption**:
+  Seamless failovers shift Workflow Executions to a secondary provider during outages.
+  Maintains service availability without needing manual synchronization between Namespaces.
+  Real-time alerts during failover events keep you informed.
+- **No manual deployment or configuration needed:**
+  Temporal Cloud simplifies deployment with push-button operation.
+  This eliminates the need for manual deployment or configuration.
+- **Fault tolerance**.
+  Your open Workflows continue their progress in the standby region.
+  This minimizes interruption and data loss during regional failures.
+- **No code changes**.
+  Your Workers and Workflow starter code don't need updates to take advantage of multi-cloud setup or to respond to failover conditions.
+  This allows for a smooth transition and continued operation.
+
+### Service Level Objectives (SLO) and guarantees {#cloud-region-SLO}
+
+**What reliability promises does this feature offer?**
+
+- Temporal provides a 99.99% Contractual SLA that provides redress in the event of downtime ([SLA](https://docs.temporal.io/cloud/sla)).
+- [RTO](https://csrc.nist.gov/glossary/term/recovery_time_objective): 20 minutes or less.
+- [RPO](https://csrc.nist.gov/glossary/term/recovery_point_objective): Near zero.
+
+### Target workloads {#target-workloads}
+
+**Who benefits from this feature?**
+
+Multi-cloud Namespaces are a great solution for Workloads where a regional cloud outage would cause:
+
+- Revenue loss
+- Poor customer experience
+- Problems stemming from policy/legal requirements that demand high availability
+
+Some examples: financial services, e-commerce, gaming, global SaaS platforms, bookings & reservations, delivery & shipping, order management.
+
+### Explore {#explore-multi-cloud}
+
+**Read more about our multi-cloud features**
+
+- [Multi-cloud Namespaces](/cloud/high-availability/enable) offer High Availability service for Temporal Cloud customers who need the highest level of availability at all times.
+- [Multi-cloud Pricing](/cloud/pricing) scales to use.
+- Multi-cloud replication supports [PrivateLink routing](/cloud/high-availability/private-link).
+
+### Explore {#explore-temporal-namespaces}
+
+**Read more about Namespaces**
+
+- [Temporal Cloud Namespaces](/cloud/namespaces) offer outstanding reliable service for Temporal Cloud customers.

docs/glossary.md

@@ -330,6 +330,13 @@ Multi-Cluster Replication is a feature which asynchronously replicates Workflow
 
 <!-- _Tags: [term](/tags/term), [explanation](/tags/explanation)_ -->
 
+#### [Multi-cloud Replication](/cloud/high-availability/enable)
+
+Multi-cloud Replication replicates Workflows and metadata to a different cloud provider (AWS or GCP).
+This is particularly beneficial for organizations required to be highly available across regions for compliance purposes.
+
+<!-- _Tags: [term](/tags/term), [explanation](/tags/explanation)_ -->
+
 #### [Multi-region Replication](/cloud/high-availability/enable)
 
 Multi-region Replication replicates Workflows and metadata to a different region that is not co-located with the primary Namespace.

docs/production-deployment/cloud/high-availability/enable.mdx

@@ -51,6 +51,9 @@ Temporal offers the following High Availability features, which you can configur
   This is particularly beneficial for organizations with multi-regional architectures or those required to be highly available across regions for compliance purposes.
   This option is a good fit if your application is architected to be multi-region.
   GCP Namespaces support Multi-region Replication.
+- **Multi-cloud Replication**: Workflows are seamlessly replicated to a different cloud provider (AWS or GCP) that you choose.
+  Replicating Workflows across different cloud providers offers reliability in the event of a widespread provider failure.
+  This is particularly beneficial for organizations in highly regulated industries with requirements for multi-cloud availability.
 
 There are charges associated with Replication and enabling High Availability features.
 For pricing details, visit Temporal Cloud's [Pricing](/cloud/pricing) page.
@@ -70,6 +73,7 @@ The following instructions explain how:
     1. Select "Add a replica":
        - Adding a replica in the same region enables Same-region Replication.
        - Adding a replica in a different region (within the same continent) replicates across regions for Multi-region Replication.
+       - Adding a replica on a different cloud provider replicates across providers for Multi-cloud Replication.
        - You cannot create a Multi-region deployment on separate continents.
 
     The web interface will present an estimated time for replication to complete.
@@ -124,7 +128,7 @@ The following instructions explain how:
 1. Visit Temporal Cloud Namespaces in your Web browser.
 1. Navigate to the Namespace details page.
 1. Select the “Add a replica” button.
-1. Choose either **Same-region Replication** or **Multi-region Replication** (across regions).<br />
+1. Choose **Same-region Replication**, **Multi-region Replication** (across regions), or **Multi-cloud Repllication** (across cloud providers).<br />
    _If you select Multi-region Replication, specify which [region](/cloud/high-availability/regions).
    You cannot create a Multi-region deployment on separate continents._
 

docs/production-deployment/cloud/high-availability/how-it-works.mdx

@@ -95,6 +95,10 @@ Because each region has multiple isolation domains, you can place your replica i
   This setup allows failovers between replicas without needing immediate consistency across regions.
   Replication across different regions enhances resilience and reliability.
 
+- **Multi-cloud Replication**:
+  Temporal asynchronously replicates all Workflows (live and historical) and data to a Namespace in a different cloud provider (AWS or GCP).
+  If a provider outage, regional outage, service disruption, or network issue occurs, traffic automatically shifts to the replica.
+
 :::caution
 
 Even as you adopt Temporal's High Availability features, don't forget to consider the reliability of your own infrastructure and dependencies.
@@ -105,10 +109,11 @@ Using physically separated regions provides fuller tolerance for your applicatio
 
 :::
 
-| **Deployment**                          | **Description**                                          |
-| --------------------------------------- | -------------------------------------------------------- |
-| **Same‑region Replication**  | Isolation domains are co-located within the same region. |
-| **Multi‑region Replication** | Isolation domains are located in separate regions.       |
+| **Deployment**                          | **Description**                                            |
+| --------------------------------------- | ---------------------------------------------------------- |
+| **Same‑region Replication**  | Isolation domains are co-located within the same region.   |
+| **Multi‑region Replication** | Isolation domains are located in separate regions.         |
+| **Multi‑cloud Replication**  | Isolation domains are located in separate cloud providers. |
 
 ## Failovers
 

docs/production-deployment/cloud/high-availability/index.mdx

@@ -48,7 +48,7 @@ This provides a higher service level than our standard 99.9% SLA.
 With High Availability features in Temporal Cloud, you can meet your availability SLAs, and ensure service disruptions and outages don’t affect the performance of your applications.
 
 - Keep your applications online by protecting your Temporal Workflows against outages and service disruptions
-- Same-region Replication and Multi-region Replication offer a 99.99% contractual SLA for workloads with strict uptime requirements, compliance, and regulatory needs; whether you choose to be in a single region or across multiple regions.
+- Same-region Replication, Multi-region Replication, and Multi-cloud Replication offer a 99.99% contractual SLA for workloads with strict uptime requirements, compliance, and regulatory needs; whether you choose to be in a single region or across multiple regions.
 
 ### Critical availability
 

sidebars.js

@@ -35,6 +35,8 @@ module.exports = {
             "evaluate/development-production-features/cloud-automation",
             "evaluate/development-production-features/low-latency",
             "evaluate/development-production-features/multi-tenancy",
+            "evaluate/development-production-features/multi-region-namespace",
+            "evaluate/development-production-features/multi-cloud-namespace",
             {
               type: "category",
               label: "Product release stages",