diff --git a/data/updown.duckdb.wal b/data/updown.duckdb.wal
index a0c456b..ce02206 100644
Binary files a/data/updown.duckdb.wal and b/data/updown.duckdb.wal differ
diff --git a/deploy/README.md b/deploy/README.md
index 68ccbbd..a42f4a3 100644
--- a/deploy/README.md
+++ b/deploy/README.md
@@ -1,6 +1,6 @@
 # Overseas VPS Deployment
 
-This deployment keeps the dashboard bound to `127.0.0.1:8765` on the server. Access it with an SSH tunnel instead of exposing it publicly.
+This deployment maps the dashboard to `0.0.0.0:8765` on the server so it can be reached from outside the host. Restrict access with your cloud firewall, security group, VPN, or reverse proxy authentication.
 
 ## Recommended server
 
@@ -28,16 +28,17 @@ sudo systemctl status updown-dashboard
 
 ## Access dashboard
 
-From your laptop:
-
-```bash
-ssh -L 8765:127.0.0.1:8765 user@YOUR_SERVER_IP
-```
-
-Then open:
+Open:
 
 ```text
-http://127.0.0.1:8765
+http://YOUR_SERVER_IP:8765
+```
+
+If you prefer tunnel-only access, change `docker-compose.yml` back to:
+
+```yaml
+ports:
+  - "127.0.0.1:8765:8765"
 ```
 
 ## Logs and data
diff --git a/docker-compose.yml b/docker-compose.yml
index 15eab1c..749d7d8 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -4,7 +4,7 @@ services:
     container_name: updown-dashboard
     restart: unless-stopped
     ports:
-      - "127.0.0.1:8765:8765"
+      - "0.0.0.0:8765:8765"
     volumes:
       - ./data:/app/data
     environment: