# Network Deployments

> Step-by-step workflows and component-level customization for users who need full control over network initialization, configuration, and scaling. Explore YAML-driven deployments, manual orchestration, dynamic node management, and extensive reference documentation.

URL: https://solo.hiero.org/docs/advanced-solo-setup/network-deployments/

- [One-shot Falcon Deployment](https://solo.hiero.org/docs/advanced-solo-setup/network-deployments/falcon-deployment.md): Deploy a complete Solo network from a single YAML file for repeatable advanced setups, CI pipelines, and custom component configuration. Falcon combines simplicity with full customization using the Solo values file format.
- [Falcon Values File Reference](https://solo.hiero.org/docs/advanced-solo-setup/network-deployments/falcon-flags-reference.md): Comprehensive reference for all supported CLI flags per section of a Falcon values file, including defaults, types, and descriptions. Use this as your source of truth when customizing Falcon deployments.
- [Step-by-Step Manual Deployment](https://solo.hiero.org/docs/advanced-solo-setup/network-deployments/manual-deployment.md): Deploy each Solo network component individually for maximum control over configuration and debugging. Execute each step manually through the Solo CLI and integrate Solo into bespoke automation pipelines.
- [Custom Application Properties](https://solo.hiero.org/docs/advanced-solo-setup/network-deployments/custom-application-properties.md): Configure consensus node application.properties with Solo's default merge mode or full overwrite mode.
- [Dynamically add, update, and remove Consensus Nodes](https://solo.hiero.org/docs/advanced-solo-setup/network-deployments/consensus-node-operations.md): Learn how to dynamically add, update, and remove consensus nodes in a running Solo network without taking the network offline. Execute operations independently while the network remains operational.
- [Consensus Node Environment Variables](https://solo.hiero.org/docs/advanced-solo-setup/network-deployments/consensus-node-environment-variables.md): Pass environment variables to the consensus node JVM with an application.env file and the --application-env flag.

## Pages in this section

- [One-shot Falcon Deployment](https://solo.hiero.org/docs/advanced-solo-setup/network-deployments/falcon-deployment.md): Deploy a complete Solo network from a single YAML file for repeatable advanced setups, CI pipelines, and custom component configuration. Falcon combines simplicity with full customization using the Solo values file format.
- [Falcon Values File Reference](https://solo.hiero.org/docs/advanced-solo-setup/network-deployments/falcon-flags-reference.md): Comprehensive reference for all supported CLI flags per section of a Falcon values file, including defaults, types, and descriptions. Use this as your source of truth when customizing Falcon deployments.
- [Step-by-Step Manual Deployment](https://solo.hiero.org/docs/advanced-solo-setup/network-deployments/manual-deployment.md): Deploy each Solo network component individually for maximum control over configuration and debugging. Execute each step manually through the Solo CLI and integrate Solo into bespoke automation pipelines.
- [Custom Application Properties](https://solo.hiero.org/docs/advanced-solo-setup/network-deployments/custom-application-properties.md): Configure consensus node application.properties with Solo's default merge mode or full overwrite mode.
- [Dynamically add, update, and remove Consensus Nodes](https://solo.hiero.org/docs/advanced-solo-setup/network-deployments/consensus-node-operations.md): Learn how to dynamically add, update, and remove consensus nodes in a running Solo network without taking the network offline. Execute operations independently while the network remains operational.
- [Consensus Node Environment Variables](https://solo.hiero.org/docs/advanced-solo-setup/network-deployments/consensus-node-environment-variables.md): Pass environment variables to the consensus node JVM with an application.env file and the --application-env flag.
