{@render children()}
diff --git a/src/routes/docs/vps/about/+page.svx b/src/routes/docs/vps/about/+page.svx
new file mode 100644
index 0000000..7058f7a
--- /dev/null
+++ b/src/routes/docs/vps/about/+page.svx
@@ -0,0 +1,91 @@
+
+
+
+
+# About Stack VPS
+
+Here, you can learn more about what powers our stack and networking.
+
+---
+## Hardware
+
+### Servers
+
+For our compute nodes, we have 8 Dell PowerEdge R640 servers. Each server has 2 Intel Xeon Platinum 8260 CPUs. Each CPU has 24 cores running at 2.4 GHz with a boost clock of 3.9 GHz.
+
+Alongside our compute nodes, we have 3 Dell PowerEdge R740 servers. We combine all of our storage servers in a Ceph cluster, which you can read more about in the software section.
+
+### Networking
+
+We have 4 switches, 2 of which are SFP and the other 2 of which are Ethernet. Each switch also has QSFP+ ports for high-speed networking. Each Proxmox node has 2 SFP+ connections and 2 Ethernet connections in addition to their IPMI ethernet connections. Our storage nodes have QSFP+ connections for high-speed networking.
+
+---
+## Software
+
+Our software stack currently uses Proxmox for our hypervisor, VyOS for routing, Kea for DHCP, and Grafana for internal monitoring.
+
+### Hypervisor
+
+We use Proxmox as a solid baseline hypervisor with good high-availability support. We use its high availability to automatically provision VMs to balance resource use across our nodes. We also automatically rebalance load across our nodes using Proxmox's built-in Cluster Resource Scheduling feature. If a node needs to shut down, Proxmox will automatically migrate any running VMs to another node before shutting down. This helps us update our nodes without any downtime.
+
+For storage, we use Ceph to provide a scalable and fault-tolerant storage solution. Each storage node acts as a monitor, manager, and metadata server. We also use our first compute node as an additional monitor.
+
+Note that Proxmox is a temporary solution while we work on our own solution, [Odorobo](https://github.com/FyraStack/odorobo). Odorobo is a hypervisor based on [Cloud-Hypervisor](https://github.com/cloud-hypervisor/cloud-hypervisor), which will allow for quick start times and better resource utilization.
+
+### Networking
+
+Our routers run VyOS because of its reliability and configurability. We originally tried using OPNsense, but had issues with IPv6 subnet delegation. VyOS provides a more stable and flexible solution for our routing needs.
+
+---
+## VPS Networking
+
+By default, your VPS will be set up using `cloud-init` with the correct networking configuration. If you need to make changes to your networking configuration, you can do so by editing the appropriate configuration files for your distribution.
+
+### Notes
+
+Fyra Stack does not currently provide a firewall layer for your VPS, though it is planned in the future. You are responsible for configuring firewall rules on your server. See the [VPS hardening guide](https://fyrastack.com/docs/vps/hardening) for more information on setting up a firewall.
+
+By default, we block SMTP traffic to your VPS (port 25). If you would like to allow SMTP traffic, contact us at [support@fyralabs.com](mailto:support@fyralabs.com?subject=Allow%20SMTP%20traffic).
+Generally, we prefer to have some history of a user's behavior before allowing SMTP traffic, as SMTP is known to cause abuse complaints. For that reason, we may deny a request to unblock SMTP traffic if we don't have enough history on a user.
+
+Spoofing MAC addresses is considered network abuse under our [acceptable use policy](https://fyrastack.com/terms-of-service). Our system also won't allow you to access the internet if you try to spoof your MAC address. All traffic to and from your assigned public IP must come from your assigned MAC address. In addition, if you try to use a source IP address that isn't assigned to you, your traffic will be blocked.
+
+### How our VPS Network Works
+
+When you set up your VPS, we use [cloud-init](https://cloud-init.io/) to configure your networking. This includes assigning your static IP address, MAC address, routes, DNS, interface name, and disabling DHCP. If you're curious about an example cloud-init configuration, here's one with information redacted:
+
+```yaml
+version: 2
+ethernets:
+ public0:
+ match:
+ macaddress: $MAC_ADDRESS
+ set-name: eth0
+ dhcp4: false
+ dhcp6: false
+ addresses:
+ - $PUBLIC_IP_V4/32
+ - $PUBLIC_IP_V6/128
+ - $PUBLIC_IPV6_DELEGATION/64
+ routes:
+ - to: $PUBLIC_GATEWAY_V4/32
+ scope: link
+ - to: 0.0.0.0/0
+ via: $PUBLIC_GATEWAY_V4
+ on-link: true
+ - to: ::/0
+ via: $PUBLIC_GATEWAY_V6
+ on-link: true
+ nameservers:
+ addresses:
+ - 1.1.1.1
+ - 1.0.0.1
+ - 2606:4700:4700::1111
+ - 2606:4700:4700::1001
+```
diff --git a/src/routes/docs/vps/getting-started/+page.svx b/src/routes/docs/vps/getting-started/+page.svx
new file mode 100644
index 0000000..4eec8c0
--- /dev/null
+++ b/src/routes/docs/vps/getting-started/+page.svx
@@ -0,0 +1,59 @@
+
+
+
+
+# Getting Started with VPS
+
+Thanks for using Fyra Stack! VPS creation and management is handled through [Dashboard](https://dash.fyrastack.com). This page will walk you through the initial setup of your VPS.
+
+---
+## 1. Create and Account
+
+To get started, create an account on Dashboard at [https://dash.fyrastack.com](https://dash.fyrastack.com/register). Enter your name, email, and a password. You'll then receive a confirmation email. You must confirm your email before you can log in.
+
+---
+## 2. Create a Project
+
+Once you're logged in, hit the button to create a new project. Give it a name and click "Create".
+
+---
+## 3. Add Billing Information
+
+To add billing information, click on the "Billing" tab in the sidebar. Click "Set up billing," Enter your credit card details, and click "Save".
+
+---
+## (Optional) Add an SSH Key
+
+Open your terminal and run the following command to generate a new SSH key pair:
+
+```bash
+ssh-keygen -t ed25519
+```
+
+To get the public key, run the following command:
+
+```bash
+cat ~/.ssh/id_ed25519.pub
+```
+
+If you saved the key in a different location, look there and use `cat` on the file ending in `.pub`.
+
+Copy the line beginning with `ssh-ed25519` and ending with `username@hostname`. This is your public key, which you'll need to add to your VPS.
+
+On Dashboard, click on your profile icon and go to Keys. From there, paste in your public key, give it a name, and click add key.
+
+---
+## 4. Create a VPS
+
+Go to the servers tab on the side in project view. Click the plus icon to create a new VPS. Name your VPS, select your distribution (for more information, see [Choosing a Linux Distribution](/docs/vps/choosing-a-distro)), select your VPS tier, and add your SSH key. If you're not using an SSH key, **you MUST save your root password here**. Your generated root password **will not** be shown again, and if you lose it, you will not be able to access your VPS.
+
+---
+## Next: Connecting to Your VPS
+
+See our dedicated [Connecting via SSH](/docs/vps/ssh) doc.
diff --git a/src/routes/docs/vps/ssh/+page.svx b/src/routes/docs/vps/ssh/+page.svx
index b5c5d37..fcd1414 100644
--- a/src/routes/docs/vps/ssh/+page.svx
+++ b/src/routes/docs/vps/ssh/+page.svx
@@ -10,7 +10,7 @@
# Connecting via SSH
-Thanks for setting up a VPS with Fyra Stack! To connect to your server for the first time, you'll need an SSH client and the public IP address of your VPS. If you added an SSH key before creating the VPS, you can log in with that key. If you did not add a key during setup, log in as `root` with the default root password provided to you, then add your SSH key before continuing.
+To connect to your server for the first time, you'll need an SSH client and the public IP address of your VPS. If you added an SSH key before creating the VPS, you can log in with that key. If you did not add a key during setup, log in as `root` with the default root password provided to you, then add your SSH key before continuing.
---
@@ -28,31 +28,15 @@ If you did not add a key before creating the VPS, connect without `-i` and enter
ssh root@your_vps_ip
```
----
-
-## Generating an SSH key
-
-Open your terminal and run the following command to generate a new SSH key pair:
-
-```bash
-ssh-keygen -t ed25519
-```
+## Adding your Public Key to your VPS
-To get the public key, run the following command:
+If your VPS already exists and does not have your key installed, log in with the default root password provided to you and add the key using `ssh-copy-id`:
```bash
-cat ~/.ssh/id_ed25519.pub
+ssh-copy-id root@your_vps_ip
```
-If you saved the key in a different location, look there and use `cat` on the file ending in `.pub`.
-
-Copy the line beginning with `ssh-ed25519` and ending with `username@hostname`. This is your public key, which you'll need to add to your VPS.
-
-### Adding your Public Key to your VPS
-
-On the Fyra Stack Dashboard, click on your profile icon and go to Keys. From there, paste in your public key, give it a name, and click add key. Do this *before* creating your VPS when possible, as it is added during the initialization stage.
-
-If your VPS already exists and does not have your key installed, log in with the default root password provided to you and add the key manually:
+Alternatively, you can also add the key manually:
```bash
mkdir -p ~/.ssh
@@ -68,12 +52,6 @@ After saving, update the permissions on the authorized_keys file:
chmod 600 ~/.ssh/authorized_keys
```
-Alternatively, you can also use the `ssh-copy-id` command to add your key to the VPS:
-
-```bash
-ssh-copy-id root@your_vps_ip
-```
-
After updating the permissions, keep the root session open while you test key-based login from a new terminal.
```bash