Adding in a reference install diagram so users know what to expect

public/docs/img/installation/octopus-install-diagram.png.json

@@ -0,0 +1 @@
+{"width":2145,"height":1419,"updated":"2026-05-07T22:28:53.266Z"}

src/pages/docs/best-practices/self-hosted-octopus/installation-guidelines.mdx

@@ -21,6 +21,10 @@ There are three components to an Octopus Deploy instance:
 - **SQL Server Database** Most data used by the Octopus Server nodes is stored in this database.
 - **Files or BLOB Storage** Some larger files - like [packages](/docs/packaging-applications/package-repositories), artifacts, and deployment task logs - aren't suitable to be stored in the database and are stored on the file system instead.  This can be a local folder, a network file share, or a cloud provider's storage.  
 
+:::figure
+![Octopus Deploy Self-Hosted Reference Diagram](/docs/img/installation/octopus-install-diagram.png)
+:::
+
 This document will provide you with guidelines and recommendations for self-hosting Octopus Deploy.
 
 <OctopusReleases />

src/pages/docs/installation/index.mdx

@@ -33,6 +33,10 @@ All inbound traffic to Octopus Deploy is via:
 
 For production instances of Octopus Deploy, it is best to configure a [load balancer](/docs/installation/load-balancers) to route traffic to your instance.  Leveraging a load balancer offers numerous benefits, such as redirecting users to a maintenance page while the instance is down for upgrading, as well as making it much easier to configure High Availability later.
 
+:::figure
+![Octopus Deploy Self-Hosted Reference Diagram](/docs/img/installation/octopus-install-diagram.png)
+:::
+
 ## Self-hosted Octopus Server
 
 When installed, the self-hosted Octopus Server: