https://solo.hiero.org/tags/manual-deployment/Recent content in Manual-Deployment on SoloHugoenhttps://solo.hiero.org/docs/advanced-solo-setup/network-deployments/Mon, 01 Jan 0001 00:00:00 +0000https://solo.hiero.org/docs/advanced-solo-setup/network-deployments/https://solo.hiero.org/docs/advanced-solo-setup/network-deployments/manual-deployment/Mon, 01 Jan 0001 00:00:00 +0000https://solo.hiero.org/docs/advanced-solo-setup/network-deployments/manual-deployment/<h2 id="overview">Overview<a class="td-heading-self-link" href="#overview" aria-label="Heading self-link"></a></h2> <p>Manual deployment lets you deploy each Solo network component individually, giving you full control over configuration, sequencing, and troubleshooting. Use this approach when you need to customise specific steps, debug a component in isolation, or integrate Solo into a bespoke automation pipeline.</p> <hr> <h2 id="prerequisites">Prerequisites<a class="td-heading-self-link" href="#prerequisites" aria-label="Heading self-link"></a></h2> <p>Before proceeding, ensure you have completed the following:</p> <ul> <li> <p><a href="https://solo.hiero.org/docs/advanced-solo-setup/system-readiness"><strong>System Readiness</strong></a> — your local environment meets all hardware and software requirements (Docker, kind, kubectl, helm, Solo).</p>