3.9K ·GitHub
What is this?
WechatOnCloud (云微) is a self-hosted panel that runs 'server-side WeChat' in a Docker container on your own NAS or server, so multiple browsers/devices can share the exact same logged-in session.
WechatOnCloud (云微) is a self-hosted panel that runs 'server-side WeChat' in a Docker container on your own NAS or server, so multiple browsers/devices can share the exact same logged-in session.Is this an app I install on my phone, or something I run on a server?It is a self-hosted web panel you deploy on a NAS or Docker host. It does not modify the WeChat client; instead it runs the real Linux WeChat (or Chromium) inside a headless container and streams the display to any browser via KasmVNC.
It is a self-hosted web panel you deploy on a NAS or Docker host. It does not modify the WeChat client; instead it runs the real Linux WeChat (or Chromium) inside a headless container and streams the display to any browser via KasmVNC.How do I get it running?Grab the docker-compose.yml from the repo (it pulls the prebuilt gloridust/woc-panel and wechat-on-cloud images from Docker Hub or GHCR) and run it with docker-compose. Then open the panel, create an instance (WeChat or Chromium), and scan the QR code to log in.
Grab the docker-compose.yml from the repo (it pulls the prebuilt gloridust/woc-panel and wechat-on-cloud images from Docker Hub or GHCR) and run it with docker-compose. Then open the panel, create an instance (WeChat or Chromium), and scan the QR code to log in.What do I need before I can run it?Just Docker with the Compose plugin on an x86_64 or arm64 host; no WeChat client install or extra runtime is required.
Just Docker with the Compose plugin on an x86_64 or arm64 host; no WeChat client install or extra runtime is required.What is the biggest safety pitfall when deploying this?The panel mounts the host's docker.sock to create/destroy instance containers, which is effectively root-level access, so anyone who can log into the panel can read your chats and send messages as you. The docs explicitly warn never to expose it directly on the public internet.
The panel mounts the host's docker.sock to create/destroy instance containers, which is effectively root-level access, so anyone who can log into the panel can read your chats and send messages as you. The docs explicitly warn never to expose it directly on the public internet.Does it work on consumer NAS boxes like Synology, or only on a generic server?Both — it's built for any Docker host (amd64/arm64), with first-class support for 飞牛 (fnOS) NAS and mentions Synology-style Compose deployment via pasting the docker-compose.yml directly in the Docker UI.
Both — it's built for any Docker host (amd64/arm64), with first-class support for 飞牛 (fnOS) NAS and mentions Synology-style Compose deployment via pasting the docker-compose.yml directly in the Docker UI.What can a Chromium instance be used for besides WeChat?A Chromium instance is a persistent cloud browser you can use to log into any web app — Telegram Web, X (Twitter), Instagram, WhatsApp Web, Discord, Gmail — and it stays logged in across restarts since the session is stored in the instance's data volume.
A Chromium instance is a persistent cloud browser you can use to log into any web app — Telegram Web, X (Twitter), Instagram, WhatsApp Web, Discord, Gmail — and it stays logged in across restarts since the session is stored in the instance's data volume.How do multiple people share the same WeChat session?Every instance is one container, and KasmVNC streams its display to the browser; multiple users connecting to the same instance are literally viewing/controlling the same session, with a soft lock that makes it read-only for others while one person is active.
Every instance is one container, and KasmVNC streams its display to the browser; multiple users connecting to the same instance are literally viewing/controlling the same session, with a soft lock that makes it read-only for others while one person is active.How much CPU and RAM does one instance need?Roughly 1 vCPU and 1.5 GiB RAM per active WeChat or Chromium instance (less when idle), plus about 0.15 GiB for the panel itself; a 4-core/8 GiB host can comfortably run 3-4 instances.
Roughly 1 vCPU and 1.5 GiB RAM per active WeChat or Chromium instance (less when idle), plus about 0.15 GiB for the panel itself; a 4-core/8 GiB host can comfortably run 3-4 instances.Do I lose my chat history or login if I restart or update an instance?No — instance data (WeChat login state, chat history, browser cookies) lives in a dedicated Docker volume per instance, so stopping, restarting, or upgrading the container to a newer image preserves it.
No — instance data (WeChat login state, chat history, browser cookies) lives in a dedicated Docker volume per instance, so stopping, restarting, or upgrading the container to a newer image preserves it.What are similar projects?Termix, WeKnora, logto, labtether, pictaria-server, claude-relay-service, casdoor, go-admin
Termix, WeKnora, logto, labtether, pictaria-server, claude-relay-service, casdoor, go-adminWhich topics is it in?vnc, multi-tenant, remote-desktop, self-hosting, arm64, pwa, rbac, reverse-proxy, wechat, telegram, authentication, docker-compose
vnc, multi-tenant, remote-desktop, self-hosting, arm64, pwa, rbac, reverse-proxy, wechat, telegram, authentication, docker-compose