Introducing Crowntime WeCom Archive: An Open-Source, Self-Hosted WeCom Conversation Archive

[zuohaisu]

中文版 → Crowntime WeCom Archive 正式开源

---

Introducing Crowntime WeCom Archive

On October 9, 2026, Crowntime (Shenzhen Crowntime Technology Co., Ltd., 康冠时代) released Crowntime WeCom Archive as open source under the AGPL-3.0 license. v1.1.0 is the project's first public release.

• GitHub (primary repository): https://github.com/zuohaisu/wecom-archive
• Gitee mirror: https://gitee.com/zuohaisu/wecom-archive
• Website: https://www.crowntime.cn/

A complete application, not an SDK wrapper

Tencent ships a conversation-archive C SDK (libWeWorkFinanceSdk_C.so) and a set of APIs for WeCom. Turning those into something an organization can actually use still means building everything around them: message retrieval, decryption, and normalization; durable message and media storage; multi-tenant isolation; administrator authentication and role-based permissions; a review console with search; export approval; audit logging; deployment and operations tooling.

The real cost lives in that application layer, and this project implements it end to end and ships it as a complete, self-hostable product. The codebase started as a system our own small team ran in production before it was opened up.

Core capabilities

• Message synchronization, decryption, normalization, and history handling
• Media archiving for text, images, voice, video, and files
• Conversation review, message search, and contact management
• Multi-tenant isolation, authentication, and role-based access control
• Media management, export approval, and audit logging
• Health monitoring, diagnostics, and an admin console

The stack is a FastAPI application (web console plus workers) with PostgreSQL; media can be stored on a local filesystem or an object-storage backend.

Self-hosting with Docker Compose

The Compose stack includes PostgreSQL 16, database migrations, the web console, and the archive/media workers. In short:

1. Copy .env.example to .env, set a database password, and generate two Fernet encryption keys;
2. Obtain the Tencent SDK and place it under backend/vendor/wecom_sdk/;
3. docker compose up -d --build;
4. Open http://127.0.0.1:8035/admin/settings/init and create the administrator;
5. Enter and test your tenant's archive credentials in the setup wizard, then run the first sync worker.

Full walkthrough: the README quickstart and the Installation guide in the Wiki.

The self-hosted edition is complete, not a trial: it requires no Crowntime cloud subscription and does not stop working when a subscription would expire. Your database and media stay on your own infrastructure.

The Tencent SDK dependency

Message retrieval and decryption depend on Tencent's proprietary C SDK, which is not included in this repository or its images. You obtain the SDK directly from Tencent under its terms, together with a WeCom organization that has conversation archiving enabled and the corresponding credentials. Production callbacks also need a public HTTPS endpoint with an operator-managed reverse proxy; Compose binds the app to localhost by default.

License and contributions

• AGPL-3.0 for the entire codebase — self-hosted and cloud-related source share one repository and one license.
• Contributions are accepted under the DCO (Developer Certificate of Origin, via Signed-off-by); no CLA. See CONTRIBUTING.md.
• Issues and pull requests live on GitHub, the single primary repository. The Gitee repository is a one-way mirror for access from mainland China.

Managed cloud is optional

Crowntime also operates a managed cloud edition for organizations that prefer not to run the system themselves. It is an optional convenience service — not a prerequisite for using the open-source edition, and the self-hosted edition is not a feature-limited version of it. Both editions come from the same codebase.

Not affiliated with Tencent

"WeCom" and "企业微信" are trademarks of Tencent. This is an independent open-source project with no affiliation to, sponsorship from, or endorsement by Tencent. This announcement makes no compliance, security, or performance guarantees — evaluate the system against your own requirements before deploying it.