docs: add private cloud (#1382)

* docs: add private cloud

* refactor: apply suggestions from code review

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

* chore: fix lint

---------

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

Author: gao-sun

docs/logto-cloud/README.mdx

@@ -6,7 +6,7 @@ import McpIcon from '@site/src/assets/mcp.svg';
 import CustomDomains from '@site/src/assets/search.svg';
 import SystemLimit from '@site/src/assets/security.svg';
 
-# Logto cloud service
+# Logto Cloud
 
 [Logto Cloud](https://cloud.logto.io) offers a range of management and operational services to help you manage identities and resources smoothly and easily. Hosted by Logto, it includes features like [multi-region support](/logto-cloud/tenant-settings#tenant-region), tenant management, [billing and pricing](/logto-cloud/billing-and-pricing), [member management](/logto-cloud/tenant-member-management), and console role-based access control.
 

docs/logto-cloud/private-cloud.mdx

@@ -0,0 +1,55 @@
+---
+id: private-cloud
+title: Private Cloud
+sidebar_position: 5.1
+---
+
+# Logto Private Cloud
+
+Deploy Logto in a dedicated Azure environment for stronger isolation, compliance alignment, and infrastructure control.
+
+## Overview \{#overview}
+
+Logto Private Cloud is a dedicated deployment option for customers that need more infrastructure isolation and control than a shared public cloud environment.
+
+It is designed for organizations with stricter security, compliance, procurement, or deployment requirements, while keeping the same core product experience as Logto Cloud.
+
+Here is how the deployment options differ:
+
+- **Logto Cloud**: managed public cloud, fastest path to production
+- **Logto Private Cloud**: dedicated deployment for customers with stricter infrastructure or compliance requirements
+- **Logto OSS**: self-hosted and self-managed
+
+## When to choose Private Cloud \{#when-to-choose-private-cloud}
+
+Logto Private Cloud is usually the right fit when your organization requires one or more of the following:
+
+- Stronger environment isolation
+- SLA-backed uptime commitment, with support and collaboration from the Logto team
+- Specific compliance requirements that cannot be met by a shared public cloud
+- Deployment in a specific region or infrastructure that is not supported by Logto Cloud
+- Connection to internal resources that cannot be accessed from a public cloud environment
+
+If you do not have these requirements, [Logto Cloud](https://cloud.logto.io/?sign_up=1) is usually the better choice because it is simpler to adopt and easier to operate.
+
+### Deployment scope \{#deployment-scope}
+
+Logto Private Cloud is currently available on **Azure** only.
+
+Supported regions depend on whether the Azure region provides the services required by Logto. If you have a target region in mind, contact us and we can confirm feasibility based on your requirements.
+
+### Security and compliance \{#security-and-compliance}
+
+Private Cloud provides a dedicated environment with clearer isolation boundaries than a shared public cloud deployment.
+
+We keep security and compliance discussions practical and requirement-driven. If your team needs a security review, compliance discussion, or deployment-specific clarification, contact us and we can go through the details directly.
+
+## Contact us \{#contact-us}
+
+If you are considering Private Cloud, [contact us](https://logto.io/contact?src=private-cloud) with:
+
+- your target Azure region
+- security or compliance requirements
+- migration context, if any
+
+We will help you evaluate fit and discuss the next steps.