chainstack · akegaviar · Jan 29, 2026
diff --git a/docs/self-hosted/deploying-nodes.mdx b/docs/self-hosted/deploying-nodes.mdx
@@ -1,17 +1,18 @@
 ---
-title: "Deploying nodes"
+title: "Deploying nodes | Self-Hosted"
+sidebarTitle: "Deploying nodes"
 description: "How to deploy blockchain nodes using Chainstack Self-Hosted"
 ---
 
 This guide explains how to deploy blockchain nodes using Chainstack Self-Hosted.

 ## Supported deployments

 | Protocol | Network | Client | Node type |
 |----------|---------|--------|-----------|
 | Ethereum | Mainnet | Reth + Prysm | Full node |
 | Ethereum | Sepolia | Reth + Prysm | Full node |
 | Ethereum | Hoodi | Reth + Prysm | Full node |

 <Note>
 Additional protocols and networks are on the roadmap. See the [FAQ](/docs/self-hosted/faq) for details.
@@ -78,7 +79,7 @@

 ### Initial sync times

 Sync times depend on your hardware and network, but expect 2–5 days for Ethereum Mainnet. See [System requirements](/docs/self-hosted/requirements) for specifications and a community-maintained list of hardware recommendations.

 <Note>
 Snapshot-based deployment for faster initial sync is planned. See the [FAQ](/docs/self-hosted/faq#when-will-snapshot-based-deployment-be-available) for the timeline.

diff --git a/docs/self-hosted/faq.mdx b/docs/self-hosted/faq.mdx
@@ -1,17 +1,18 @@
 ---
-title: "FAQ"
+title: "FAQ | Self-Hosted"
+sidebarTitle: "FAQ"
 description: "Frequently asked questions about Chainstack Self-Hosted"
 ---
 
 ## General

 ### What is Chainstack Self-Hosted?

 Chainstack Self-Hosted brings the power of Chainstack's blockchain infrastructure platform to your own infrastructure. Deploy, manage, and monitor blockchain nodes on your own hardware or cloud environment while maintaining complete control over your data and infrastructure.

 ### Is Chainstack Self-Hosted ready for production?

 Chainstack Self-Hosted is currently in **beta**. We recommend using it for:

 - Development and testing environments
 - Proof-of-concept deployments
@@ -43,11 +44,11 @@

 **Q1 2026** — A proof of concept for archive node deployment is planned. Archive nodes require significantly more storage (15+ TB) and different sync strategies.

 ### Do you plan to support validator nodes?

 Validator node support is on the roadmap but is **not expected before late 2026**. Running validators requires additional considerations around uptime guarantees, slashing protection, and key management that we want to address properly.

 **Need validator support sooner?** Contact us at [Chainstack Feedback](https://ideas.chainstack.com/en?b=6968ecf76c93cb94db0422c8) to discuss your use case.

 ### Will you support multiple endpoints per node?

@@ -57,7 +58,7 @@

 ### What Kubernetes distributions are supported?

 Chainstack Self-Hosted works with any recent Kubernetes distribution:

 - k3s (tested and documented)
 - Standard Kubernetes (k8s)
@@ -72,19 +73,19 @@

 - 2 CPU cores, 2 GB RAM, 4 GB storage

 **Control Panel + Ethereum Mainnet node:**

 - 6 CPU cores, 18 GB RAM, 2+ TB NVMe SSD

 See [System requirements](/docs/self-hosted/requirements) for detailed specifications.

 ### Can I run multiple blockchain nodes on one server?

 Yes, provided you have sufficient resources. Each Ethereum full node requires approximately 4 CPU cores, 16 GB RAM, and 2 TB storage. Plan your infrastructure accordingly.

 ### Do I need a dedicated server or can I use a VM?

 Either works, as long as storage performance is adequate. For blockchain nodes, NVMe SSD storage is strongly recommended due to the high I/O requirements.

 <Warning>
 For VMs, ensure the virtual disk is backed by SSD storage, not HDD.
@@ -94,13 +95,13 @@

 ### How long does initial node sync take?

 Expect 2–5 days for Ethereum Mainnet, depending on your hardware and network. See [System requirements](/docs/self-hosted/requirements) for specifications and a community-maintained list of hardware recommendations.

 [Snapshot-based deployment](#when-will-snapshot-based-deployment-be-available) will reduce this significantly.

 ### How to find out the status of the initial node sync?

 At the moment, the only option is to check the corresponding pod logs. For example, if the Blockchain Node ID on **Chainstack Self-Hosted > Nodes > Node Details** is `6244046a-f344-4453-abd5-5bbbc0377422`, then you can check the logs in the following way:

 ```bash
 # List all pods and find the pods related to the node ID
@@ -118,7 +119,7 @@

 ### How do I resize the disk if storage runs out?

 As blockchain storage constantly grows, you may need to allocate more disk space to your node. This involves finding the right PVC and using `kubectl patch`.

 <Steps>
 <Step title="Find the node ID">
@@ -169,7 +170,7 @@

 ### How do I join the beta program?

 Fill out the beta signup form: [Join the Chainstack Self-Hosted Beta](https://3b81e.share.hsforms.com/2cWH4wEOeTOySPUNKOVDEEQ)

 ### What does the beta include?

@@ -204,7 +205,7 @@

 When reporting bugs, please include:

 - Version of Chainstack Self-Hosted
 - Steps to reproduce the issue
 - Relevant logs and error messages
 - Your environment details (K8s distribution, OS, etc.)
diff --git a/docs/self-hosted/first-login.mdx b/docs/self-hosted/first-login.mdx
@@ -1,9 +1,10 @@
 ---
-title: "First login"
+title: "First login | Self-Hosted"
+sidebarTitle: "First login"
 description: "First login to Chainstack Self-Hosted and initial configuration steps"
 ---
 
 This guide walks you through your first login to Chainstack Self-Hosted and initial configuration.

 ## First login

@@ -37,7 +38,7 @@
 | Ingress | `http://your-configured-hostname` |
 | Port forward | `http://<SERVER-IP>:8080` |

 You'll see the Chainstack Self-Hosted login page:

 <Frame>
  <img src="/images/self-hosted/login-page.png" alt="Chainstack Self-Hosted login page" />
@@ -76,14 +77,14 @@

 ## Understanding the interface

 The Chainstack Self-Hosted interface provides access to all node management functions.

 ### Main sections

 | Section | Purpose |
 |---------|---------|
 | **Nodes** | List, deploy, and manage blockchain nodes |
 | **Docs** | Link to Chainstack Self-Hosted documentation |
 | **Settings** | User profile and credentials |

 ### Node status indicators
@@ -100,7 +101,7 @@

 With your admin account configured, you're ready to:

 1. [Deploy your first node](/docs/self-hosted/deploying-nodes) — Deploy a blockchain node
 2. [Manage nodes](/docs/self-hosted/managing-nodes) — Learn node operations and monitoring

 ## Troubleshooting first login

diff --git a/docs/self-hosted/installation.mdx b/docs/self-hosted/installation.mdx
@@ -1,13 +1,14 @@
 ---
-title: "Installation"
+title: "Installation | Self-Hosted"
+sidebarTitle: "Installation"
 description: "Detailed instructions for installing Chainstack Self-Hosted with basic and advanced configuration options"
 ---
 
 This guide provides detailed instructions for installing Chainstack Self-Hosted, including advanced configuration options.

 ## Installation methods

 Chainstack Self-Hosted supports two installation modes:

 | Mode | Description | Use case |
 |------|-------------|----------|
@@ -102,7 +103,7 @@
 | Option | Description | Default |
 |--------|-------------|---------|
 | `-v, --version` | Self-hosted Control Panel version (required) | — |
 | `-n, --namespace` | Kubernetes namespace | `control-panel` |
 | `-r, --release` | Helm release name | `cp` |
 | `-f, --values` | Custom values file | — |
 | `-s, --storage-class` | Storage class for PostgreSQL | Cluster default |
@@ -180,9 +181,9 @@
 kubectl port-forward svc/cp-cp-ui 8080:80 -n control-panel --address 0.0.0.0
 ```

 ## Uninstallation

 To completely remove Chainstack Self-Hosted:

 ```bash
 ./cpctl uninstall
@@ -203,4 +204,4 @@
 After installation, continue to:

 1. [First login](/docs/self-hosted/first-login) — First login and configuration
 2. [Deploying nodes](/docs/self-hosted/deploying-nodes) — Deploy blockchain nodes
diff --git a/docs/self-hosted/introduction.mdx b/docs/self-hosted/introduction.mdx
@@ -1,24 +1,25 @@
 ---
-title: "Introduction"
+title: "Introduction | Self-Hosted"
+sidebarTitle: "Introduction"
 description: "Deploy and manage blockchain infrastructure in your own environment with complete control over your data"
 ---
 
 Welcome to the documentation for Chainstack Self-Hosted, a control plane for deploying and managing blockchain infrastructure in your own environment.

 <Note>
 Chainstack Self-Hosted is currently in beta. We actively welcome feedback and feature requests. See [how to join the beta](/docs/self-hosted/support#join-the-beta) for details.
 </Note>

 ## What is Chainstack Self-Hosted?

 Chainstack Self-Hosted brings the power of Chainstack's blockchain infrastructure platform to your own infrastructure. Deploy, manage, and monitor blockchain nodes on your own hardware or cloud environment while maintaining complete control over your data and infrastructure.

 ### Key features

 - Full infrastructure control — run blockchain nodes on your own servers, whether on premises, in a private cloud, or on dedicated servers
 - Simplified deployment — deploy blockchain nodes through an intuitive web interface without complex manual configuration
 - Enterprise-grade architecture — built on Kubernetes for reliability, scalability, and ease of operations
 - Ethereum protocol support — deploy Ethereum Mainnet full nodes with the high-performance Reth execution client and Prysm consensus client

 ## Getting help


diff --git a/docs/self-hosted/managing-nodes.mdx b/docs/self-hosted/managing-nodes.mdx
@@ -1,9 +1,10 @@
 ---
-title: "Managing nodes"
+title: "Managing nodes | Self-Hosted"
+sidebarTitle: "Managing nodes"
 description: "Node operations and management in Chainstack Self-Hosted"
 ---
 
 This guide covers the operations available for managing deployed blockchain nodes.

 ## Node list

@@ -38,8 +39,8 @@

 | Information | Description |
 |-------------|-------------|
 | Protocol | Blockchain protocol (e.g., Ethereum) |
 | Network | Network name (e.g., Mainnet, Hoodi) |
 | Date created | When the node was deployed |
 | Deployment ID | Unique identifier for the deployment |
 | Revision ID | Current revision of the deployment |

diff --git a/docs/self-hosted/quick-start.mdx b/docs/self-hosted/quick-start.mdx
@@ -1,29 +1,30 @@
 ---
-title: "Quick start"
+title: "Quick start | Self-Hosted"
+sidebarTitle: "Quick start"
 description: "Complete walkthrough from a fresh Ubuntu installation to a running Chainstack Self-Hosted Control Panel"
 ---
 
 This guide walks you through a complete installation of Chainstack Self-Hosted on a dedicated server, from a fresh Ubuntu installation to a running Control Panel.

 ## Overview

 By the end of this guide, you will have:

 - A Kubernetes cluster running on your server
 - The Chainstack Self-Hosted Control Panel deployed and accessible
 - The ability to deploy blockchain nodes through the web interface

 ## Prerequisites

 Before starting, ensure you have:

 - A dedicated server or virtual machine meeting the [system requirements](/docs/self-hosted/requirements)
 - Root or sudo access to the server
 - A stable internet connection

 ## End-to-end example

 This example uses a dedicated server from Contabo running Ubuntu 22.04, but the steps apply to any compatible server.

 <Steps>

@@ -275,15 +276,15 @@

 ## Next steps

 Congratulations! You now have Chainstack Self-Hosted running. Continue with:

 1. [First login](/docs/self-hosted/first-login) — First login and initial configuration
 2. [Deploying nodes](/docs/self-hosted/deploying-nodes) — Deploy your first blockchain node
 3. [Troubleshooting](/docs/self-hosted/troubleshooting) — If you encounter any issues

 ## Useful kubectl commands

 Set the default namespace to avoid typing `-n control-panel` every time:

 ```bash
 kubectl config set-context --current --namespace=control-panel

diff --git a/docs/self-hosted/release-notes.mdx b/docs/self-hosted/release-notes.mdx
@@ -1,6 +1,7 @@
 ---
-title: "Release notes"
+title: "Release notes | Self-Hosted"
+sidebarTitle: "Release notes"
 description: "Product updates and announcements for Chainstack Self-Hosted"
 rss: true
 ---


diff --git a/docs/self-hosted/requirements.mdx b/docs/self-hosted/requirements.mdx
@@ -1,16 +1,17 @@
 ---
-title: "System requirements"
+title: "System requirements | Self-Hosted"
+sidebarTitle: "System requirements"
 description: "Hardware, software, and network requirements for running Chainstack Self-Hosted"
 ---
 
 This page outlines the hardware, software, and network requirements for running Chainstack Self-Hosted.

 ## Overview

 Chainstack Self-Hosted consists of two main components with different resource requirements:

 1. **Control Panel** — the management platform that handles deployments, authentication, and orchestration
 2. **Blockchain nodes** — the actual blockchain clients that you deploy and manage

 ## Control Panel requirements

@@ -34,8 +35,8 @@
 |-----------|-------------|-------|
 | Kubernetes | Any recent version | k3s, k8s, EKS, GKE, AKS supported |
 | Helm | v3.x or later | Required for installation |
 | yq | v4.x or later | mikefarah/yq required |
 | openssl | Any recent version | Required for certificate generation |
 | kubectl | Compatible with cluster | Required for cluster management |

 ### Operating systems
@@ -57,47 +58,47 @@
 - **Cloud providers** — use the default storage class (gp2/gp3 for AWS, standard for GCP, managed-premium for Azure)
 - **On-premises** — any CSI-compatible storage provisioner

 ## Blockchain node requirements

 Resource requirements vary by protocol and node configuration. Below are the requirements for currently supported configurations.

 ### Ethereum Mainnet full node (Reth + Prysm)

 | Resource | Minimum | Recommended |
 |----------|---------|-------------|
 | CPU | 4 cores | 6+ cores |
 | RAM | 16 GB | 32 GB |
 | Storage | 2 TB NVMe SSD | 4 TB NVMe SSD |

 ### Ethereum Sepolia testnet full node (Reth + Prysm)

 | Resource | Minimum | Recommended |
 |----------|---------|-------------|
 | CPU | 4 cores | 6+ cores |
 | RAM | 16 GB | 32 GB |
 | Storage | 1.5 TB NVMe SSD | 2 TB NVMe SSD |

 ### Ethereum Hoodi testnet full node (Reth + Prysm)

 | Resource | Minimum | Recommended |
 |----------|---------|-------------|
 | CPU | 4 cores | 6+ cores |
 | RAM | 16 GB | 32 GB |
 | Storage | 250 GB NVMe SSD | 500 GB NVMe SSD |

 ### Storage considerations

 - **SSD type** — TLC NVMe drives are strongly recommended. Avoid QLC drives due to lower write endurance and performance
 - **Storage growth** — the Ethereum chain grows approximately 1 TB per year. Plan for 4 TB to ensure several years of headroom
 - **IOPS** — high random read/write performance is critical. Target drives with sustained write speeds of 1+ GB/s

 For a deep dive on SSD selection for Ethereum nodes, see [yorickdowne's SSD guide](https://gist.github.com/yorickdowne/f3a3e79a573bf35767cd002cc977b038).

 ### CPU considerations

 - Clock speed matters more than core count for blockchain nodes
 - Higher single-thread performance improves block processing
 - AMD Ryzen 7000/9000 series or Intel Core 12th gen+ recommended

 ### Initial sync time

@@ -120,7 +121,7 @@
 | cp-ui | 80 | TCP | Web interface |
 | cp-auth | 8080, 9090 | TCP | Authentication service |
 | cp-deployments-api | 8080, 9090 | TCP | Deployment management API |
 | keycloak | 80, 8080 | TCP | Identity management |
 | PostgreSQL | 5432 | TCP | Database |
 | Temporal | 7233–7246 | TCP | Workflow orchestration |

@@ -139,9 +140,9 @@

 For the Control Panel, only the UI service port needs to be accessible from outside the cluster. All other services communicate internally.

 For blockchain nodes, the required ports depend on the protocol:

 ### Ethereum nodes

 | Port | Protocol | Purpose |
 |------|----------|---------|
@@ -151,9 +152,9 @@

 ## Combined infrastructure example

 For a complete deployment running the Control Panel plus one Ethereum Mainnet full node:

 | Resource | Control Panel | Ethereum Node | Total |
 |----------|---------------|---------------|-------|
 | CPU | 2 cores | 4 cores | 6 cores |
 | RAM | 2 GB | 16 GB | 18 GB |
@@ -161,21 +162,21 @@

 ### Example server configurations

 #### Budget configuration (single Ethereum Mainnet node)

 - **CPU** — AMD Ryzen 5 7600 or Intel Core i5-13400
 - **RAM** — 32 GB DDR5
 - **Storage** — 4 TB NVMe SSD

 #### Testnet configuration (2 Ethereum testnet nodes)

 - **CPU** — AMD Ryzen 5 7600 or Intel Core i5-13400
 - **RAM** — 32 GB DDR5
 - **Storage** — 3 TB NVMe SSDs

 ## Next steps

 Once you've verified your system meets these requirements:

 1. [Quick start guide](/docs/self-hosted/quick-start) — Complete walkthrough from zero to running
 2. [Installation guide](/docs/self-hosted/installation) — Detailed installation instructions
diff --git a/docs/self-hosted/support.mdx b/docs/self-hosted/support.mdx
@@ -1,6 +1,7 @@
 ---
-title: "Support and feedback"
+title: "Support and feedback | Self-Hosted"
+sidebarTitle: "Support and feedback"
 description: "Get help, provide feedback, and join the Chainstack Self-Hosted beta program"
 ---
 
 Learn how to get help, provide feedback, and join the beta program.
@@ -11,7 +12,7 @@

 Start with the documentation for answers to common questions:

 - [Quick start guide](/docs/self-hosted/quick-start) — Installation walkthrough
 - [Troubleshooting](/docs/self-hosted/troubleshooting) — Common issues and solutions
 - [FAQ](/docs/self-hosted/faq) — Frequently asked questions

@@ -19,7 +20,7 @@

 For technical issues and questions:

 **Chainstack Support Center**

 [https://support.chainstack.com/hc/en-us](https://support.chainstack.com/hc/en-us)

@@ -45,11 +46,11 @@

 ### Community resources

 Additional resources for blockchain node operators:

 - Ethereum documentation: [ethereum.org/developers](https://ethereum.org/developers)
 - Reth documentation: [reth.rs](https://reth.rs/)
 - Prysm documentation: [docs.prylabs.network](https://docs.prylabs.network/)

 ## Providing feedback

@@ -73,7 +74,7 @@

 ## Join the beta

 Chainstack Self-Hosted is currently in beta, and we're actively looking for participants.

 ### What beta participants receive

@@ -84,7 +85,7 @@

 ### How to join

 Fill out the beta signup form:

 <Card title="Join the Chainstack Self-Hosted Beta" icon="rocket" href="https://3b81e.share.hsforms.com/2cWH4wEOeTOySPUNKOVDEEQ">
  Get early access to new features and direct communication with the product team.
@@ -109,4 +110,4 @@
 |---------|---------|
 | Technical support | [support.chainstack.com](https://support.chainstack.com/hc/en-us) |
 | Feature requests | [Chainstack Feedback](https://ideas.chainstack.com/en?b=6968ecf76c93cb94db0422c8) |
 | Beta signup | [Signup form](https://3b81e.share.hsforms.com/2cWH4wEOeTOySPUNKOVDEEQ) |
diff --git a/docs/self-hosted/supported-clients-and-protocols.mdx b/docs/self-hosted/supported-clients-and-protocols.mdx
@@ -1,17 +1,18 @@
 ---
-title: "Supported clients and protocols"
+title: "Supported clients and protocols | Self-Hosted"
+sidebarTitle: "Supported clients and protocols"
 description: "Blockchain protocols and networks available in Chainstack Self-Hosted"
 ---
 
 This page lists the node clients, blockchain protocols, and networks currently supported by Chainstack Self-Hosted.

 ## Available configurations

 | Protocol | Network | Client | Node type |
 |----------|---------|--------|-----------|
 | Ethereum | Mainnet | Reth + Prysm | Full node |
 | Ethereum | Sepolia | Reth + Prysm | Full node |
 | Ethereum | Hoodi | Reth + Prysm | Full node |

 <Note>
 Additional protocols and networks are planned for future releases. See the [FAQ](/docs/self-hosted/faq) for the roadmap.

diff --git a/docs/self-hosted/troubleshooting.mdx b/docs/self-hosted/troubleshooting.mdx
@@ -1,9 +1,10 @@
 ---
-title: "Troubleshooting"
+title: "Troubleshooting | Self-Hosted"
+sidebarTitle: "Troubleshooting"
 description: "Diagnose and resolve common issues with Chainstack Self-Hosted"
 ---
 
 This guide helps you diagnose and resolve common issues with Chainstack Self-Hosted.

 ## Installation troubleshooting

@@ -31,7 +32,7 @@
 curl https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3 | bash
 ```

 #### yq not found or wrong version

 ```bash
 # Must be mikefarah/yq v4+
@@ -153,7 +154,7 @@
 kubectl logs -l app.kubernetes.io/name=cp-auth -n control-panel
 ```

 #### Check Keycloak

 ```bash
 kubectl get pods -l app.kubernetes.io/name=keycloak -n control-panel
@@ -305,7 +306,7 @@

 When contacting support, include:

 - Version of Chainstack Self-Hosted
 - Kubernetes distribution and version
 - `diagnostic.txt` file
 - `debug-$timestamp.txt` file