diff --git a/src/SUMMARY.md b/src/SUMMARY.md
index bb18000e..24b518c8 100644
--- a/src/SUMMARY.md
+++ b/src/SUMMARY.md
@@ -69,3 +69,4 @@
   - [Timer API](./apis/timer.md)
   - [VFS API](./apis/vfs.md)
   - [WebSocket API](./apis/websocket_authentication.md)
+- [Hosted Nodes User Guide](./hosted-nodes.md)
diff --git a/src/hosted-nodes.md b/src/hosted-nodes.md
new file mode 100644
index 00000000..da481ead
--- /dev/null
+++ b/src/hosted-nodes.md
@@ -0,0 +1,88 @@
+# Hosted Nodes User Guide
+
+Kinode DAO runs a Kinode hosting service for users who do not want to run a Kinode themselves.
+These hosted Kinodes are useful for both end users and developers.
+This guide is largely targeted at developers who want to develop Kinode applications using their hosted Kinode.
+End users may also find the [Managing Your Kinode](#managing-your-kinode) section useful.
+
+Here, we use `ssh` extensively.
+This guide is specifically tailored to `ssh`s use for the Kinode hosting service.
+A more expansive guide can be found [here](https://www.digitalocean.com/community/tutorials/ssh-essentials-working-with-ssh-servers-clients-and-keys).
+
+## Managing Your Kinode
+
+[Valet](https://valet.kinode.org/) is the interface for managing your Kinode hosted by Kinode DAO.
+Kinode DAO plans to open-source the hosting code so there will be other hosting options in the future.
+Once logged in, `Your Kinodes` will be displayed: clicking on the name of a Kinode will navigate to the homepage for that Kinode.
+Clicking on the gear icon will open a modal with some information about the Kinode.
+Click `Show advanced details` to reveal information for accessing your Kinode's terminal.
+
+## Accessing Your Kinode's Terminal
+
+As discussed in [Managing Your Kinode](#managing-your-kinode), navigate to:
+1. https://valet.kinode.org/
+2. `Your Kinodes`
+3. Gear icon
+4. `Show advanced details`
+
+In the advanced details, note the `SSH Address` and `SSH Password`.
+Here and below, the following SSH details will be assumed (you'll need to replace them with yours from `advanced details`):
+
+Field           | Value
+--------------- | -----
+SSH Address     | kexampleuser@template.hosting.kinode.net
+SSH Password    | 123456789
+Local HTTP Port | 8099
+
+To access your Kinode remote instance, open a terminal and
+```bash
+ssh kexampleuser@template.hosting.kinode.net
+```
+where `kexampleuser@template.hosting.kinode.net` should be the `user@kinode_name.hosting.kinode.net` in your `SSH Address`.
+You will be prompted for a password: copy-paste the `SSH Password`.
+
+You should now have a different terminal prompt, indicating you have `ssh`d into the remote instance hosting your Kinode.
+
+### Using SSH keys
+
+Rather than typing in a password to create a SSH connection, you can use a keypair.
+
+#### Generating Keypair
+
+https://docs.github.com/en/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key
+
+#### `ssh-agent`
+
+https://docs.github.com/en/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent
+
+#### SSH Config
+
+https://www.digitalocean.com/community/tutorials/ssh-essentials-working-with-ssh-servers-clients-and-keys#defining-server-specific-connection-information
+
+#### Adding Public Key to Remote Node
+
+https://www.digitalocean.com/community/tutorials/ssh-essentials-working-with-ssh-servers-clients-and-keys#copying-your-public-ssh-key-to-a-server-with-ssh-copy-id
+
+## Using `kit` With Your Hosted Node
+
+`kit` interacts with a Kinode through the Kinode's HTTP RPC.
+However, Kinode limits HTTP RPC access to localhost: remote requests are rejected.
+The local limit is a security measure, since the HTTP RPC allows injection of arbitrary messages with "root" capabilities.
+
+To use `kit` with a hosted node, you need to create a SSH tunnel, which maps a port on your local machine to a port on the Kinode's remote host.
+HTTP requests routed to that local port will then appear to the remote host as originating from its localhost.
+
+Create a SSH tunnel like so (again, replacing [assumed values with those in your `advanced details`](#accessing-your-kinodes-terminal)):
+```bash
+ssh -L 9090:localhost:8099 kexampleuser@template.hosting.kinode.net -f -N
+```
+or, if you've added your host to your [`~/.ssh/config`](#ssh-config),
+```bash
+ssh -L 9090:localhost:8099 template -f -N
+```
+
+Now, `kit` requests sent to `9090` will be routed to the remote Kinode, e.g.,
+```
+kit s foo -p 9090
+```
+will function the same as for a locally-hosted Kinode.