update references to deployment modes

Author: jordanstephens

blog/2025-03-14-deploying-defang-with-defang-part-1.md

@@ -61,7 +61,7 @@ This wasn’t just about reducing complexity—it was also a validation exercise
 
 ### Deployment Modes
 
-- [**Deployment modes**](/docs/concepts/deployment-modes) (`development`, `staging`, `production`) adjust infrastructure settings across our dev/staging/prod deployments making sure dev is low cost, and production is secure and resilient.
+- [**Deployment modes**](/docs/concepts/deployment-modes) (`affordable`, `balanced`, `high_availability`) adjust infrastructure settings across our dev/staging/prod deployments making sure dev is low cost, and production is secure and resilient.
 
 ### **DNS & Certs**
 

docs/concepts/deployment-modes.md

@@ -6,22 +6,22 @@ sidebar_position: 501
 
 # Deployment Modes
 
-Defang provides three deployment modes: development, staging, and production. These modes allow you to balance cost and resiliency according to your needs.
+Defang provides three deployment modes: `affordable`, `balanced`, and `high_availability`. These modes allow you to balance cost and resiliency according to your needs.
 
-* **Development**: This mode is used for development and testing purposes. It typically involves less stringent resource allocations and may include debugging tools and verbose logging to aid in development.
-* **Staging**: This mode serves as a pre-production environment where applications are tested in conditions that closely mimic production. It helps in identifying issues that might not be apparent in the development environment.
-* **Production**: This mode is used for live deployments. It involves optimized configurations for performance, security, and reliability. Resource allocations are typically higher, and debugging tools are minimized to ensure stability.
+* **Affordable**: This mode is used for development and testing purposes. It typically involves less stringent resource allocations and may include debugging tools and verbose logging to aid in development.
+* **Balanced**: This mode serves as a pre-production environment where applications are tested in conditions that closely mimic production. It helps in identifying issues that might not be apparent in the development environment.
+* **High Availability**: This mode is used for live deployments. It involves optimized configurations for performance, security, and reliability. Resource allocations are typically higher, and debugging tools are minimized to ensure stability.
 
 ## Deployment Mode Comparison
 
-| Feature | Development | Staging | Production |
+| Feature | Affordable | Balanced | High Availability |
 |-|-|-|-|
 | Build Resources | Builds will be run with 2x vCPUs | Builds will be run with 2x vCPUs | Builds will be run with 4x vCPUs |
-| Compute | Using spot instances | (like development) | On-demand instances |
-| Databases | Defang will provision resources optimized for burstable memory | (like production) | Defang will provision resources optimized for production |
-| Deployment | Previous deployments will be spun down before new deployments are spun up. | (like production) | Rolling updates will be used to deploy new versions. Defang will gradually replace services while maintaining at least [the original number of replicas](/docs/tutorials/scaling-your-services). |
+| Compute | Using spot instances | (like `affordable`) | On-demand instances |
+| Databases | Defang will provision resources optimized for burstable memory | (like `high_availability`) | Defang will provision resources optimized for production |
+| Deployment | Previous deployments will be spun down before new deployments are spun up. | (like `high_availability`) | Rolling updates will be used to deploy new versions. Defang will gradually replace services while maintaining at least [the original number of replicas](/docs/tutorials/scaling-your-services). |
 | Logging | Logs retained for 1 day to save costs. | | Logs retained for 30 days for compliance. |
-| Networking | | (like production) | Defang will provision a NAT gateway. |
+| Networking | | (like `high_availability`) | Defang will provision a NAT gateway. |
 | Load Balancing | HTTP redirect to HTTPS using `302 Found` | | Termination Protection will be enabled; logs are retained on "down" |
 | DNS | Defang will provision shorter TTLs; zones will be forcefully destroyed | | Defang will provision longer TTLs; records can be overwritten for ZDT |
 | Managed storage | Operations that cause downtime are allowed | | Encryption at rest; Final snapshot created on "down" |

docs/concepts/deployments.md

@@ -6,17 +6,17 @@ sidebar_position: 500
 
 # Deployment
 
-When you deploy using Defang, whether it's with `defang compose up` with a [Compose file](./compose.md) or using a [Pulumi program](./pulumi.md), Defang will build your services in the cloud and manage the deployment process for you. If you provide a Dockerfile and build context, Defang will upload the files found within the build context to the cloud (either yours in [Defang BYOC](./defang-byoc.md) or ours in [Defang Playground](./defang-playground.md)), build the image, and store it in the cloud provider's container registry. 
+When you deploy using Defang, whether it's with `defang compose up` with a [Compose file](./compose.md) or using a [Pulumi program](./pulumi.md), Defang will build your services in the cloud and manage the deployment process for you. If you provide a Dockerfile and build context, Defang will upload the files found within the build context to the cloud (either yours in [Defang BYOC](./defang-byoc.md) or ours in [Defang Playground](./defang-playground.md)), build the image, and store it in the cloud provider's container registry.
 
 ## Deploying Updates
 
 When you run a deployment to update one or more [services](/docs/concepts/services), Defang will build new images for your services, and provision new resources to replace your existing services.
 
 ### Zero Downtime Deployments
 
-Defang can deploy your services using different [modes](/docs/concepts/deployment-modes). When using the `production` mode, Defang will make sure the new replacement services are healthy before deprovisioning your existing services.
+Defang can deploy your services using different [modes](/docs/concepts/deployment-modes). When using the `high_availability` mode, Defang will make sure the new replacement services are healthy before deprovisioning your existing services.
 
-By default, using the `development` mode, Defang will deprovision your existing services before provisioning replacements. This helps reduce costs.
+By default, using the `affordable` mode, Defang will deprovision your existing services before provisioning replacements. This helps reduce costs.
 
 :::info
 In [Defang BYOC](./defang-byoc.md), Defang uses your cloud provider account to build and store your images. In [Defang Playground](./defang-playground.md), we build and store your images for you.
@@ -25,14 +25,15 @@ In [Defang BYOC](./defang-byoc.md), Defang uses your cloud provider account to b
 
 ### Deployment Modes
 
-As mentioned above, Defang offers different [deployment modes](/docs/concepts/deployment-modes): `development`, `staging`, and `production`. You can switch the modes using the `--mode` CLI flag.
+As mentioned above, Defang offers different [deployment modes](/docs/concepts/deployment-modes): `affordable`, `balanced`, and `high_availability`. You can switch the modes using the `--mode` CLI flag.
+
 :::warning
 Workloads with GPUs do not support zero downtime deployments. If you have a workload with a GPU, you will experience downtime during updates.
 :::
 
 ## Instance Types
 
-Defang defaults to "spot" instances. This is a cost-effective way to run your workloads, but it does mean that your workloads can be interrupted at any time. This is consistent with the [12 Factor](https://12factor.net/) principle of [disposability](https://12factor.net/disposability). 
+Defang defaults to "spot" instances. This is a cost-effective way to run your workloads, but it does mean that your workloads can be interrupted at any time. This is consistent with the [12 Factor](https://12factor.net/) principle of [disposability](https://12factor.net/disposability).
 
 :::info
 In the future, we may provide a way to use "on-demand" instances for workloads that require more stability.

docs/tutorials/updating-your-services.md

@@ -18,7 +18,7 @@ If you are using [Compose files](../concepts/compose.md) to define your services
 
 ## Deployment Modes
 
-Defang offers multiple [deployment modes](/docs/concepts/deployment-modes). You can specify which mode you would like to be used when you deploy with the `--mode` flag on the CLI. The default mode is `development`. You may also specify `staging` or `production`.
+Defang offers multiple [deployment modes](/docs/concepts/deployment-modes). You can specify which mode you would like to be used when you deploy with the `--mode` flag on the CLI. The default mode is `affordable`. You may also specify `balanced` or `high_availability`.
 
 ```shell
 $ defang compose up --mode=production