Self-hosting

Two different things are easy to confuse: ChengOS is the platform you deploy on a server, and ChengApp is the client you install on a device. This page is about the former.

Deployment modes

The deployment script offers docker, hybrid (native) and distributed modes. Docker is the least work; hybrid suits teams with existing infrastructure who want to manage processes themselves.

The data boundary

When you deploy it yourself, business data stays in your database and the boundary is yours. That is a different proposition from using someone else’s hosted instance, and which one fits depends on your compliance requirements.

Upgrade and rollback

Upgrades use the same script. Back up the database first. A rollback has to move the application version and the database state together — rolling back only one side will not work.

Cross-network is a separate capability

ChengID / Hosted Coordinator carries user-to-user and user-to-agent sessions across networks. It is its own communication mode, not a fallback for a failed local link, and it does not act as a file data plane.

Questions people ask

If I deploy ChengOS, do I still need ChengApp?
Not necessarily. The platform ships a web interface; ChengApp adds a local desktop and mobile experience plus same-network collaboration.
Does deployment require public internet access?
No. Whether you need it depends on whether you want cross-network access and whether you call external model services.

Evidence for the claims on this page

Last verified:

支持原生与 Docker 私有化部署,服务端数据边界由部署方掌握。
Scope: 部署脚本覆盖 docker / hybrid / distributed 模式。
Source: deploy/chengos.sh 与 deploy/README.md ·
当前提供 Windows 与 Android 客户端;macOS 仅在路线图中,无 iOS 目标。
Scope: 以发布清单 lib/config/release-manifest.json 为准。
Source: lib/config/release-manifest.json ·
ChengID / Hosted Coordinator 支持跨网络的用户与用户、用户与 Agent 通信。
Scope: 独立的服务器通信模式,不是局域网直连失败后的降级;不承担文件数据面。
Source: ChengApp Hosted Coordinator 实现 ·