snapshot of https://github.com/mattermost/mattermost.git (master, 2026-09-16; blobs > 131072B omitted)

docs/main/deployment-guide/deployment-architecture.mdx

@@ -0,0 +1,31 @@
+---
+title: "Size your deployment"
+description: Interactive deployment architecture builder. Pick a scale tier, deployment type, and hosting provider — get an architecture diagram and a bill of materials.
+---
+
+Pick your scale tier, deployment type, and hosting provider. The builder below renders a target architecture and a bill of materials sized to those choices. Sizing follows the [Mattermost scaling guide](/deployment-guide/scale/scaling-for-enterprise); provider SKUs are illustrative — verify against current pricing and regional / compliance constraints before committing to a procurement decision.
+
+<DeploymentArchitectureBuilder />
+
+## How to use this page
+
+1. **Pick the scale tier** that fits your expected concurrent user count. Tiers correspond to the named bands in the scaling guide (Trial / Small / Medium / Large / Extra Large / Mega / Hyperscale).
+2. **Pick a deployment type**:
+    - **Virtual machines** — Mattermost installed via the [Linux install paths](/deployment-guide/server/deploy-linux), with a separate VM per role (app, database, cache, search). Most common for self-hosted and private-cloud deployments.
+    - **Kubernetes** — Mattermost deployed via the [Mattermost Operator](/deployment-guide/server/deploy-kubernetes). The diagram and bill of materials swap the load balancer for an ingress controller and the app row for the Operator pattern.
+3. **Pick a hosting provider** to see provider-specific SKU recommendations. **On-prem / Other** swaps managed services for self-managed equivalents (PostgreSQL on a VM, Redis on a VM, OpenSearch / Elasticsearch on a VM cluster, MinIO or NFS for object storage).
+
+## What's next
+
+Once you've sized the architecture:
+
+- For **air-gapped** environments, also work through [Air-Gapped Operations](/deployment-guide/air-gapped-operations/quick-start-runbook). The architecture is the same; the install procedure and dependency-staging are different.
+- For **HA tuning** (clustering, Redis configuration, multi-AZ database topology), see [High Availability cluster-based deployment](/deployment-guide/server/high-availability-cluster-based-deployment).
+- For **version and hardware minimums** on the components you just sized, see [Software and hardware requirements](/deployment-guide/software-hardware-requirements), the last step in Plan.
+- To **choose an install path**, see [Deploy the Mattermost server](/deployment-guide/server/deploy-server), which compares Kubernetes, Linux, and containers.
+
+:::note[Where this page sits]
+
+This is the second step in [Plan](/deployment-guide/server/server-deployment-planning), after [Application architecture](/deployment-guide/application-architecture). If you haven't picked the *shape* of the deployment yet, [Deployment Scenarios](/deployment-guide/deployment-scenarios/deployment-scenarios-index) covers which operational pattern fits (air-gapped, mission partner, DDIL, sovereign-Microsoft, out-of-band); this page sizes **the components** of whichever shape you pick.
+
+:::