diff --git a/Nakama-Deployment.-.md b/Nakama-Deployment.-.md
new file mode 100644
index 0000000..5e15dfd
--- /dev/null
+++ b/Nakama-Deployment.-.md
@@ -0,0 +1,27 @@
+# Nakama Deployment
+
+After generating an updated `tekton_admin.js` locally (see [Skin Creation Workflow](./Skin-Creation-Workflow) or the Gacha editor), push it to the remote Nakama server.
+
+## Steps
+
+1. **Copy the latest script** — open `server/nakama/tekton_admin.js` locally and copy its full contents.
+2. **SSH into the VPS.**
+3. **Create or edit the file on the remote server:**
+   ```bash
+   nano ~/tekton_admin.js
+   # or, recommended:
+   micro ~/tekton_admin.js
+   ```
+   Paste the copied contents and save.
+4. **Find your Nakama Container ID.** Lazydocker is highly recommended:
+   ```bash
+   # Install lazydocker on Ubuntu:
+   curl https://raw.githubusercontent.com/jesseduffield/lazydocker/master/scripts/install_update_linux.sh | bash
+   ```
+   Open lazydocker, or run `docker ps` to find the Container ID.
+5. **Copy the file into the Nakama container:**
+   ```bash
+   # Replace ed21ac5d442a with your actual Container ID
+   docker cp ~/tekton_admin.js ed21ac5d442a:/nakama/data/modules/tekton_admin.js
+   ```
+6. **Restart the container** (via lazydocker or `docker restart <Container ID>`). Nakama reloads the modules and live game clients fetch the new catalog on next boot.