docs: add resilience in Elastic Cloud Serverless page

deploy-manage/production-guidance/availability-and-resilience.md

@@ -3,6 +3,7 @@
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/high-availability-cluster-design.html
 applies_to:
+  serverless:
   deployment:
     ess: all
     ece: all
@@ -65,6 +66,8 @@
 
 In addition, [Resilience in {{ech}} and {{ece}} deployments](./availability-and-resilience/resilience-in-ech.md) outlines how ECH and ECE orchestrators implement resilience, and offers guidance to ensure your deployments follow best practices.
 
+In addition, [Resilience in {{serverless-full}}](./availability-and-resilience/resilience-in-serverless.md) describes how the Serverless platform handles durability, availability, and recovery automatically.
+
 ## Client traffic distribution
 
 When designing a resilient {{es}} cluster, avoid routing client traffic, whether from {{kib}}, Logstash, Beats, {{agent}}, or other applications, to a single node. Relying on one node introduces a single point of failure, which can compromise data availability if that node becomes unavailable.

deploy-manage/production-guidance/availability-and-resilience/resilience-in-serverless.md

@@ -0,0 +1,51 @@
+---
+navigation_title: Resilience in Serverless
+applies_to:
+  serverless:
+products:
+  - id: cloud-serverless
+---
+
+# Resilience in {{serverless-full}} [resilience-in-serverless]
+
+In {{serverless-full}}, Elastic manages all infrastructure resilience automatically. Unlike {{ech}} or self-managed deployments, there are no nodes to configure, no replica counts to tune, and no availability zone settings to manage. Resilience is built into the platform at the infrastructure level.
+
+## Data durability [resilience-serverless-data-durability]
+
+{{serverless-short}} uses a stateless storage architecture in which indexed data is written to cloud-provider object storage rather than stored as local replicas on cluster nodes. This provides extreme data durability:
+
+* Object storage is replicated across multiple physical locations within a region by the underlying cloud provider, independently of compute node health.
+* Data durability does not depend on in-cluster shard replication. A node failure has no impact on data that has already been written — the data exists independently of the compute layer.
+* Elastic automatically retains recovery data for each project to support emergency data recovery scenarios.
+
+To learn more about the stateless architecture underpinning {{serverless-short}}, refer to [Elastic's serverless architecture](https://www.elastic.co/blog/elastic-serverless-architecture).
+
+The stateless architecture introduces a higher baseline write latency compared to {{ech}}, as writes are batched before being committed to object storage. Refer to [Compare {{ech}} and Serverless](/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md) for details on write performance characteristics.
+
+## High availability [resilience-serverless-high-availability]
+
+{{serverless-short}} automatically distributes compute resources across multiple availability zones within a region. No configuration is required:
+
+* Query and indexing traffic is served from multiple zones simultaneously.
+* If a zone becomes unavailable, traffic is automatically shifted to the remaining zones with no action required from you.
+
+Elastic maintains a service level agreement (SLA) for {{serverless-short}} project availability. Refer to the [Elastic Cloud Serverless Service Level Agreement](https://www.elastic.co/agreements/sla-elastic-cloud-serverless) for details.
+
+## Data recovery [resilience-serverless-data-recovery]
+
+Elastic retains recovery data for each {{serverless-short}} project. In the event of data loss caused by an infrastructure failure, Elastic can use this to restore your project to a previous state.
+
+{{serverless-short}} does not currently offer a self-service recovery workflow for data loss resulting from user-initiated operations, such as accidental index deletion or bulk document removal. If you experience this type of data loss, [contact Elastic Support](/troubleshoot/index.md#contact-us) to discuss your options.
+
+::::{note}
+Self-service data recovery is planned for a future release.
+::::
+
+## Regional scope [resilience-serverless-regional-scope]
+
+All resilience in {{serverless-short}} is regional. Projects run in a single cloud region, and there is no built-in support for multi-region architectures:
+
+* Cross-region replication is not available.
+* There is no automatic failover to an alternative region if the region itself becomes unavailable.
+
+If your requirements include multi-region resilience, you can deploy separate projects in different regions and manage data routing or synchronization at the application level. Refer to [available Serverless regions](/deploy-manage/deploy/elastic-cloud/regions.md) for the supported options.

deploy-manage/toc.yml

@@ -364,6 +364,7 @@ toc:
               - file: production-guidance/availability-and-resilience/resilience-in-small-clusters.md
               - file: production-guidance/availability-and-resilience/resilience-in-larger-clusters.md
               - file: production-guidance/availability-and-resilience/resilience-in-ech.md
+              - file: production-guidance/availability-and-resilience/resilience-in-serverless.md
           - file: production-guidance/scaling-considerations.md
           - file: production-guidance/optimize-performance.md
             children: